LinHES Forums http://forum.linhes.org/ |
|
Wireless / TV card conflict - sit0? R5A30.5 http://forum.linhes.org/viewtopic.php?f=2&t=8455 |
Page 1 of 1 |
Author: | parkinpants [ Sun Feb 12, 2006 8:35 am ] |
Post subject: | Wireless / TV card conflict - sit0? R5A30.5 |
Hi, I've been struggling to get a comfortable wifi setup on my via epia mII mini-itx system for some time now. My current problem is as follows, trial and error trauma in chronologocal order. 1. Tv card is set to 192.168.0.1 on mythtv-setup by default, this appears with 'static settings' under sit0 in the /etc/network/interfaces file 2. LAN router is at 192.168.0.1 3. I am using ndiswrapper for wifi 4. Tv works 5. If I setup my wifi card as per... ifup wlan0 iwlist wlan0 scan iwconfig wlan0 essid NETWORKNAME dhclient wlan0 ... then I see 192.168.0.2 successfully registered as the LAN address for mythbox on ifconfig 6. However, even though it says "bound to 192...etc), wireless doesn't actually work, if i do ping www.google.com i get nothing 7. The same thing happens if I have eth0 identified in the /interfaces file (even though not physicall connected). It is as if wlan0 only works if it is the only registered device in the /interfaces file (other than lo) 8. This can be solved by commenting out the sit0 static settings on the /interfaces file an then repeating wifi steps above. 9. However if I do this, then Tv doesn't work. I get - "the mythbackend is not running..check the IP address..etc" 10. If i now do ifdown sit0, and then do "iwlist wlan0 scan" i get "operation not permitted: wlan0 doesn't support scanning". 11. I then realised LAN and sit0 are both on 192.168.0.1, so I changed sit0 to 192.167.0.1 in mythtv-setup and /interfaces. Now the tv still won't work, but not with the error message - it just flickers for a sec and then returns back to the Main Menu. 12. What exactly is sit0? This wasn't identified on ifconfig with previous versions of KM. I just used to have "lo" for the mythbackend/tv server. 13. Bottom line, I can only have Tv or Wi-fi, not both. I appreciate I don't fully understand what lo and sit0 are so maybe that is my downfall. 14. I have tried using netcardconfig to set my /interfaces file but no solution there. My /interfaces file at the moment. Code: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo sit0 wlan0 iface lo inet loopback #iface eth0 inet static # address 192.168.0.1 # netmask 255.255.255.0 # network 192.168.0.0 # broadcast 192.168.0.255 # gateway 192.168.0.254 iface sit0 inet static address 192.167.0.1 netmask 255.255.255.0 network 192.167.0.0 broadcast 192.167.0.255 gateway 192.167.0.254 iface wlan0 inet dhcp Current output of "ifconfig" Code: lo Link 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:595 errors:0 dropped:0 overruns:0 frame:0 TX packets:595 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:249809 (243.9 KiB) TX bytes:249809 (243.9 KiB) sit0 Link encap:IPv6-in-IPv4 inet addr:192.167.0.1 Mask:255.255.255.0 inet6 addr: ::127.0.0.1/96 Scope:Unknown inet6 addr: ::192.168.0.2/96 Scope:Compat inet6 addr: ::192.168.0.1/96 Scope:Compat UP RUNNING NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:131 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:40:F4:D6:44:FB inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fed6:44fb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:618038 errors:0 dropped:0 overruns:0 frame:0 TX packets:1152496 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43493632 (41.4 MiB) TX bytes:1667865997 (1.5 GiB) Interrupt:12 Memory:e1000000-e1010000 Current output of iwconfig Code: lo no wireless extensions.
eth0 no wireless extensions. sit0 no wireless extensions. Warning: Driver for device wlan0 has been compiled with version 19 of Wireless Extension, while this program supports up to version 17. Some things may be broken... wlan0 IEEE 802.11b ESSID:"PARKYSPLACE" Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:B6:00:BC Bit Rate:18 Mb/s Sensitivity=-200 dBm RTS thr:2346 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-89 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Please help geniuses. |
Author: | nickread [ Sun Feb 12, 2006 10:46 pm ] |
Post subject: | |
*Warning-limited knowledge* l0 is the 'loopback interface' and is basically just an easy way of referring to the local machine without knowing anything else about it. So if you frontend is on the same machine as your backend, then you would (by default) use l0 (or 127.0.0.1) from the frontend to connect to the backend. sit0 is an IPV6 interface. Its there because IPV6 support is compiled into your kernal I think. You probably don't need it. You may have a default gateway/routing issue? |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |