Re: USB Install problem with Fedora-13-x86_64-DVD - RESOLVED
Great, Dar!!! I added iso file (after removing Packages and Repodata) and it really worked for me as for you.. :))) I supposed that If I offer the Creator the DVD iso file, that the corresponding stick will be created. It was the mistake. Thank you so much for your greta help! Regards jk > Původní zpráva > Od: Darr > Předmět: Re: USB Install problem with Fedora-13-x86_64-DVD > Datum: 02.8.2010 15:10:34 > > On Monday, 02 August, 2010 @06:31 zulu, j.halifax scribed: > > > I have created 8GB USB flash memory installation media > > with LiveUSB-Creator on MSW and used it for USB installation. > > > > After creating Install Target Device (HD) I got the following > > Error Message: > > > > == > > Missing ISO 0660 Image > > > That program creates a bootable Live USB, not a bootable > installation USB. To turn the stick that program makes into > an installation USB stick, copy the ISO to the thumbdrive, too. > > If you want to make your writable space larger (how big did > you set the 'Persistent Storage' slider?), delete the /packages > and /repodata subdirectories from the stick before copying > the ISO file to the USB stick. > > Near the beginning of the install, anaconda will give you a > dialog and ask where the ISO is... it's typically in /sdb. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: USB Install problem with Fedora-13-x86_64-DVD
Thank you... > $ rpm -qf --whatprovides /usr/bin/livecd-iso-to-disk > livecd-tools-031-1.fc12.1.i686 That's bad as I have no Internet yet.. :((( Thanks anyway... :) So you will need to yum nstall livecd-tools > Původní zpráva > Od: JD > Předmět: Re: USB Install problem with Fedora-13-x86_64-DVD > Datum: 02.8.2010 09:52:27 > > On 08/02/2010 12:05 AM, j.halifax . wrote: > > Thank you! > > > >> Here is how I did it: > >> sudo /usr/bin/livecd-iso-to-disk --format --reset-mbr > > Is the /livecd-iso-to-disk included in Fedora Live? > > > > Thanks. > I do not think so. It is provided by: > > $ rpm -qf --whatprovides /usr/bin/livecd-iso-to-disk > livecd-tools-031-1.fc12.1.i686 > > So you will need to yum nstall livecd-tools > > CHeers, > > JD > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: USB Install problem with Fedora-13-x86_64-DVD
Thank you! > Here is how I did it: > sudo /usr/bin/livecd-iso-to-disk --format --reset-mbr Is the /livecd-iso-to-disk included in Fedora Live? Thanks. > Původní zpráva > Od: JD > Předmět: Re: USB Install problem with Fedora-13-x86_64-DVD > Datum: 02.8.2010 08:50:32 > > On 08/01/2010 11:31 PM, j.halifax . wrote: > > Hi All, > > > > Could you help me pls with installing fc13 distribution > > of Fedora-13-x86_64-DVD from USB? > > > > I have created 8GB USB flash memory installation media > > with LiveUSB-Creator on MSW and used it for USB installation. > > > > After creating Install Target Device (HD) I got the following > > Error Message: > > > > == > > Missing ISO 0660 Image > > The installer has tried to mount image #1 but cannot find > > it on the hard drive. > > Please copy this image to the device and click Retry. > > == > > > > I can install Fedora-13-x86_64-Live but then I don't know > > how to install the additional applications included in the > > Full fc13 Distribution. > > > > Any idea what should I do! :( > > > > Thank you so much! > > jh > I do not know if the Windows version has bugs or not. > I used an existing fedora to install the F13 iso onto an 8GB usb stick. > Here is how I did it: > sudo /usr/bin/livecd-iso-to-disk --format --reset-mbr > /tmp/Fedora-13-i386-DVD.iso /dev/sde > > where /dev/sde is my USB stick drive. > > I can boot this usb stick and install F13 onto hard drive without any > issues. > > Good luck. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
USB Install problem with Fedora-13-x86_64-DVD
Hi All, Could you help me pls with installing fc13 distribution of Fedora-13-x86_64-DVD from USB? I have created 8GB USB flash memory installation media with LiveUSB-Creator on MSW and used it for USB installation. After creating Install Target Device (HD) I got the following Error Message: == Missing ISO 0660 Image The installer has tried to mount image #1 but cannot find it on the hard drive. Please copy this image to the device and click Retry. == I can install Fedora-13-x86_64-Live but then I don't know how to install the additional applications included in the Full fc13 Distribution. Any idea what should I do! :( Thank you so much! jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
VPN (pptpd) stopped working
Hi all, Could you please advise, how to find why VPN which was working with pptpd stopped working? I was out and when I came I found the box down and since that time VPN is not working. - Windows client says Error 678 "The remote computer didn't respond" - (but I can ping it as 195.39.130.92) and - on the Internet port of the server 195.39.130.92 I can see the following traffic related to the VPN client PC: # tcpdump -n -i eth0|grep "94.129.168.182" |grep -v "ICMP" tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:31:50.107939 IP 94.129.168.182.gw > 195.39.130.92.pptp: Flags [S], seq 3061761952, win 16384, options [mss 1460,nop,nop,sackOK], length 0 11:31:50.107967 IP 195.39.130.92.pptp > 94.129.168.182.gw: Flags [R.], seq 0, ack 3061761953, win 0, length 0 11:31:50.608848 IP 94.129.168.182.gw > 195.39.130.92.pptp: Flags [S], seq 3061761952, win 16384, options [mss 1460,nop,nop,sackOK], length 0 11:31:50.608869 IP 195.39.130.92.pptp > 94.129.168.182.gw: Flags [R.], seq 0, ack 1, win 0, length 0 11:31:51.228744 IP 94.129.168.182.gw > 195.39.130.92.pptp: Flags [S], seq 3061761952, win 16384, options [mss 1460,nop,nop,sackOK], length 0 11:31:51.228762 IP 195.39.130.92.pptp > 94.129.168.182.gw: Flags [R.], seq 0, ack 1, win 0, length 0 Thank you for your help! jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: fc12 encrypted file system
I do support Tim's point of view. jh > Původní zpráva > Od: Tim > Předmět: Re: fc12 encrypted file system > Datum: 16.5.2010 06:49:08 > > On Sun, 2010-05-16 at 00:05 -0400, Genes MailLists wrote: > > Strictly speaking you were not ... you were making a meta comment > > about hijacking - not the topic itself. > > Strictly speaking, I was. I was replying directly to a post, about that > post. About *what* that post was. And in response to it. The message > was directly related to the one I replied to, and properly associated by > the headers. The one I drew attention to had absolutely nothing to do > with the message it replied to. *THAT* is hijacking. > > My response explained was what wrong, why it was wrong, and how to go > about getting their answer. Direct and to the point, without even > trying to be insulting (unlike jdow). Useful information to them, and > to other people who use mailing lists. > > > > It is generally considered more appropriate to reply directly to the > > poster to proffer advice .. rather than to the list on such issues. > > It is *sometimes* better to do that. Sometimes the best course of > action is to respond as I did. If nobody makes a public announcement > about not hijacking, nobody else gets to see that it's unwanted. Then, > pretty soon, just about all your *new* messages become erroneous > replies. > > If you pay attention to this list, you'll see that we occasionally make > such redirective postings to thread hijackers. We don't respond to > every one. > > > I think that was jdow's point. > > That wasn't the point they said. The point they made was to try and be > insulting, deliberately making a smartarse response just to write an > email, when there wasn't any need to make any further postings to the > thread. While passing a judgement call on myself being unaware of > something, which they have no information about whether I was aware of > it or not. There's something seriously wrong with the mental processes > of people who proceed to declare what someone else knows or doesn't > know, without any actual knowledge of that other person. > > For the record I am more than well aware of the supposed *irony* of > making the sort of response that I did. Those of us who respond to such > posts do think twice about doing so. And like I said before, sometimes > the best action is to do what I did. > > jdow was doing what jdow continually does on this list, act the jackass, > simply for the sake of it. A large proportion of their messages are > just the same. > > -- > [...@localhost ~]$ uname -r > 2.6.27.25-78.2.56.fc9.i686 > > Don't send private replies to my address, the mailbox is ignored. I > read messages from the public lists. > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: GW (LAN1, LAN2, ADSL) config
> > .please do netstat -rn > Please also do /sbin/ifconfig -a > == netstat == # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.180.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 10.255.253.010.255.250.250 255.255.255.0 UG0 0 0 eth2 10.1.1.010.255.250.250 255.255.255.0 UG0 0 0 eth2 195.39.130.00.0.0.0 255.255.255.0 U 0 0 0 eth0 10.255.250.00.0.0.0 255.255.255.0 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3 172.17.0.0 192.168.180.1 255.255.0.0 UG0 0 0 eth3 192.168.0.0 192.168.180.1 255.255.0.0 UG0 0 0 eth3 0.0.0.0 195.39.130.89 0.0.0.0 UG0 0 0 eth0 == ifconfig == ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:24299910 errors:0 dropped:0 overruns:0 frame:0 TX packets:15282420 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16111717780 (15.0 GiB) TX bytes:2946725879 (2.7 GiB) Interrupt:21 Base address:0xca00 eth1 Link encap:Ethernet HWaddr 00:19:D1:9D:E6:14 BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Memory:9220-9222 eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36 inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0 inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:53693057 errors:0 dropped:0 overruns:0 frame:0 TX packets:15359524 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5565104705 (5.1 GiB) TX bytes:13115812080 (12.2 GiB) Interrupt:22 Base address:0xa900 eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4 inet addr:192.168.180.100 Bcast:192.168.180.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4068329 errors:0 dropped:0 overruns:0 frame:0 TX packets:60337 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:417749601 (398.3 MiB) TX bytes:4328913 (4.1 MiB) Interrupt:18 Base address:0x6800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:431338 errors:0 dropped:0 overruns:0 frame:0 TX packets:431338 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41551814 (39.6 MiB) TX bytes:41551814 (39.6 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Thank you so much... :) jh > Původní zpráva > Od: Rick Sewill > Předmět: Re: GW (LAN1, LAN2, ADSL) config > Datum: 21.4.2010 01:10:47 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/20/2010 05:48 PM, j.halifax . wrote: > >>> > >> Is IP forwarding on? > >> > > Yes, it is. > > > > > > > >> Původní zpráva > >> Od: Terry Polzin > >> Předmět: Re: GW (LAN1, LAN2, ADSL) config > >> Datum: 20.4.2010 19:03:39 > >> > >> On Tue, 2010-04-20 at 15:31 +0200, j.halifax . wrote: > >>> Hi All, > >>> > >>> please help me kindly to reconfig my default GW (Fedora 12). > >>> > >>> The GW has 3 active Ethernet cards: > >>> eth0 - connected to Internet ADSL router (incl. VPN, pptpd) > >>> eth1 - not used > >>> eth2 - LAN1 > >>> eth3 - LAN2. > >>> > >>> I had everything working fine but due to some problems I lost > >>> the configuration of the GW and I can't get it working again. > >>> > >>> (1) The Internet access (LAN1 -> GW -> Internet) is working fine. > >>> (2) The access of (Internet -> GW -> LAN1 / LAN2) is ok incl. VPN > >>>
Re: GW (LAN1, LAN2, ADSL) config
> > > Is IP forwarding on? > Yes, it is. > Původní zpráva > Od: Terry Polzin > Předmět: Re: GW (LAN1, LAN2, ADSL) config > Datum: 20.4.2010 19:03:39 > > On Tue, 2010-04-20 at 15:31 +0200, j.halifax . wrote: > > Hi All, > > > > please help me kindly to reconfig my default GW (Fedora 12). > > > > The GW has 3 active Ethernet cards: > > eth0 - connected to Internet ADSL router (incl. VPN, pptpd) > > eth1 - not used > > eth2 - LAN1 > > eth3 - LAN2. > > > > I had everything working fine but due to some problems I lost > > the configuration of the GW and I can't get it working again. > > > > (1) The Internet access (LAN1 -> GW -> Internet) is working fine. > > (2) The access of (Internet -> GW -> LAN1 / LAN2) is ok incl. VPN > > (3) I can not access LAN2 neither from LAN1 nor from GW box > > > > Traceroute shows that for (3) packets don't go to eth3 (LAN2) as > > they should, but they fall down to eth0 (default gw). > > > > Can you please advise me what I need to set-up (iptables) in the GW? > > > > Thank you so much for your kind help. > > > > Regards, > > jh > > > Is IP forwarding on? > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
GW (LAN1, LAN2, ADSL) config
Hi All, please help me kindly to reconfig my default GW (Fedora 12). The GW has 3 active Ethernet cards: eth0 - connected to Internet ADSL router (incl. VPN, pptpd) eth1 - not used eth2 - LAN1 eth3 - LAN2. I had everything working fine but due to some problems I lost the configuration of the GW and I can't get it working again. (1) The Internet access (LAN1 -> GW -> Internet) is working fine. (2) The access of (Internet -> GW -> LAN1 / LAN2) is ok incl. VPN (3) I can not access LAN2 neither from LAN1 nor from GW box Traceroute shows that for (3) packets don't go to eth3 (LAN2) as they should, but they fall down to eth0 (default gw). Can you please advise me what I need to set-up (iptables) in the GW? Thank you so much for your kind help. Regards, jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: secure log stopped working [SOLVED]
> > ...I would like to understand possible causes anyway. > 1. out of space > 2. permission change (should be root:root 600) > 3. rsyslogd crash The (2) was my case. :) Thank you so much for making me good nights! ;))) jh > Původní zpráva > Od: Phil Meyer > Předmět: Re: secure log stopped working > Datum: 04.3.2010 23:19:21 > > On 03/04/2010 01:14 PM, j.halifax . wrote: > >> ...what could be a reason that records of > >> /var/log/secure stopped coming? > >> > > kill -1 > > helped but I would like to understand possible causes anyway. > > > > Thank you. > > > > > > 1. out of space > > 2. permission change (should be root:root 600) > > 3. rsyslogd crash > > Those are my guesses. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: secure log stopped working
> ...what could be a reason that records of > /var/log/secure stopped coming? kill -1 helped but I would like to understand possible causes anyway. Thank you. > Původní zpráva > Od: j.halifax . > Předmět: secure log stopped working > Datum: 04.3.2010 15:30:59 > > Hi all, > > Don't you know anybody please what could be a reason that records of > /var/log/secure stopped coming? Couldn't it be due to hacking the box? :( > > Thank you for any help. > jh > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
secure log stopped working
Hi all, Don't you know anybody please what could be a reason that records of /var/log/secure stopped coming? Couldn't it be due to hacking the box? :( Thank you for any help. jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Which "VIDEO-PLAYER" ?
> On your web site you create an anchor to a video file, at the client > side (the computer visiting your site), the appropriate video player > will be launched. You could do a php script to do it a loop of > videos. Probably I didn't explain the task well. Everything should run in the same PC. (i.e. no Internet, client and no server). I am afraid that the loop would require restarting the player SW and breaks in the content. Thank you for your idea! jh > Původní zpráva > Od: Luis Costabile > Předmět: Re: Which "VIDEO-PLAYER" ? > Datum: 26.2.2010 14:02:35 > > On your web site you create an anchor to a video file, at the client > side (the computer visiting your site), the appropriate video player > will be launched. You could do a php script to do it a loop of > videos. > > > On 25 February 2010 23:44, j.halifax . wrote: > > Hi video-gurus, > > > > Could you please give me an advice of which "video-player" (some SW) to use > for the following task on FC12_64 ? > > > > (1) I need to create a web-site on my PC with a PLAYER playing video in one > > of > its frames > > (2) The video-content played should be an "endless" list of small > > video-shots > with their names > > (or data) being read from standard input of the player or from an > > "infinitely" > growing file or pipe > > > > Questions are the following: > > - Which "video-player" to use > > - How to call it from the web site for running it in a frame > > > > Thank you so much... > > jh > > -- > > users mailing list > > users@lists.fedoraproject.org > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Which "VIDEO-PLAYER" ?
> I think VLC and its streaming capabilities might do what you want to achieve. Actually, I don't need to stream the content, but your idea is good. I can stream the content and to see the result in the same PC in the browser. :) Thank you! jh > Původní zpráva > Od: Jorge Fábregas > Předmět: Re: Which "VIDEO-PLAYER" ? > Datum: 26.2.2010 13:26:39 > > On Friday 26 February 2010 00:44:57 j.halifax . wrote: > > Questions are the following: > > - Which "video-player" to use > > - How to call it from the web site for running it in a frame > > I think VLC and its streaming capabilities might do what you want to achieve. > You can further investigate there:: > > http://www.videolan.org/vlc/ > > HTH, > Jorge > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Which "VIDEO-PLAYER" ?
Hi video-gurus, Could you please give me an advice of which "video-player" (some SW) to use for the following task on FC12_64 ? (1) I need to create a web-site on my PC with a PLAYER playing video in one of its frames (2) The video-content played should be an "endless" list of small video-shots with their names (or data) being read from standard input of the player or from an "infinitely" growing file or pipe Questions are the following: - Which "video-player" to use - How to call it from the web site for running it in a frame Thank you so much... jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Routing problems
> Are you sure you have packet forwarding enabled? > What does 'sysctl -a | grep forward' say? sysctl -a | grep forward net.ipv4.conf.all.forwarding = 1 net.ipv4.conf.all.mc_forwarding = 0 net.ipv4.conf.default.forwarding = 1 net.ipv4.conf.default.mc_forwarding = 0 net.ipv4.conf.lo.forwarding = 1 net.ipv4.conf.lo.mc_forwarding = 0 net.ipv4.conf.eth1.forwarding = 1 net.ipv4.conf.eth1.mc_forwarding = 0 net.ipv4.conf.eth0.forwarding = 1 net.ipv4.conf.eth0.mc_forwarding = 0 net.ipv4.conf.eth2.forwarding = 1 net.ipv4.conf.eth2.mc_forwarding = 0 net.ipv4.conf.eth3.forwarding = 1 net.ipv4.conf.eth3.mc_forwarding = 0 net.ipv4.conf.sit0.forwarding = 1 net.ipv4.conf.sit0.mc_forwarding = 0 net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 0 net.ipv6.conf.all.mc_forwarding = 0 net.ipv6.conf.default.forwarding = 0 net.ipv6.conf.default.mc_forwarding = 0 net.ipv6.conf.eth1.forwarding = 0 net.ipv6.conf.eth1.mc_forwarding = 0 net.ipv6.conf.sit0.forwarding = 0 net.ipv6.conf.sit0.mc_forwarding = 0 net.ipv6.conf.lo.forwarding = 0 net.ipv6.conf.lo.mc_forwarding = 0 net.ipv6.conf.eth2.forwarding = 0 net.ipv6.conf.eth2.mc_forwarding = 0 net.ipv6.conf.eth0.forwarding = 0 net.ipv6.conf.eth0.mc_forwarding = 0 net.ipv6.conf.eth3.forwarding = 0 net.ipv6.conf.eth3.mc_forwarding = 0 === net.ipv4.ip_forward = 1. Is it sufficient? Thank you... > Původní zpráva > Od: Bruno Wolff III > Předmět: Re: Routing problems > Datum: 20.2.2010 16:52:22 > > On Thu, Feb 18, 2010 at 07:31:56 +0100, > "j.halifax ." wrote: > > > > >From the LAN default GW (10.255.250.37) > > - I can ping 172.17.1.50: > > PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > > 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms > > 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms > > > > >From other boxes in the same LAN (e.g. 10.255.250.38) > > - I cann't ping 172.17.1.50 > > - I cann't traceroute 172.17.1.50: It goes to LAN default GW > > 10.255.250.37 and then to its default GW dsl-router on eth0 > > instead of eth3 (so that the routing rule for 172.17.0.0 > > doesn't > > match for 172.17.1.50) > > > > Can anybody help pleasee? > > Are you sure you have packet forwarding enabled? > What does 'sysctl -a | grep forward' say? > > > Původní zpráva > Od: Bruno Wolff III > Předmět: Re: Routing problems > Datum: 20.2.2010 16:52:22 > > On Thu, Feb 18, 2010 at 07:31:56 +0100, > "j.halifax ." wrote: > > > > >From the LAN default GW (10.255.250.37) > > - I can ping 172.17.1.50: > > PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > > 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms > > 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms > > > > >From other boxes in the same LAN (e.g. 10.255.250.38) > > - I cann't ping 172.17.1.50 > > - I cann't traceroute 172.17.1.50: It goes to LAN default GW > > 10.255.250.37 and then to its default GW dsl-router on eth0 > > instead of eth3 (so that the routing rule for 172.17.0.0 > > doesn't > > match for 172.17.1.50) > > > > Can anybody help pleasee? > > Are you sure you have packet forwarding enabled? > What does 'sysctl -a | grep forward' say? > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Routing problems
> ip rule list ip rule list 0: from all lookup local 32766: from all lookup main 32767: from all lookup default > ip route list table local > ip route list table main > ip route list table default ip route list table local local 195.39.130.92 dev eth0 proto kernel scope host src 195.39.130.92 broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1 local 192.168.180.100 dev eth3 proto kernel scope host src 192.168.180.100 broadcast 10.255.250.255 dev eth2 proto kernel scope link src 10.255.250.37 broadcast 192.168.180.0 dev eth3 proto kernel scope link src 192.168.180.100 broadcast 195.39.130.255 dev eth0 proto kernel scope link src 195.39.130.92 broadcast 10.255.250.0 dev eth2 proto kernel scope link src 10.255.250.37 broadcast 192.168.180.255 dev eth3 proto kernel scope link src 192.168.180.100 broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1 broadcast 195.39.130.0 dev eth0 proto kernel scope link src 195.39.130.92 local 10.255.250.37 dev eth2 proto kernel scope host src 10.255.250.37 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1 ip route list table main 192.168.180.0/24 dev eth3 proto kernel scope link src 192.168.180.100 10.200.1.0/24 via 10.255.250.250 dev eth2 195.39.130.0/24 dev eth0 proto kernel scope link src 195.39.130.92 10.1.1.0/24 via 10.255.250.250 dev eth2 10.201.1.0/24 via 10.255.250.250 dev eth2 172.17.1.0/24 via 192.168.180.100 dev eth3 10.255.250.0/24 dev eth2 proto kernel scope link src 10.255.250.37 169.254.0.0/16 dev eth0 scope link metric 1003 169.254.0.0/16 dev eth2 scope link metric 1004 169.254.0.0/16 dev eth3 scope link metric 1005 192.168.0.0/16 via 192.168.180.100 dev eth3 default via 195.39.130.89 dev eth0 ip route list table default My comment: Table is empty == I can't see any fault. Packets to 172.17.1.50 should match 172.17.1.0/24 via 192.168.180.100 dev eth3 and go to eth3. But it doesn't and goes by default to eth0 (Internet) Don't you know any way of debugging routing decisions (to see why do packets match or not)? Thank you again. :) jh > Původní zpráva > Od: Rick Sewill > Předmět: Re: Routing problems > Datum: 19.2.2010 05:54:39 > > On Fri, 2010-02-19 at 04:31 +0100, j.halifax . wrote: > > > What happens if you try to "ping" from the eth2 interface of the router? > > > ping -I 10.255.250.37 172.17.1.50 > > > > Commands issued in 10.255.l250.37 (via ssh 195.39.130.92): > > = > > ping -I 10.255.250.37 172.17.1.50 > > PING 172.17.1.50 (172.17.1.50) from 10.255.250.37 : 56(84) bytes of data. > > >From 195.39.130.92 icmp_seq=2 Destination Host Unreachable > > :( > > ping -I eth2 182.15.1.50 > > PING 182.15.1.50 (182.15.1.50) from 10.255.250.37 eth2: 56(84) bytes of > > data. > > >From 195.39.130.92 icmp_seq=1 Destination Host Unreachable > > :( > > ping 172.17.1.50 > > PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > > 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=8.65 ms > > :) > > > > == > > iptables -L -v > > Chain INPUT (policy ACCEPT 3325K packets, 706M bytes) > > pkts bytes target prot opt in out source > destination > > > > Chain FORWARD (policy ACCEPT 2152K packets, 964M bytes) > > pkts bytes target prot opt in out source > destination > > 534 40008 ACCEPT all -- anyeth3anywhere > 172.17.0.0/16 > > > > Chain OUTPUT (policy ACCEPT 1080K packets, 160M bytes) > > pkts bytes target prot opt in out source > destination > > > > ping -I eth2 172.17.1.50 > > PING 172.17.1.50 (172.17.1.50) from 10.255.250.37 eth2: 56(84) bytes of > > data. > > >From 195.39.130.92 icmp_seq=2 Destination Host Unreachable > > > > iptables -L -v > > Chain INPUT (policy ACCEPT 3325K packets, 706M bytes) > > pkts bytes target prot opt in out source > destination > > > > Chain FORWARD (policy ACCEPT 2153K packets, 964M bytes) > > pkts bytes target prot opt in out source > destination > > 534 40008 ACCEPT all -- anyeth3anywhere > 172.17.0.0/16 > > > > Chain OUTPUT (policy ACCEPT 1080K packets, 160M bytes) > > pkts bytes target prot opt in out source > destination > > = > > > > Thank you.. > > jh > > > You convinced me my gut instinct is wrong about iptables being involved. > > I have another line of thought. > > I believe, with iproute2, there are additional routing tables. > > With a note of caution as I am reading documentation as I go, > and you may find you have more experienc
Re: Routing problems
> What happens if you try to "ping" from the eth2 interface of the router? > ping -I 10.255.250.37 172.17.1.50 Commands issued in 10.255.l250.37 (via ssh 195.39.130.92): = ping -I 10.255.250.37 172.17.1.50 PING 172.17.1.50 (172.17.1.50) from 10.255.250.37 : 56(84) bytes of data. >From 195.39.130.92 icmp_seq=2 Destination Host Unreachable :( ping -I eth2 182.15.1.50 PING 182.15.1.50 (182.15.1.50) from 10.255.250.37 eth2: 56(84) bytes of data. >From 195.39.130.92 icmp_seq=1 Destination Host Unreachable :( ping 172.17.1.50 PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=8.65 ms :) == iptables -L -v Chain INPUT (policy ACCEPT 3325K packets, 706M bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 2152K packets, 964M bytes) pkts bytes target prot opt in out source destination 534 40008 ACCEPT all -- anyeth3anywhere 172.17.0.0/16 Chain OUTPUT (policy ACCEPT 1080K packets, 160M bytes) pkts bytes target prot opt in out source destination ping -I eth2 172.17.1.50 PING 172.17.1.50 (172.17.1.50) from 10.255.250.37 eth2: 56(84) bytes of data. >From 195.39.130.92 icmp_seq=2 Destination Host Unreachable iptables -L -v Chain INPUT (policy ACCEPT 3325K packets, 706M bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 2153K packets, 964M bytes) pkts bytes target prot opt in out source destination 534 40008 ACCEPT all -- anyeth3anywhere 172.17.0.0/16 Chain OUTPUT (policy ACCEPT 1080K packets, 160M bytes) pkts bytes target prot opt in out source destination = Thank you.. jh > Původní zpráva > Od: Rick Sewill > Předmět: Re: Routing problems > Datum: 18.2.2010 20:10:40 > > On Thu, 2010-02-18 at 13:48 +0100, j.halifax . wrote: > > > I think the problem is probably the routing tables in the other boxes > > > in the same LAN (e.g. 10.255.250.38) > > > > route in 10.255.250.38: > > Destination Gateway GenmaskFlags Metric RefUse Iface > > 192.168.122.0 * 255.255.255.0 U 0 00 virbr0 > > 10.255.250.0* 255.255.255.0 U 0 00 eth0 > > link-local * 255.255.0.0 U 0 00 eth0 > > default 10.255.250.37 0.0.0.0 UG0 00 eth0 > > > > traceroute -n 172.17.1.50 (from 10.255.250.38): > > traceroute to 172.17.1.50 (172.17.1.50), 30 hops max, 40 byte packets > > 1 10.255.250.37 0.194 ms 0.124 ms 0.120 ms > > 2 195.39.130.92 3000.438 ms !H 3000.449 ms !H 3000.427 ms !H > > > > The request comes to the LAN default GW and fells through to > > its default GW eth0 leading to Internet, instead of going to eth3 > > > > :(( > > Thank you... > > jh > > > > > > I'm still stumped. > > What happens if you try to "ping" from the eth2 interface of the router? > > ping -I 10.255.250.37 172.17.1.50 > > I guess the following is equivalent: > ping -I eth2 172.17.1.50 > > I expect this ping to fail. > > I am still suspicious iptables is involved. > > If your router had periods of time when there was no traffic, > I would do > iptables -L -v > to get the packet counts for every iptables rule, > do the ping from the PC that fails, and do > iptables -L -v > again and compare the packet counts for every iptables rule, > to determine which iptables rules were being used for the ping packets. > > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Routing problems
> I think the problem is probably the routing tables in the other boxes > in the same LAN (e.g. 10.255.250.38) route in 10.255.250.38: Destination Gateway GenmaskFlags Metric RefUse Iface 192.168.122.0 * 255.255.255.0 U 0 00 virbr0 10.255.250.0* 255.255.255.0 U 0 00 eth0 link-local * 255.255.0.0 U 0 00 eth0 default 10.255.250.37 0.0.0.0 UG0 00 eth0 traceroute -n 172.17.1.50 (from 10.255.250.38): traceroute to 172.17.1.50 (172.17.1.50), 30 hops max, 40 byte packets 1 10.255.250.37 0.194 ms 0.124 ms 0.120 ms 2 195.39.130.92 3000.438 ms !H 3000.449 ms !H 3000.427 ms !H The request comes to the LAN default GW and fells through to its default GW eth0 leading to Internet, instead of going to eth3 :(( Thank you... jh > Původní zpráva > Od: Andrew Haley > Předmět: Re: Routing problems > Datum: 18.2.2010 13:08:00 > > On 02/18/2010 11:56 AM, j.halifax . wrote: > >> Please post > >> * Full details of your network > >> * The routing table, uncensored :) > > Hmm, this is a remarkable plate of spaghetti. > > I think the problem is probably the routing tables in the other boxes > in the same LAN (e.g. 10.255.250.38) > > Andrew. > > > > route > > Destination Gateway Genmask Flags Metric RefUse > > Iface > > 192.168.180.0 * 255.255.255.0 U 0 0> > 0 > eth3 > > 10.200.1.0 10.255.250.250 255.255.255.0 UG0 00 eth2 > > 195.39.130.0* 255.255.255.0 U 0 0 > > 0 > eth0 > > 10.1.1.010.255.250.250 255.255.255.0 UG0 00 > > eth2 > > 10.201.1.0 10.255.250.250 255.255.255.0 UG0 00 eth2 > > 10.255.250.0* 255.255.255.0 U 0 0> > 0 > eth2 > > link-local *255.255.0.0 U 1003 0 > > > 0 eth0 > > link-local *255.255.0.0 U 1004 0 > > > 0 eth2 > > link-local *255.255.0.0 U 1005 0 > > > 0 eth3 > > 172.17.0.0 192.168.180.100 255.255.0.0 UG0 00 eth3 > > 192.168.0.0 192.168.180.100 255.255.0.0 UG0 00 eth3 > > default pc89.n0.0.0.0 UG0 0 > > > 0 eth0 > > > > ifconfig > > eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D > > inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0 > > inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:5174154 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3474632 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:2851269308 (2.6 GiB) TX bytes:646868735 (616.9 MiB) > > Interrupt:21 Base address:0xca00 > > > > eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36 > > inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0 > > inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:18187178 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:2506338 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:1585335954 (1.4 GiB) TX bytes:1901082841 (1.7 GiB) > > Interrupt:22 Base address:0xa900 > > > > eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4 > > inet addr:192.168.180.100 Bcast:192.168.180.255 > Mask:255.255.255.0 > > inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:2048995 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4746 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:201714109 (192.3 MiB) TX bytes:364982 (356.4 KiB) > > Interrupt:18 Base address:0x6800 > > > > loLink encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:255570 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:255570 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:25105805 (23.9 MiB) TX bytes:25105805 (23.9 MiB) > > > > Thanx. :) > > > > > >> Povodní zpráva > >> Od: Andrew Haley > >> PYedmt: Re: Routing problems > >> Datum: 18.2.2010 12:31:34 > >> > >> On 02/1
Re: Routing problems
> Please post > * Full details of your network > * The routing table, uncensored :) route Destination Gateway Genmask Flags Metric RefUse Iface 192.168.180.0 * 255.255.255.0 U 0 00 eth3 10.200.1.0 10.255.250.250 255.255.255.0 UG0 00 eth2 195.39.130.0* 255.255.255.0 U 0 00 eth0 10.1.1.010.255.250.250 255.255.255.0 UG0 00 eth2 10.201.1.0 10.255.250.250 255.255.255.0 UG0 00 eth2 10.255.250.0* 255.255.255.0 U 0 00 eth2 link-local *255.255.0.0 U 1003 0 0 eth0 link-local *255.255.0.0 U 1004 0 0 eth2 link-local *255.255.0.0 U 1005 0 0 eth3 172.17.0.0 192.168.180.100 255.255.0.0 UG0 00 eth3 192.168.0.0 192.168.180.100 255.255.0.0 UG0 00 eth3 default pc89.n0.0.0.0 UG0 00 eth0 ifconfig eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:5174154 errors:0 dropped:0 overruns:0 frame:0 TX packets:3474632 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2851269308 (2.6 GiB) TX bytes:646868735 (616.9 MiB) Interrupt:21 Base address:0xca00 eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36 inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0 inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:18187178 errors:0 dropped:0 overruns:0 frame:0 TX packets:2506338 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1585335954 (1.4 GiB) TX bytes:1901082841 (1.7 GiB) Interrupt:22 Base address:0xa900 eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4 inet addr:192.168.180.100 Bcast:192.168.180.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2048995 errors:0 dropped:0 overruns:0 frame:0 TX packets:4746 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:201714109 (192.3 MiB) TX bytes:364982 (356.4 KiB) Interrupt:18 Base address:0x6800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:255570 errors:0 dropped:0 overruns:0 frame:0 TX packets:255570 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25105805 (23.9 MiB) TX bytes:25105805 (23.9 MiB) Thanx. :) > Původní zpráva > Od: Andrew Haley > Předmět: Re: Routing problems > Datum: 18.2.2010 12:31:34 > > On 02/18/2010 11:19 AM, j.halifax . wrote: > >> What is the address of the subnet "other LAN" ? > >> There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. > > You are right, both of them are accessible through eth3 and the same > > box of 192.168.180.100 (I didn't include the whole routing table) like: > > 172.17.0.0192.168.180.100 255.255.0.0UG 000 eth3 > > 192.168.0.0 192.168.180.100 255.255.0.0UG 000 eth3. > > Please post > > * Full details of your network > * The routing table, uncensored > > >> Původní zpráva > >> Od: Andrew Haley > >> Předmět: Re: Routing problems > >> Datum: 18.2.2010 11:51:17 > >> > >> On 02/18/2010 10:01 AM, Rick Sewill wrote: > >>> On Thu, 2010-02-18 at 07:31 +0100, j.halifax . wrote: > Hi All, > > Could you please help me with routing in the LAN default GW box? > > I have > eth0 connected to Internet > eth2 to internal LAN 10.255.250.0 > LAN default GW is 10.255.250.37 > eth3 connected to other LAN > >> > >> What is the address of the subnet "other LAN" ? > >> > >> There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. > >> > >> Andrew. > >> > >> > >> > Route in the default GW (10.255.250.37): > > Destination Gateway Genmask Flags Metric Ref Use > >> Iface > 192.168.180.0 * 255.255.255.0 U 0 0 > > > >> 0 eth3 > 10.255.250.0 * 2
Re: Routing problems
> What is the address of the subnet "other LAN" ? > There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. You are right, both of them are accessible through eth3 and the same box of 192.168.180.100 (I didn't include the whole routing table) like: 172.17.0.0192.168.180.100 255.255.0.0UG 000 eth3 192.168.0.0 192.168.180.100 255.255.0.0UG 000 eth3. Thank you for help! > Původní zpráva > Od: Andrew Haley > Předmět: Re: Routing problems > Datum: 18.2.2010 11:51:17 > > On 02/18/2010 10:01 AM, Rick Sewill wrote: > > On Thu, 2010-02-18 at 07:31 +0100, j.halifax . wrote: > >> Hi All, > >> > >> Could you please help me with routing in the LAN default GW box? > >> > >> I have > >> eth0 connected to Internet > >> eth2 to internal LAN 10.255.250.0 > >> LAN default GW is 10.255.250.37 > >> eth3 connected to other LAN > > What is the address of the subnet "other LAN" ? > > There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. > > Andrew. > > > > >> Route in the default GW (10.255.250.37): > >> > >> Destination Gateway Genmask Flags Metric Ref Use > Iface > >> 192.168.180.0 * 255.255.255.0 U 0 0 > >> > 0 eth3 > >> 10.255.250.0 * 255.255.255.0 U 0 0 > >> > 0 eth2 > >> link-local * 255.255.0.0 U 1003 > >> 0 > 0 eth0 > >> link-local * 255.255.0.0 U 1004 > >> 0 > 0 eth2 > >> link-local * 255.255.0.0 U 1005 > >> 0 > 0 eth3 > >> 172.17.0.0 192.168.180.100 255.255.0.0 UG0 00 > eth3 > >> default dsl-router0.0.0.0 UG0 > >> 0 > 0 eth0 > >> > >> >From the LAN default GW (10.255.250.37) > >> - I can ping 172.17.1.50: > >> PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > >> 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms > >> 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms > >> > >> >From other boxes in the same LAN (e.g. 10.255.250.38) > >> - I cann't ping 172.17.1.50 > >> - I cann't traceroute 172.17.1.50: It goes to LAN default GW > >> 10.255.250.37 and then to its default GW dsl-router on eth0 > >> instead of eth3 (so that the routing rule for 172.17.0.0 > >> doesn't > > >> match for 172.17.1.50) > >> > >> Can anybody help pleasee? > >> Thank you so much! > >> jh > >> > > > > Your problem has me stumped. > > > > The only thing I can think of is to ask how iptables is set up. > > > > I think you have iptables doing masquerading to the eth0 interface. > > The masquerading shouldn't be the problem. > > > > Are you doing anything special with packets coming in eth2 in iptables? > > > > I assume 10.255.250.38 can ping the Internet so you have routing set up. > > > > I can't think of anything else to check at this moment. > > > > Hopefully others will have better suggestions and ideas where to look. > > > > > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Routing problems
> The only thing I can think of is to ask how iptables is set up. The iptables > are not used (I am not familiar with them, but tried different arrangement > and nothing helped). > I think you have iptables doing masquerading to the eth0 interface. > The masquerading shouldn't be the problem. Yes, masquerading is on eth0 and it works ok, Internet access as well both from inside out and from outside to the LAN via VPN (pptpd). But it doesn't work from outside to 172.17.1.50 (or so) analogously... Thank you for your help! > Původní zpráva > Od: Rick Sewill > Předmět: Re: Routing problems > Datum: 18.2.2010 11:03:31 > > On Thu, 2010-02-18 at 07:31 +0100, j.halifax . wrote: > > Hi All, > > > > Could you please help me with routing in the LAN default GW box? > > > > I have > > eth0 connected to Internet > > eth2 to internal LAN 10.255.250.0 > > LAN default GW is 10.255.250.37 > > eth3 connected to other LAN > > > > Route in the default GW (10.255.250.37): > > > > Destination Gateway Genmask Flags Metric Ref Use > Iface > > 192.168.180.0 * 255.255.255.0 U 0 0 > > > 0 eth3 > > 10.255.250.0 * 255.255.255.0 U 0 0 > > > 0 eth2 > > link-local * 255.255.0.0 U 1003 > > 0 > 0 eth0 > > link-local * 255.255.0.0 U 1004 > > 0 > 0 eth2 > > link-local * 255.255.0.0 U 1005 > > 0 > 0 eth3 > > 172.17.0.0 192.168.180.100 255.255.0.0 UG0 00 > eth3 > > default dsl-router0.0.0.0 UG0 > > 0 > 0 eth0 > > > > >From the LAN default GW (10.255.250.37) > > - I can ping 172.17.1.50: > > PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > > 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms > > 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms > > > > >From other boxes in the same LAN (e.g. 10.255.250.38) > > - I cann't ping 172.17.1.50 > > - I cann't traceroute 172.17.1.50: It goes to LAN default GW > > 10.255.250.37 and then to its default GW dsl-router on eth0 > > instead of eth3 (so that the routing rule for 172.17.0.0 > > doesn't > > match for 172.17.1.50) > > > > Can anybody help pleasee? > > Thank you so much! > > jh > > > > Your problem has me stumped. > > The only thing I can think of is to ask how iptables is set up. > > I think you have iptables doing masquerading to the eth0 interface. > The masquerading shouldn't be the problem. > > Are you doing anything special with packets coming in eth2 in iptables? > > I assume 10.255.250.38 can ping the Internet so you have routing set up. > > I can't think of anything else to check at this moment. > > Hopefully others will have better suggestions and ideas where to look. > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Routing problems
Hi All, Could you please help me with routing in the LAN default GW box? I have eth0 connected to Internet eth2 to internal LAN 10.255.250.0 LAN default GW is 10.255.250.37 eth3 connected to other LAN Route in the default GW (10.255.250.37): Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.180.0 * 255.255.255.0 U 0 0 0 eth3 10.255.250.0 * 255.255.255.0 U 0 0 0 eth2 link-local * 255.255.0.0 U 1003 0 0 eth0 link-local * 255.255.0.0 U 1004 0 0 eth2 link-local * 255.255.0.0 U 1005 0 0 eth3 172.17.0.0 192.168.180.100 255.255.0.0 UG0 00 eth3 default dsl-router0.0.0.0 UG0 0 0 eth0 >From the LAN default GW (10.255.250.37) - I can ping 172.17.1.50: PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms >From other boxes in the same LAN (e.g. 10.255.250.38) - I cann't ping 172.17.1.50 - I cann't traceroute 172.17.1.50: It goes to LAN default GW 10.255.250.37 and then to its default GW dsl-router on eth0 instead of eth3 (so that the routing rule for 172.17.0.0 doesn't match for 172.17.1.50) Can anybody help pleasee? Thank you so much! jh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: OpenOffice and password protected encrypted .docx files?
> ...Since I don't have MS Office 2007 the question is whether > I can open the file at all? In such cases I ask the sender to export it as ".doc" and send it again. I do not accept M$' immoral pressure for buying unneeded new versions. > Původní zpráva > Od: Roger > Předmět: Re: OpenOffice and password protected encrypted .docx files? > Datum: 04.2.2010 10:41:08 > > On 02/04/2010 07:52 PM, Mike Cloaked wrote: > > Can anyone advise me on the following problem? > > > > I have been sent a .docx which was created in MS Office 2007, and encrypted > > with a password that is needed to open it. In the past if anyone sent me an > > open .docx file then OpenOffice in F12 would open it without any problems. > > However the password protected file appears not to be accessible in > > OpenOffice, and attempting to open the file does not ask for a password and > > won't play ball. Since I don't have MS Office 2007 the question is whether > > I can open the file at all? > > > > Can anyone suggest a solution? > > > > Thanks > > > Had the same problem a month ago researched and googled for days, the > only solution I found was to request the password. > Roger > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> I think that pptp is generally regarded as low quality, insecure vpn > tunnel and that Windows L2TP is a much better implementation as is openvpn. As for some external points of views I would agree, but I can not compare how they are made "inside". The necessity of having to install openvpn client on MSW makes its use inconvenient in that field. Have you any experience with openswan ? > > Microsoft has fixed Windows Server and improved security on the desktop > OS versions to a point where it is reasonable to use them... but I still > prefer Linux. I was speaking about my own experience only. Wherever I have been working in last 10 years (ISP, APS company, telecom) we had to ditch Windows to stop operation problems. Linux is nice and extremely reliable (as my example below documented). L:) > Původní zpráva > Od: Craig White > Předmět: Re: Connect Standard Windows VPN to Linux box > Datum: 15.1.2010 15:00:04 > > j.halifax . wrote: > >>I don't understand why. I tend to use RHEL or CentOS for servers so I > >>was unaware of this. > > > > > > Paul Horwatyh said (in https://bugzilla.redhat.com/show_bug.cgi?id=350381): > > > > === > > The poptop server has to the best of my knowledge never been packaged as > > part of Fedora. > > > > The client is commonly used for connecting to MS-based company VPNs and > > in some countries for ADSL client connections; there is not such a clear > > need > > > for the server since a better, more secure solution is available in the form > of > > openvpn. Having said that, if somebody was to package up poptop and > > volunteer > > > to maintain it in Fedora, I doubt that there would be any serious > > objections. > > === > > > > That's true, but if one wished to access openvpn server e.g. from Internet > Cafe > > (when he is on the leave or business trip), he would have to install the > > openvpn client there, right? - That would be hard. > > > > More, because Linux become much more reliable comparing to Windows, > > Windows are being ditched from server side fields. That's also our cause. > > We need to remove the all boxes of the Windows platform in the server > > side field. The reliability of Linux v. Windows become incomparable. > > > > (For example:I made some prepaid card solution for one ISP and 3.5 years > > after > > > I left the ISP they called me. They needed to add some function but nobody > knew > > where the solution was running because nobody has touched it ever. That's > > what > > > rathe none can experience with Windows.) > > I think that pptp is generally regarded as low quality, insecure vpn > tunnel and that Windows L2TP is a much better implementation as is openvpn. > > I don't necessarily have a 'cause' and I use Linux because it works, it > is free and it is generally easier to maintain. To some extent, > Microsoft has fixed Windows Server and improved security on the desktop > OS versions to a point where it is reasonable to use them... but I still > prefer Linux. > > Craig > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> I don't understand why. I tend to use RHEL or CentOS for servers so I > was unaware of this. Paul Horwatyh said (in https://bugzilla.redhat.com/show_bug.cgi?id=350381): === The poptop server has to the best of my knowledge never been packaged as part of Fedora. The client is commonly used for connecting to MS-based company VPNs and in some countries for ADSL client connections; there is not such a clear need for the server since a better, more secure solution is available in the form of openvpn. Having said that, if somebody was to package up poptop and volunteer to maintain it in Fedora, I doubt that there would be any serious objections. === That's true, but if one wished to access openvpn server e.g. from Internet Cafe (when he is on the leave or business trip), he would have to install the openvpn client there, right? - That would be hard. More, because Linux become much more reliable comparing to Windows, Windows are being ditched from server side fields. That's also our cause. We need to remove the all boxes of the Windows platform in the server side field. The reliability of Linux v. Windows become incomparable. (For example:I made some prepaid card solution for one ISP and 3.5 years after I left the ISP they called me. They needed to add some function but nobody knew where the solution was running because nobody has touched it ever. That's what rathe none can experience with Windows.) L:) > Původní zpráva > Od: Craig White > Předmět: Re: Connect Standard Windows VPN to Linux box > Datum: 15.1.2010 02:15:17 > > On Fri, 2010-01-15 at 09:07 +0800, Ed Greshko wrote: > > Chris Smart wrote: > > > 2010/1/15 j.halifax . : > > > > > >>> However under Fedora, I can't fund the pptpd package. > > >>> > > >> Yes. yum says me "No package pptpd available." :( > > >> Thank you. > > >> > > > > > > You can download the source yourself and build it: > > > http://poptop.sourceforge.net/ > > > > > > It has a sample pptpd.conf which you can edit. > > > > > > > > > > > I really don't understand the conundrum. > > > > The standard vpn server on a Windows box uses pptp. So, when I want my > > linux box to access a windows system I use a pptp client on my linux box > > to create a vpn tunnel to the windows system that is running a pptp server. > > > > When I want a windows system to access/create a vpn tunnel I have my > > linux box running the openvpn server and the windows box using an > > openvpn client. > > > > So, the question is simply "what side do you want to be the server, and > > what side the client". > > I think they want to actually set up a pptp server on Linux - c'est la > vie. Apparently pptpd has never been packaged in Fedora but it is > available as part of RHEL. > > https://bugzilla.redhat.com/show_bug.cgi?id=350381 > > I don't understand why. I tend to use RHEL or CentOS for servers so I > was unaware of this. > > Craig > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> So, the question is simply "what side do you want to be the server, and > what side the client". The server should run on Linux side. I believed that it implied from the Subject's "connect ... to Linux"; but I should say that explicitely. you are right. L:) > Původní zpráva > Od: Ed Greshko > Předmět: Re: Connect Standard Windows VPN to Linux box > Datum: 15.1.2010 02:09:13 > > Chris Smart wrote: > > 2010/1/15 j.halifax . : > > > >>> However under Fedora, I can't fund the pptpd package. > >>> > >> Yes. yum says me "No package pptpd available." :( > >> Thank you. > >> > > > > You can download the source yourself and build it: > > http://poptop.sourceforge.net/ > > > > It has a sample pptpd.conf which you can edit. > > > > > > > I really don't understand the conundrum. > > The standard vpn server on a Windows box uses pptp. So, when I want my > linux box to access a windows system I use a pptp client on my linux box > to create a vpn tunnel to the windows system that is running a pptp server. > > When I want a windows system to access/create a vpn tunnel I have my > linux box running the openvpn server and the windows box using an > openvpn client. > > So, the question is simply "what side do you want to be the server, and > what side the client". > > > -- > All that glitters has a high refractive index. > > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: TV over the internet
Thanx for your methodology! :)) Leos > Původní zpráva > Od: Ed Greshko > Předmět: Re: TV over the internet > Datum: 15.1.2010 02:02:29 > > j.halifax . wrote: > >> If you want a pure linux solution you'd first have to get a TV-Card for > >> your system with the ability to connect to a satellite receiver and then > >> use something like vlc to do the streaming within your LAN. I did that > >> a long time ago...so I can't really advise as to the set up. > >> > > > > Yes, that experience that you "can't really advise" I am looking for. > > I.e. which TV card works w/ vlc under fc12 well and so. : > > > This *may* help. > > I did my own research way back when. I first found out what I could > about TV cards in general. I found what chipsets were used most often. > I then looked in /lib/modules/`uname -r`/kernel/drivers/media/video to > see what modules were there and what chipsets were represented. > > At that time the best supported chipsets that were also easy to obtain > in Taiwan were Bt8XX. So, I went out and bought that and everything > worked just fine. I still use that in my RHELv4 system with xdtv. > > The info is out there. It may not exist on this list. :-) > > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> All those look like client packages for connecting _to_ a vpn server, > not creating one. I don't see any server there, of course Fedora might > just bundle it in ppp or something, I've no idea.. I was advised to try "openswan"... So I'll do. Thank you. Leos. > Původní zpráva > Od: Chris Smart > Předmět: Re: Connect Standard Windows VPN to Linux box > Datum: 15.1.2010 01:25:54 > > 2010/1/15 Craig White : > > try 'yum search pptp' > > > > Yeah, but it provides: > > NetworkManager-pptp.x86_64 : NetworkManager VPN plugin for pptp > pptp.x86_64 : Point-to-Point Tunneling Protocol (PPTP) Client > pptp-setup.x86_64 : PPTP Tunnel Configuration Script > > All those look like client packages for connecting _to_ a vpn server, > not creating one. I don't see any server there, of course Fedora might > just bundle it in ppp or something, I've no idea.. > > -c > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> try 'yum search pptp' Thanx, Carig, yum found it, so it should be included in the NM (which I don't use).: yum search pptp Loaded plugins: presto, refresh-packagekit = Matched: pptp NetworkManager-pptp.x86_64 : NetworkManager VPN plugin for pptp pptp.x86_64 : Point-to-Point Tunneling Protocol (PPTP) Client pptp-setup.x86_64 : PPTP Tunnel Configuration Script > > > > > > The > > > http://sawrub-blog.blogspot.com/2009/10/vpn-setup-using-pptp.html > > > describes the connecting as Linux box to Linux VPN server (if I > > > understand it correctly). No mention about MSW > > > > PPTP is the Microsoft VPN protocol, so creating a server on Linux will > > allow Windows users to connect to it. > > > > Under Debian it's a matter of: > > sudo apt-get install pptpd > > > > And setting up a username and password in /etc/ppp/chap-secrets. > > > > However under Fedora, I can't fund the pptpd package. > > try 'yum search pptp' > > Craig > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
> However under Fedora, I can't fund the pptpd package. Yes. yum says me "No package pptpd available." :( Thank you. Leos > Původní zpráva > Od: Chris Smart > Předmět: Re: Connect Standard Windows VPN to Linux box > Datum: 15.1.2010 00:46:40 > > 2010/1/15 j.halifax . : > > Thank you for your advise... > > > > The > > http://sawrub-blog.blogspot.com/2009/10/vpn-setup-using-pptp.html > > describes the connecting as Linux box to Linux VPN server (if I > > understand it correctly). No mention about MSW > > PPTP is the Microsoft VPN protocol, so creating a server on Linux will > allow Windows users to connect to it. > > Under Debian it's a matter of: > sudo apt-get install pptpd > > And setting up a username and password in /etc/ppp/chap-secrets. > > However under Fedora, I can't fund the pptpd package. > > -c > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: TV over the internet
> If you want a pure linux solution you'd first have to get a TV-Card for > your system with the ability to connect to a satellite receiver and then > use something like vlc to do the streaming within your LAN. I did that > a long time ago...so I can't really advise as to the set up. Yes, that experience that you "can't really advise" I am looking for. I.e. which TV card works w/ vlc under fc12 well and so. :) Thank you. Leos > Původní zpráva > Od: Ed Greshko > Předmět: Re: TV over the internet > Datum: 15.1.2010 00:43:39 > > j.halifax . wrote: > > Thank you for your response... > > > > Probably I didn't say what I want clearly enough. I want to receive > > TV from satellite and stream (re-broadcast) it in my LAN. :) > > > As mentioned by the earlier respondent, that can be achieved with a > slingbox. > > I have both a SlingBox hosted in the US so I can watch TV from the US as > well as a SlingBox here in Taiwan so my brother-in-law can watch Taiwan > TV in Abu Dhabi. But, I also watch that "local" SlingBox via wifi at > times. So, it is "streamed" within my LAN. Yes, it is a Windows > solution. I confess to using an alternate O/S when it fits my needs. > > If you want a pure linux solution you'd first have to get a TV-Card for > your system with the ability to connect to a satellite receiver and then > use something like vlc to do the streaming within your LAN. I did that > a long time ago...so I can't really advise as to the set up. > > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: TV over the internet
Thanx for your kind info. :) > Původní zpráva > Od: Ed Greshko > Předmět: Re: TV over the internet > Datum: 15.1.2010 00:22:58 > > Mark Mahabir wrote: > > > > The SlingPlayer software is free, officially supported for Windoze and > > Mac and possibly maybe you might be able to get it running via Wine, > > see here: > > > > > http://www.slingcommunity.com/article/17253/How-To-Run-SlingPlayer-on-Linux-OS/ > > > > YMMV. > > > FYI, that information is outdated. With the newer versions of > SlingPlayer it is not possible to run it under wine. > > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: TV over the internet
Thank you for your response... Probably I didn't say what I want clearly enough. I want to receive TV from satellite and stream (re-broadcast) it in my LAN. :) Leos > It's not really linux supported but I have these guys hosting a > Slingbox for me in the US: > > http://statesidetv.net > > The SlingPlayer software is free, officially supported for Windoze and > Mac and possibly maybe you might be able to get it running via Wine, > see here: > > http://www.slingcommunity.com/article/17253/How-To-Run-SlingPlayer-on-Linux-OS/ > > YMMV. > > Mark > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Connect Standard Windows VPN to Linux box
Thank you for your advise... The http://sawrub-blog.blogspot.com/2009/10/vpn-setup-using-pptp.html describes the connecting as Linux box to Linux VPN server (if I understand it correctly). No mention about MSW Leos -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Connect Standard Windows VPN to Linux box
Hi All, Can anyone advice what I need to do in Linux server to be able to connect to it by means of the Windows standard VPN connection? Thank you so much... Regards, hj -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Sat TV in private LAN
Hi all, Can anyone recommend a solution based on Fedora 12 for streaming satellite channels in a private LAN? Thanks. Regards JH -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: LAN Card doesn't activate
Hi Hugh, Thank you for your response and excuse for insufficient info... I'll add next details in your text. Regards, jh > Původní zpráva > Od: D. Hugh Redelmeier > Předmět: Re: LAN Card doesn't activate > Datum: 11.1.2010 02:10:49 > > | From: j.halifax . > > | Doesn't anybody know why my LAN Cards don't get active after rebooting > | despite of having the check-box for automated activation checked? > | > | After every reboot I have to open Network option in System->Admin menu > | and activate cards manual way. > > You haven't told us much about your setup. Yes, sorry, I believed that it is some basic mistake I have done. > > Assuming you are using Fedora, what version are you using? uname -r tells me 2.6.31.9-174.fc12.x86_64 > > Why do you say "cards"? How many do you have? In how many systems? I have 3 cards to Internet DSL and 2 different networks > > Are your cards managed by Network Manager, or by the old fashioned > system-config-network etc. scripts? I find that the two systems can > interfere. I don't use Network manager, LAN devices are configured as it follows: eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:247782 errors:0 dropped:0 overruns:0 frame:0 TX packets:211249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:156440806 (149.1 MiB) TX bytes:50247350 (47.9 MiB) Interrupt:21 Base address:0xca00 "cat /etc/sysconfig/networking/devices/ifcfg-eth0" gives: # VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] DEVICE=eth0 ONBOOT=yes BOOTPROTO=none TYPE=Ethernet NM_CONTROLLED=no IPV6INIT=no USERCTL=no NAME="System eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 HWADDR=00:1b:11:b1:5d:0d PEERROUTES=yes IPADDR=195.39.130.92 NETMASK=255.255.255.0 GATEWAY=195.39.130.89 DNS2=195.226.224.72 DNS1=195.226.224.74 eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36 inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0 inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:761309 errors:0 dropped:0 overruns:0 frame:0 TX packets:195979 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:84964475 (81.0 MiB) TX bytes:148972906 (142.0 MiB) Interrupt:22 Base address:0xa900 "cat /etc/sysconfig/networking/devices/ifcfg-eth2" gives: DEVICE=eth2 BOOTPROTO=none NETMASK=255.255.255.0 TYPE=Ethernet HWADDR=00:19:5b:38:b7:36 IPADDR=10.255.250.37 NM_CONTROLLED=no IPV6INIT=no ONBOOT=yes USERCTL=no DNS2=195.226.224.72 DNS1=195.226.224.74 GATEWAY=195.39.130.89 MTU=1500 eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4 inet addr:172.16.110.3 Bcast:172.16.110.255 Mask:255.255.255.0 inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47237 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4589511 (4.3 MiB) TX bytes:3610 (3.5 KiB) Interrupt:18 Base address:0x6800 "cat /etc/sysconfig/networking/devices/ifcfg-eth3" gives me: # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. DEVICE=eth3 BOOTPROTO=none NETMASK=255.255.255.0 TYPE=Ethernet HWADDR=00:1b:11:b1:1c:d4 IPADDR=172.16.110.3 NM_CONTROLLED=no IPV6INIT=no ONBOOT=yes USERCTL=no loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:11088 errors:0 dropped:0 overruns:0 frame:0 TX packets:11088 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:942300 (920.2 KiB) TX bytes:942300 (920.2 KiB) > > > On three notebooks, I use Network Manager: it is better at handling > changes in connectivity. > > For some reason, the notebook running Fedora 11 and the one running > Fedora 12 don't automatically connect to the wired network: I have to > poke the NetworkManager icon to get a menu and select from that menu > the wired interface. For wireless, that would make sense, but for > wired that seems silly: after all I wired the connection. Isn't it similar to my problems? > > > Does this correspond to what you are experiencing? I guess that it does. :( > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuid
