[SLE] new at wireless configuration... but keep trying!
Hi all out there, In spite of all the received help, I'm not able yet of getting connected my Linksys Wireless card. Surely I'm wrong at several points or I'm missing something important. Please, could you be so kind as to take a look to the following summary and give me some clue to try to work around this issue? * The computer is a Toshiba S1900-203 running Open SuSE 10.1. * The wireless card, a PCMCIA card Linksys #[WPC54G v2] * The "windows" driver is installed and listed by ndiswrapper -l citlali:~ # ndiswrapper -l Installed drivers: lstinds driver installed, hardware present citlali:~ # * iwconfig shows citlali:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr:4096 B Fragment thr:4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 * The power led is green at start up: ndiswrapper has been added to "MODULES_LOADED_ON_BOOT="" " line in /etc/sysconfig/kernel. * By using YaST - Network Devices - Network Card - Traditional Method with ifup, I've added a new Wireless device and wrote down ndiswrapper as Module name (PCMCIA, USB are not marked) and configured it with a static IP address (I need it instead of a DHCP assigned one). The wireless device is listed as active in the devices network tools list and I can ping the IP address manually assigned to it but any access to an IP outside the private network is prevented! Please, why? No link to any available wireless access point is established. ifconfig gives the following... citlali:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:02:3F:79:60:BC inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::202:3fff:fe79:60bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:482 errors:0 dropped:0 overruns:0 frame:0 TX packets:429 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:302659 (295.5 Kb) TX bytes:86667 (84.6 Kb) 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:42220 errors:0 dropped:0 overruns:0 frame:0 TX packets:42220 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2114866 (2.0 Mb) TX bytes:2114866 (2.0 Mb) wlan0 Link encap:Ethernet HWaddr 00:12:17:DF:D9:24 inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::212:17ff:fedf:d924/64 Scope:Link UP BROADCAST RUNNING 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) Interrupt:5 Memory:44020000-44022000 I have to removed the newly created wireless card to regain access to Internet. Please, could you help me to get this wireless card working? 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
On Monday 12 June 2006 3:31 pm, Ricardo Rodríguez - XEN wrote:
Hi all out there,
In spite of all the received help, I'm not able yet of getting connected my Linksys Wireless card. 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
--
Jerry Feldman
On Mon, 2006-06-12 at 16:12 -0400, Jerry Feldman wrote:
On Monday 12 June 2006 3:31 pm, Ricardo Rodríguez - XEN wrote:
Hi all out there,
In spite of all the received help, I'm not able yet of getting connected my Linksys Wireless card. 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
This issue has already been addressed in a previous message. It seems that the problem arises while having both interfaces active on the same network. Disabling wlan0 causes eth0 to work fine. I have not gotten wlan0 up and running yet...
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.
No way. I've already tried that. I've one of the available access points with DHCP enabled. Windows boxes have no problems to get a lease. Linux box fails. Here you have ifrenew wlan0 output... citlali:~ # ifrenew wlan0 wlan0 device: Texas Instruments ACX 111 54Mbps Wireless Interface Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding. citlali:~ #
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
modprobe -r ndiswrapper has hanged the computer several times. When it works, I've been not able yet to find a path for the failure, this command, dmesg -c and ndiswrapper show nothing in the terminal window. Please, where must I look for this messages? Sorry for my lack of skills! I'm afraid Linux is still a bit far from my capacity. Thank you so much for your help, Ricardo -- Ricardo Rodríguez Your XEN ICT Team -- 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
On Mon, 2006-06-12 at 21:31 +0200, Ricardo Rodríguez - XEN wrote:
Hi all out there,
In spite of all the received help, I'm not able yet of getting connected my Linksys Wireless card. Surely I'm wrong at several points or I'm missing something important. Please, could you be so kind as to take a look to the following summary and give me some clue to try to work around this issue?
* The computer is a Toshiba S1900-203 running Open SuSE 10.1.
* The wireless card, a PCMCIA card Linksys #[WPC54G v2]
* The "windows" driver is installed and listed by ndiswrapper -l
citlali:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:02:3F:79:60:BC inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::202:3fff:fe79:60bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:482 errors:0 dropped:0 overruns:0 frame:0 TX packets:429 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:302659 (295.5 Kb) TX bytes:86667 (84.6 Kb)
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:42220 errors:0 dropped:0 overruns:0 frame:0 TX packets:42220 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2114866 (2.0 Mb) TX bytes:2114866 (2.0 Mb)
wlan0 Link encap:Ethernet HWaddr 00:12:17:DF:D9:24 inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::212:17ff:fedf:d924/64 Scope:Link UP BROADCAST RUNNING 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) Interrupt:5 Memory:44020000-44022000
I have to removed the newly created wireless card to regain access to Internet.
Please, could you help me to get this wireless card working? Thanks!!!
Having both eth0 and wlan0 active at the same time on the same network can cause routing problems. Disable the eth0 config and use only the wlan0 connection and see what happens. Use rcnetwork restart to try and reset the routing tables. Show us the results of route -n as well with only the wlan0 active. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- 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
On Mon, 2006-06-12 at 18:42 -0400, Ken Schneider wrote:
Having both eth0 and wlan0 active at the same time on the same network can cause routing problems. Disable the eth0 config and use only the wlan0 connection and see what happens.
I've read before that two interfaces on the same network can cause routing problems, but I'd no taken into account it in this case. Sorry. wlan0 seems it doesn't work.
Use rcnetwork restart to try and reset the routing tables. Show us the results of route -n as well with only the wlan0 active.
Once I disable eth0 (ifdown eth0), route -n shows:
citlali:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
citlali:~ #
rcnetwork restart brings up eth0 interface. I'm guessing some more
previous steps are needed to prevent the interface to bring up after
this command. In any case, after a rcnetwork restart and a ifdown eth0
the route -n output is the same.
I get this results with the same configuration that tells me...
citlali:~ # ifstatus wlan0
wlan0 device: Texas Instruments ACX 111 54Mbps Wireless
Interface
wlan0 dhcpcd is still waiting for data
wlan0 is up
5: wlan0:
participants (4)
-
Jerry Feldman
-
Ken Schneider
-
Ricardo Rodríguez
-
Ricardo Rodríguez - XEN