I'm on Suse 9.2 Pro with all the latest updates. When I plug in a Linksys 802.11B wireless USB, the new hardware is detected and configured OK. There's a signal level reported. But it will not access the net beyond there. The router reports two MAC addresses for this machine, one for the wireless, one for the wired card and assigns two IP nos..

iwconfig thinks it's OK, it can see the router but won't get through to the world. I tried both Managed and Ad-Hoc. I tried disabling the hardwired card, so Suse would only see the wireless but that made no difference.



wlan0 IEEE 802.11-DS ESSID:"WLAN" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point: 00:30:BD:C4:BD:5C
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption keyff
Power Managementff
Link Quality=0/0 Signal level=90/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

linux:/home/jfb # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

Is the router using wep or wpa security?
Is the router using any mac filtering?
Appears the wlan is not getting an IP from the access point.
Manually configure one use the following based on info above.
IP 192.168.2.10
Subnet 255.255.255.0
Gateway 192.168.2.1
DNS 192.168.2.1 or use ones from provider.
Then take eth0 down and then bring eth1 up.
Lets go from there.

Brian1

It's a Belkin F5D6231 with WEP and MAC filtering
I disabled the eth0 card once already, didn't seem to make any difference to the wireless connection.