Sorry, I forget to give the essential information:
It’s a quite old desktop computer (Intel Pentium 4 @ 2 GHz, essentially a modified HP VL420) with 768 MBytes of RAM.
This computer will be a third computer at home, put in a place where I can’t pass a CAT5 cable. (I know I can use Ethernet over the power cable adapters, but I want to learn some Linux, too).
I use the ifup method (with YaST2) because in the Network Manager everything was grayed out. Now I understand that people can choose one method or another.
I use the KDE 4 desktop which came with the standard installation of OpenSUSE 11.2.
The USB adapter is working fine on an old laptop with Windows 2000.
So it must be in the network config. First do this:
Go into Yast, Network Settings and disable ipV6. Also check in the config of the wireless card, if it’s set to start at boottime. Configure it to use DHCP, leave all automatic.
Please let us know, the card shows up, so IMHO we should be able to get this working.
So, I don’t know why, but now I’m connected to my AP. But DHCP is unable to work for the wireless connection (it was working fine for the wired connection).
I tried to change some settings in Yast (Network card setup) like:
changed from DHCP both versions 4 and 6 to 4 only (like the ethernet card)
adding ndiswrapper in the module name box in the Kernel Module.
The light on the device is now blinking (before it was lit continously)
suse112:/home/robert # rcnetwork restart
Shutting down network interfaces:
eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
eth0 done
wlan0 name: Silicon Integrated WLAN controller
wlan0 done
Shutting down service network . . . . . . . . . done
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
eth0 Starting DHCP4 client. . . . . . . .
eth0 DHCP4 continues in background
eth0 waiting
wlan0 name: Silicon Integrated WLAN controller
wlan0 warning: using NO encryption
command 'iwconfig wlan0 ap 9BoxRobert' returned
Interface wlan0 doesn't support IP addresses
wlan0 Interface doesn't support IP addresses
Error for wireless request "Set AP Address" (8B14) :
invalid argument "9BoxRobert".
wlan0 done
Setting up service network . . . . . . . . . . done
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
suse112:/home/robert # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"**9BoxRobert**"
Mode:Managed Frequency:2.412 GHz Access Point: 00:25:15:10:F1:B8
Bit Rate=54 Mb/s Tx-Power:17 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:31/100 Signal level:-76 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
suse112:/home/robert # rcnetwork status
Checking optional network interfaces:
eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
eth0 waiting
wlan0 name: Silicon Integrated WLAN controller
wlan0 DHCP4 client NOT running
wlan0 IEEE 802.11g ESSID:"9BoxRobert"
Mode:Managed Frequency:2.412 GHz Access Point: 00:25:15:10:F1:B8
Bit Rate=54 Mb/s Tx-Power:17 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:46/100 Signal level:-66 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wlan0 dead
Checking mandatory network interfaces:
lo
lo IP address: 127.0.0.1/8
secondary lo IP address: 127.0.0.2/8
lo running
Checking service network . . . . . . . . . . . running
It’s strange that in rcnetwork status it’s telling me: wlan0 DHCP4 client NOT running
But the worst is the result of rcnetwork restart :
*wlan0 Interface doesn’t support IP addresses
Error for wireless request “Set AP Address” (8B14) :
invalid argument “9BoxRobert”.
*
The SSID “9BoxRobert” should be good ! It’s even detected in Yast, in Network Manager.
Maybe my Wi-Fi adapter isn’t compatible with Linux after all …
ran into a somewhat similar problem with being unable to assign an AP to wlan0, same error (interface wlan0 doesnt support ip addresses). After not finding a **** thing on that very simple problem, I was able to fix it by retyping the ap, this time remembering to include the apparently crucial :'s (ie, xx:xx:xx:xx:xx:xx vs xxxxxx…). My guess is that the error we were getting is iwconfig’s polite but not very informative way of saying ‘that isn’t formatted like an AP address, so I’m going to assume you were trying to assign an IP.’
not especially relevant, but this was the first page that came up when I searched for that error. Hope it helps someone.