Re: [SLE] new at wireless configuration... but keep trying!
Jerry Feldman
12/6/2006 22:12 >>> As far as I can see it does appear to be working. One thing I found is that when you have BOTH the NIC and the Wireless configured, the kernel routing table does not have the default route.
Here is a procedure you can use: bring up a terminal window, and as root: ifdown eth0 ifdown wlan0 ifup wlan0 Then, take a look at the routing table: netstat -nr, and you should see a default route
or, another way to see if the wireless is working, temporarily configure it for DHCP and see if the router gives it an ip address.
In any case, if neither of these work, take a look at what dmesg says when loading ndiswrapper. This is what shows up on my system. (You can force this by unloading ndiswrapper (modprobe -r ndiswrapper), run dmesg -c to clear its buffer, then load ndiswrapper (modprobe ndiswrapper). diswrapper version 1.10 loaded (preempt=no,smp=no) ndiswrapper (load_pe_images:573): fixing KI_USER_SHARED_DATA address in the driver ndiswrapper: driver bcmwl5 () loaded ndiswrapper: using irq 225 wlan0: vendor: '' wlan0: ndiswrapper ethernet device 00:14:a5:4d:9e:40 using driver bcmwl5, 14E4:4319.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Hi, Jerry Thanks for the input. First of all I would like to understand, if possible, what is going on with the default route. Is it my fault at any extent that when wlan0 is up the route doesn't work? ifdown eth0 ifdown wlan0 ifup eth0 Recovers default route functionality. But netstat -nr shows the default route both with wlan0 up or down. Here the sequence: ifdown eth0 ifdown wlan0 ifup eth0 citlali:~ # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.100 0.0.0.0 UG 0 0 0 eth0 citlali:~ # ping www.cesga.es PING www.cesga.es (193.144.34.128) 56(84) bytes of data. 64 bytes from 193.144.34.128: icmp_seq=1 ttl=53 time=82.1 ms citlali:~ # ifup wlan0 wlan0 device: Texas Instruments ACX 111 54Mbps Wireless Interface wlan0 warning: using NO encryption SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set citlali:~ # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.100 0.0.0.0 UG 0 0 0 wlan0 citlali:~ # ping www.cesga.es PING www.cesga.es (193.144.34.128) 56(84) bytes of data.
From citlali.xen.net (192.168.1.41): icmp_seq=2 Destination Host Unreachable
As far as I can see here, in both cases, wlan0 up and down, the default route is present, but it doesn't work when wlan0 is up. I've not moved ahead yet to dmesg alternative just trying to work out this issue first. Please, does this any sense for you? Thanks!!! On the other hand, I've also problems with hibernate/suspend options when wlan0 is up or has been up at any time during the computer functioning. I don't know if broth symptoms could have a common root. Any new input will be welcome! Thanks. All the best, Ricardo -- Ricardo Rodríguez XEN, Resources Management -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (1)
-
Ricardo Rodríguez - XEN