LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 10-02-2005, 06:13 AM   #1
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Rep: Reputation: 0
linksys WAG56G Access Point not reachable via NDIS/WUSB54G adapter


Hiya all,

Spec is suse 9.3 kernel 2.6.11.4-20a-default, ndiswrapper-1.4rc1, xp adapter driver WUSB54Gv4_20050321(driver name rt2500usb), Wireless usb network adapter Linksys WUSB54Gv4. WAG54G Wireless Router / access point.

The config *appears* ok (correct me if i'm wrong..) , and I think (?) the adapter can get the broadcast ESSID, but it just can't connect to it.

To keep things simple, there is not security on the WAG54G. I also know the xp network driver and usb adapter hardware work perfectly together - got them going in winblows in 1 minute flat, talking perfectly to the WAG54G.

Trace as below.

Other things I have tried:
a) other ndiswrappers (1.2, 1.4rc3), but they go into a nasty loop when attempting the modprobe.
b) gazing pensively into the mid-distance in strokey-beard stylee for many hours
c) ramming my head against a brick wall at high velocity

Any ideas please ? I'm almost there.. I can feel it in my bones. Those that aren't smashed to pieces from c) above, that is.

Thanks in advance, (advanced geek-speak below..)
----------------------------------------------------------------------

Code:
# ndiswrapper -l
Installed ndis drivers:
rt2500usb               driver present, hardware present

# modprobe ndiswrapper
Oct  2 12:10:48 linux kernel: usb 3-5: new high speed USB device using ehci_hcd and address 3
Oct  2 12:11:17 linux kernel: ndiswrapper: unsupported module, tainting kernel.
Oct  2 12:11:17 linux kernel: ndiswrapper version 1.4rc1 loaded (preempt=no,smp=no)
Oct  2 12:11:17 linux kernel: ndiswrapper: driver rt2500usb (Linksys,01/07/2005, 2.00.00.0000) loaded
Oct  2 12:11:17 linux kernel: wlan0: ndiswrapper ethernet device 00:12:17:5f:66:02 using driver rt2500usb, 13B1:000D.0.conf
Oct  2 12:11:17 linux kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Oct  2 12:11:17 linux kernel: usbcore: registered new driver ndiswrapper
Oct  2 12:11:28 linux kernel: wlan0: no IPv6 routers present

#dmesg
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
subfs 0.9
bootsplash: status on console 0 changed to on
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=8 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87
thinkpad: unsupported module, tainting kernel.
thinkpad: I have registered to handle major: 10 minor: 170.
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=9 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87
usb 3-5: new high speed USB device using ehci_hcd and address 3
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=192.168.1.255 LEN=250 TOS=0x00 PREC=0x00 TTL=64 ID=1 DF PROTO=UDP SPT=138 DPT=138 LEN=230
ndiswrapper: unsupported module, tainting kernel.
ndiswrapper version 1.4rc1 loaded (preempt=no,smp=no)
ndiswrapper: driver rt2500usb (Linksys,01/07/2005, 2.00.00.0000) loaded
wlan0: ndiswrapper ethernet device 00:12:17:5f:66:02 using driver rt2500usb, 13B1:000D.0.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
usbcore: registered new driver ndiswrapper
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=73 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=53
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=73 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=53
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=73 TOS=0x00 PREC=0x00 TTL=255 ID=1 DF PROTO=UDP SPT=5353 DPT=5353 LEN=53
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=73 TOS=0x00 PREC=0x00 TTL=255 ID=2 DF PROTO=UDP SPT=5353 DPT=5353 LEN=53
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=3 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87
wlan0: no IPv6 routers present
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=8 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=9 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.102 DST=192.168.1.255 LEN=250 TOS=0x00 PREC=0x00 TTL=64 ID=2 DF PROTO=UDP SPT=138 DPT=138 LEN=230

# iwlist wlan0 scanning
Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0     Scan completed :
          Cell 01 - Address: 00:13:10:0C:8F:81
                    ESSID:"linksys"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.462 GHz (Channel 11)
                    Quality:0/100  Signal level:-39 dBm  Noise level:-256 dBm
                    Encryption key:off
                    Bit Rate:1 Mb/s
                    Bit Rate:2 Mb/s
                    Bit Rate:5.5 Mb/s
                    Bit Rate:11 Mb/s
                    Bit Rate:6 Mb/s
                    Bit Rate:9 Mb/s
                    Bit Rate:12 Mb/s
                    Bit Rate:18 Mb/s
                    Bit Rate:24 Mb/s
                    Bit Rate:36 Mb/s
                    Bit Rate:48 Mb/s
                    Bit Rate:54 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0


# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:12:17:5F:66:02
          inet6 addr: fe80::212:17ff:fe5f:6602/64 Scope:Link
          UP BROADCAST NOTRAILERS 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)

# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"linux"
          Mode:Auto  Frequency:2.412 GHz  Access Point: 00:00:00:00:00:00
          Bit Rate=11 Mb/s   Tx-Power:20 dBm   Sensitivity=-121 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:135/154  Noise level:0/154
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

linux:~ # ping linuxquestions.org

ping: unknown host linuxquestions.org
--------------------------------
So, iwlist succeeds in getting the ESSID of the access point 'linksys', but iwconfig then reports all '0's for the address, and a susbsequent ping to this site fails (boo-hisss...). I have set the ESSID to 'any' (rather than the real essid) to prove that iwscan is indeed picking up the correct id from the network... which it is.
 
Old 10-02-2005, 08:34 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
So, iwlist succeeds in getting the ESSID of the access point 'linksys', but iwconfig then reports all '0's for the address, and a susbsequent ping to this site fails (boo-hisss...). I have set the ESSID to 'any' (rather than the real essid) to prove that iwscan is indeed picking up the correct id from the network... which it is.
Maybe I'm misunderstanding your post, but you seem to imply that because iwlist sees an AP, iwconfig will configure itself. It doesn't happen that way. Iwlist is just a tool to tell you what the world around you looks like, it doesn't actually share that information with any other tool. So the first step is to use iwconfig to set the SSID and WEP key (if you use one). Once you've done that (and the output of iwconfig shows it sees the AP) you need to request an IP address using DHCP or assign one using ifconfig. I think Suses uses dhclient to request an IP so the command would look something like:

dhclient wlan0

It also may use dhcpcd, in which case the command would be

dhcpcd wlan0


Setting a static IP is a touch more complicated, but basically you set the IP address with ifconfig, and then you need to set a gateway (your router essentially) using the route command.


By the way, of the other approaches you've tried, I'd try to cut back on C unless you own stock in pain relief companies.
 
Old 10-02-2005, 09:46 AM   #3
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Original Poster
Rep: Reputation: 0
Hangdog - many thanks for taking the time to reply :-). I have now (using yast) explicitly set the ESSID 'linksys' , and now iwconfig shows the new value 'linksys'. However, the Access Point address still showing zeros (is this normal !?)...

sit0 no wireless extensions.

eth0 no wireless extensions.

Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0 IEEE 802.11g ESSID:"linksys" Nickname:"linux"
Mode:Auto Frequency:2.462 GHz Access Point: 00:00:00:00:00:00
Bit Rate=11 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption keyff
Power Managementff
Link Quality:100/100 Signal level:-34 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

iwlist is still sure something is out there though..

# iwlist wlan0 scanning
Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0 Scan completed :
Cell 01 - Address: 00:13:10:0C:8F:81
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:0/100 Signal level:-34 dBm Noise level:-256 dBm
Encryption keyff
Bit Rate:1 Mb/s
Bit Rate:2 Mb/s
Bit Rate:5.5 Mb/s
Bit Rate:11 Mb/s
Bit Rate:6 Mb/s
Bit Rate:9 Mb/s
Bit Rate:12 Mb/s
Bit Rate:18 Mb/s
Bit Rate:24 Mb/s
Bit Rate:36 Mb/s
Bit Rate:48 Mb/s
Bit Rate:54 Mb/s
Extra:bcn_int=100
Extra:atim=0


Having configured the yast wireless to tell it that for this device, get the IP from a dhcp server, ifup seems to start a dhcp client automatically for me, which then gets bored as it can't get one.

#ifup wlan0
wlan0
wlan0 configuration: wlan-bus-usb
wlan0 warning: using NO encryption
Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding.

Finally, the messages log is showing some interested ndiswrapper messages, not sure if these are relevant or not. They appear one every few seconds. i've googled them and come up with nothing at all.

Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 253(36)
Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 253(33)
Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 254(36)
Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 254(33)
Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 255(36)
Oct 2 16:05:48 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 255(33)
Oct 2 16:05:49 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 256(36)
Oct 2 16:05:49 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 256(33)
Oct 2 16:05:52 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 257(36)
Oct 2 16:05:52 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 257(33)
Oct 2 16:05:53 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 258(36)
Oct 2 16:05:53 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 258(33)
Oct 2 16:05:55 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 259(36)
Oct 2 16:05:55 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 259(33)
Oct 2 16:05:57 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 260(36)
Oct 2 16:05:57 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 260(33)
Oct 2 16:05:58 linux kernel: wlan0: no IPv6 routers present
Oct 2 16:06:00 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 261(36)
Oct 2 16:06:00 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 261(33)
Oct 2 16:06:16 linux kernel: ndiswrapper (NdisAllocateBuffer:1079): pool d1be1be0 is full: 262(36)
Oct 2 16:06:16 linux kernel: ndiswrapper (NdisAllocatePacket:1303): pool d1be1c00 is full: 262(33)

Any further thoughts please ?
 
Old 10-02-2005, 10:11 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
However, the Access Point address still showing zeros (is this normal !?)...
No, it should be showing a MAC address. The fact that it is all zeros suggests that it really hasn't connected, despite the signal strength being 100.

I'm also going to suggest that for now, you don't use Yast. Graphical front-ends like Yast can cover up valuable information.

From a console, su to root and try to set the SSID with iwconfig. You also might try switching to mode from Auto to Managed (also done using iwconfig). Sometimes (and I haven't really figured out why) trying to set the SSID a few times in a row fails at first, but then sets it. You might try issuing the command 2 or 3 times and see if that gets it to pick up the access point. By the way, I'm assuming you're not running WEP encryption on the access point. Is that true or do we need to set a WEP key?

I'm also going to suggest that you use an older version of ndiswrapper. My personal opinion is that the last couple of rc versions have caused more problems than they have solved. I'd start with 1.2 and see if that works better. If you do this, make sure you uninstall the rc version before installing the older version. I believe make uninstall works for ndiswrapper (at least after 1.0 or 1.1), but there are also uninstall instructions on the ndiswrapper wiki (see my sig for the link).
 
Old 10-02-2005, 10:21 AM   #5
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Original Poster
Rep: Reputation: 0
Excellent - many thanks. I'll plough through that lot now.
 
Old 10-02-2005, 11:44 AM   #6
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Original Poster
Rep: Reputation: 0
I tried bypassing yast and doing it from the command line (using iwconfig to set SSID and mode), multiple times to get it to 'hook in', but to no avail.

I did a full deinstall as per ndis wiki site, then installed ndis1.2. This fails at an earler stage. I am able to register the driver successfully, but modprobe goes into an infinite loop spewing out messages like these at 3 per second.

Oct 2 18:08:30 linux kernel: ndiswrapper: unsupported module, tainting kernel.
Oct 2 18:08:30 linux kernel: ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Oct 2 18:08:30 linux kernel: ndiswrapper: driver rt2500usb (Linksys,01/07/2005, 2.00.00.0000) loaded
Oct 2 18:08:30 linux kernel: usb 3-5: reset high speed USB device using ehci_hcd and address 2
Oct 2 18:08:31 linux kernel: usb 3-5: reset high speed USB device using ehci_hcd and address 2
Oct 2 18:08:31 linux kernel: usb 3-5: reset high speed USB device using ehci_hcd and address 2
Oct 2 18:08:31 linux kernel: usb 3-5: reset high speed USB device using ehci_hcd and address 2
..
..

It such a shame that device vendors (are you listening cisco/linksys?) do not support their drivers natively on linux, and we have to resort to a quite ingenious re-purposing of existing windows drivers (dnis is very clever, lets face it), but whose configuration is bordering on witchcraft, unfortunately, especially if it doesnt work 'straight away'. I've spent a week trying to get wlan working, ended up upgrading to suse 9.3, then get it *almost* working. About to give up, and run a long cable around the house instead ;-)

Any final ideas please? Thanks.
 
Old 10-02-2005, 07:00 PM   #7
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Oct 2 18:08:31 linux kernel: usb 3-5: reset high speed USB device using ehci_hcd and address 2
OK this might be weird, but it also might work. I did a little googling and stumbled onto this thread where someone was having a similar problem. The interesting bit is this:

Quote:
I think I've found a bit of a pattern, if I go
modprobe -r ehci_hcd
modprobe ndiswrapper
modprobe ehci-hcd
modprobe -r ehci-hcd

The usb port that has my wireless adapter seems to hang around (which it normally will not after ehci is onloaded), even though ehci-hcd is not loaded, and then iwconfig shows my home network just fine. Don't know much more than this, or even why its happening. Just hope it helps get to an end...
But maybe more importantly, this little tidbit is on the ndiswrapper wiki description of the support for your card:

Quote:
oad with modprobe ehci-hcd log2_irq_thresh=4 to avoid "usb X-Y: reset high speed USB device using ehci_hcd and address Z"
I would try booting, unloading the ehci_hcd module, then reloading it with the added flag from the quote and see if that allows the card to work.
 
Old 10-03-2005, 12:43 AM   #8
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Original Poster
Rep: Reputation: 0
Nice one hangdog! It finally works! Many thanks for your time and effort,

For newbies sake (like me), it's nice to have everything in one place. So once I've got it working automatically on bootup, I'll post the download/configuration process for my config, in it's entirety, as a reply to this thread.

Thanks again hangdog. Excellent.
 
Old 10-03-2005, 05:52 AM   #9
flybynight446
LQ Newbie
 
Registered: Oct 2005
Posts: 17

Original Poster
Rep: Reputation: 0
As mentioned above, here are the specifics of the specific config not covered in Linux Questions NDIS Wrapper , which is a good starting point.

>> Obtaining the win xp wireless driver

ndis wiki card list shows my best candidates is:

Quote:
# Card: Linksys #[WUSB54Gv4], 802.11b/g, USB 2.0 -- [link here|List#WUSB54Gv4]
* Driver 2: older Linksys Windows XP driver: ftp://ftp.linksys.com/pub/network/WU...4_20040703.exe Notes: ndiswrapper v1.2-rc1, kernel 2.6.11.7 (also works with grsec2 patch v2.1.5): seems to work, but only 11Mbit/s and without any encryption. no need to unplug the device before removing the ndiswrapper module. works on USB2.0, USB1.1 not tested (yet).
Download it from the above url, unzip using winzip, then grab the 3 relevant files files: WUSB54GV4.cat rt2500usb.inf rt2500usb.sys

Note: v4 of this adapter using a different chipset to v1 and v2. These instructions are for WUSB54Gv4 only! (check your adapter model..)

>> Obtaining the v1.2 ndiswrapper
Download from somewhere and drop in a dir you create eg. /usr/local/src/ndis1_2. ndis wiki page only seems to have newer versions.. which I (and others) have had problems with. So we're going with 1.2, which works in our config. NDISWrapper Installation as per above link.

>> Registering the driver with ndiswrapper
Code:
# ndiswrapper -l
No drivers installed
In the directory containing the rt* files, register the driver with ndis
Code:
# ndiswrapper -i rt2500usb.inf
Installing rt2500usb
Now view the installed driver:
Code:
#ndiswrapper -l
Installed ndis drivers:
rt2500usb       driver present
Plug in the linksys adapter into the usb port, /var/log/messages shows:

Code:
 Oct  3 11:52:17 linux kernel: usb 3-5: new high speed USB device using ehci_hcd and address 3
Note the hardware is now present :
Code:
# ndiswrapper -l
Installed ndis drivers:
rt2500usb       driver present, hardware present
Next do the modprobe stuff (the first two are specific frigs to our xp driver)
Code:
# modprobe -r ehci-hcd
# modprobe ehci-hcd log2_irq_thresh=4
# modprobe ndiswrapper
After the final modprobe above, messages file shows:
Code:
 Oct  3 11:54:05 linux kernel: ndiswrapper: unsupported module, tainting kernel.
Oct  3 11:54:05 linux kernel: ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Oct  3 11:54:05 linux kernel: ndiswrapper: driver rt2500usb (Linksys,04/01/2004, 1.00.00.0000) loaded
Oct  3 11:54:09 linux kernel: wlan0: ndiswrapper ethernet device 00:12:17:5f:66:02 using driver rt2500usb, configuration file 13B1:000D.0.conf
Oct  3 11:54:09 linux kernel: wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
Oct  3 11:54:09 linux kernel: usbcore: registered new driver ndiswrapper
Oct  3 11:54:14 linux ifup: No configuration found for wlan0
Now we should have a wlan0 network setup, but as it says, there's no configuration. Next go into Yast / Network devices / Network and set up appropriate parameters for our device (called wlan-bus-usb) :
  • Device Type : Wireless
    check 'usb' box, and it fills in 'bus-usb' configuration name
    Setup method : Automatic, via DHCP
    Operating Mode : Managed
    Network Name (ESSID) : linksys
    Authentication Mode : Open (our xp driver only works in the clear..), then Finish

The 'Link' light should start blinking now ie. everything should be working. iwconfig will show the newly configured access point now has non-zero mac address, and the ESSID: and Mode: match our config parameters above

Code:
# iwconfig wlan0

Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0     IEEE 802.11g  ESSID:"linksys"  Nickname:"linux"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:13:10:0C:8F:81
          Bit Rate=54 Mb/s   Tx-Power:20 dBm   Sensitivity=-115 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:-37 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:15   Missed beacon:0
First ping the router:
Code:
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=150 time=6.45 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=150 time=1.51 ms
Now try getting the home page of this site:
Code:
# wget linuxquestions.org
--12:03:59--  http://linuxquestions.org/
           => `index.html'
Resolving linuxquestions.org... 64.179.4.149
Connecting to linuxquestions.org|64.179.4.149|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.linuxquestions.org/ [following]
--12:04:00--  http://www.linuxquestions.org/
           => `index.html'
Resolving www.linuxquestions.org... 64.179.4.149
Connecting to www.linuxquestions.org|64.179.4.149|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Finally, we need to get it to start up automatically when we restart. For ndiswrapper, do this once:

Code:
# ndiswrapper -m
Adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper
Given the driver frig above, I dont know the most elegant way (newbie-itus) of getting this to boot up, but one way which definitely works is to take the 3 startup 'modprobe' commands, put them in a file and make it executable. eg. create a file in eg. /root called 'wireless' containing :

Code:
# modprobe -r ehci-hcd
# modprobe ehci-hcd log2_irq_thresh=4
# modprobe ndiswrapper
Then /etc/init.d/boot.local, add in a call to the script above.

Code:
#! /bin/sh
#
# Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany.  All rights reserved.
#
# Author: Werner Fink <werner@suse.de>, 1996
#         Burchard Steinbild, 1996
#
# /etc/init.d/boot.local
#
# script with local commands to be executed from init on system startup
#
# Here you should add things, that should happen directly after booting
# before we're going to the first run level.
#
/root/wireless
This seems to work perfectly. I'm not sure if it's the most elegant implementation, but at least you can run it easily should you plug in the adapter AFTER the machine has started, and need to kick it into life.

After doing the above, reboot, dive into a browser and all should be working straight off without typing any further commands. ie it should just 'work'. Bootup log shows nice startup

Setting up network interfaces:
Code:
    lo        
    lo        IP address: 127.0.0.1/8   
    wlan0     configuration: wlan-bus-usb
    wlan0     warning: using NO encryption
    wlan0     (DHCP) . . <notice>pidofproc: dhcpcd 6570
if anyone has a more elegant way of doing this, please reply with corrections.
 
Old 10-03-2005, 07:07 AM   #10
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
That is one truly excellent how-to. You know you might want to put a summary of this, or a link to this post, in the HCL and/or the ndiswrapper link you gave. A description like this is worth its weight in gold to someone struggling with this wireless rig so making it available in a few places is a good idea.

One minor suggestions is that you may want to investigate how Suse loads modules on system boot. In Slackware there is a start up script that loads them and can be customized. If you could load the usb-hcd module with the proper flags from the get-go it would save you a step in your script. The only reason I suggest that is that some kernels haven't enabled module removal (don't ask me why, but the option is there) in which case your procedure is going to run into trouble. But as I said, it is a very minor suggestion.

Congrats!

<edit>
One more thing, old ndiswrapper versions are available at the ndiswrapper sourceforge site. You just need to click on the "Show all files" link to see it. For reasons that escape me, the ndiswrapper crew insists on hiding the older versions.
</edit>

Last edited by Hangdog42; 10-03-2005 at 07:14 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Linksys WUSB54G Wireless Network Adapter + kubuntu Airjoe Linux - Wireless Networking 1 11-15-2005 09:50 PM
Using an access point as a wirless adapter? xxterrorxx Linux - Wireless Networking 1 10-07-2005 07:15 AM
How to identify v4 of Linksys wusb54g adapter? zenith1 Linux - Wireless Networking 2 09-08-2005 03:13 PM
Linksys WUSB11 v2.6 - Able to ping Access point but nothing beyond shepper Slackware 8 03-25-2005 02:25 AM
Linux Access Point using Prism based adapter violetb Linux - Wireless Networking 3 11-24-2004 11:00 AM


All times are GMT -5. The time now is 07:44 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration