Networking :: Setting with a routeur

Quote (williahow @ Oct. 21 2004,15:37)

docdtv - try using

modprobe prism2_usb prism2_doreset=1

before the wlanctl-ng/pump commands described elswhere in the forum

This works for me using a D-LinK DWL-122 Ver A1 with D-Link DL-614+ Revision A (2 antenna) combination

Thanks for the tip, williahow!

Again, I am trying to make a D-Link 614+ WAP/router work with a D-Link DWL-122 (hardware version A1) as client (USB) card. [But the router is NOT Revision A (2 antenna) combination, as is the one williahow uses.]

For the benefit of newbies and people with imperfect recall,
http://www.faqs.org/docs/linux_scratch/appendixa/modutils.html has a nice summary of the "modutils" package, which helps one manage kernel modules like "prism2_usb".

After booting DSL 0.8.2, (based on Linux kernel 2.4.26) I do
"lsmod | grep pr" and read:
prism2_usb 61468 0
p80211 22412 0 [prism2_usb]
usbcore 57824 1 [hid prism2_usb usb-uhc1]
so that one sees that prism2 is loaded AUTOMATICALLY.

Issuing "modinfo prism2_usb" shows that this module supports
3 commands, including the one williahow kindly suggested I use, viz. modprobe prism2_usb prism2_doreset=1

Unfortunately, it does not seem to help me get DHCP working.
"pump -i wlan0" still reports "Operation failed." It seems similar utilities like "dhcpd" and "dhclient" do not come with DSL to try out.

"modinfo p80211" shows some more commands, but none
seem germane to solving my problem.

After a boot, the DWL-122 power lamp is on and the networking lamp blinks. A necessary and sufficient condition to make the latter light steadily is to use the "prism2" (GUI-based) applet and issue the correct (E)SSID - the proper channel does not seem to matter.

FYI, the details reported by iwconfig track the parameters given via the prism2 applet (i.e. the SSID and channel->frequency).

I looked again at: ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README
"wlanctl-ng" comes with DSL 0.8.2 and I tried issuing various of its commands to get dhcp to work out, but to no avail either.

"wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable"
reports back "...returncode=success"

"wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem"
reports back "...returncode=success"

I grow pessimistic that I will get my client card to work, even though I know that it works just fine under Windows 98SE. But I will watch the discussion here if someone has a suggestion in the future.

williahow, you have been kind and meticulous. But can you offer me yet more details? Like the DSL version, ALL the commands you issue to get connected, etc? Thanks.

docdtv,

My setup is DSL version 0.8.2, these are commands which work for me on a basic (dsl toram) boot

modprobe prism2_usb prism2_doreset=1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
#Sometimes from power up this has to be done twice for a success
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid= authtype=opensystem
ifconfig wlan0 up
pump -i wlan0

The issue could be that I don't currently have WEP turned on in the D-Link Router (living dangerously..). When I turned WEP on, I also get connection failure.

Quote (williahow @ Oct. 25 2004,19:04)

Thanks so very much again, williahow! These commands work perfectly, pretty much(+) *AS IS*, booting with the USB card PC-attached!

It turns out I had actually tried the "ifconfig wlan0 up" command per the suggestions of the Web page at:
http://m4i.homeip.net/m4i/pub/wlan-ng12_usb_readme.txt
- as well as the various other commands in your script, as discussed previously. But obviously I had never used all of them in the particular order, *especially* not the double-repeated command!!!

Thanks again!

(+) Of course I follow "ssid=" with my particular (E)SSID.

original here.