DWL 122 Help


Forum: Networking
Topic: DWL 122 Help
started by: cjnodell

Posted by cjnodell on Aug. 02 2005,11:53
I have a d-link DWL-122 USB wireless networking adapter. It has a prism 2 chipset and the company recommends using linux-wlan-ng drivers with linux. I will be using DSL 1.4

I have read that DSL comes with these drivers. How can i get the adapter to work?

What commands to i need to type, or what tools do i need to use?

I am new to linux, so a step-by-step guide would be nice.

Thanks!

Posted by tempestuous on Aug. 03 2005,02:01
Firstly, thanks for doing your research about chipset and driver before posting a question.
It would sure be helpful if everyone did this.

Plug your USB adaptor in.  Wait a few seconds for hotplug to autodetect it ... you can check "lsmod" if you like - "prism2_usb" should now be listed.
Now launch DSLpanel from its desktop icon, then Prism2.  Enter your wireless network's SSID and WEP key, then press OK.  With the WEP key, you must place a colon between every two characters.  Run ifconfig and ping your router to check that all is well.

If you want to see what magic is going on behind the gui, have a look at /usr/local/bin/prism2.sh in a text editor.  You can modify this script if, for example, you prefer to use a static IP address.

Posted by cjnodell on Aug. 03 2005,09:05
Thanks, everzthing works great. I took a look at the prism2.sh, but was not able to extract what commands where used to get my wireless up and running. Here is the script>

#!/bin/sh
#
# Wireless Card config for prism2 chipset for DSL 0.8.x
# Pasted together from various googled sources and forums
# Reworked for Damn Small Linux

if [ -z "$(lsmod | grep prism)" ] ; then
  modprobe prism2_cs
fi

wlanctl-ng "$1" lnxreq_ifstate ifstate=enable
if [ -n $2 ]; then
  wlanctl-ng "$1" lnxreq_wlansniff enable=false channel "$2"
  wlanctl-ng "$1" p2req_channel_info_results channel "$2"
fi
if [ -n "$4" ]; then
  wlanctl-ng "$1" lnxreq_hostwep decrypt=true encrypt=true
  wlanctl-ng "$1" dot11req_mibset mibattribute=dot11WEPDefaultKeyID=0
  wlanctl-ng "$1" dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true
  wlanctl-ng "$1" dot11req_mibset mibattribute=dot11PrivacyInvoked=true
  wlanctl-ng "$1" dot11req_mibset mibattribute=dot11WEPDefaultKey0="$4"
fi
wlanctl-ng "$1" lnxreq_autojoin ssid="$3" authtype=opensystem
pump -i "$1"
kill `pidof wmnet`
wmnet -w -W "$1" &

There are a lot of if/than statements, so how would i know exactly what commands the script choose to run? In addition, there where a lot of variables. Some of them i can figure out.  $1 is probablz wlan0, $3 is my ssid but thats all i can figure out. I wouldlike to have a list of commands i can tzpe in to make the wirelss adapter wour, without using the graphical tool that comes with DSL

Posted by tempestuous on Aug. 03 2005,10:18
prism2.sh gets its input values from the flua script /usr/local/bin/prism2_setup -
$1 device (default wlan0)
$2 channel (default 11)
$3 SSID
$4 WEP

To run a similar script without the flua interface, just delete all the "if" and "fi" lines.  And obviously "modprobe prism2_cs" must be changed to "modprobe prism2_usb" for your adaptor, or even delete it if your system automatically loads this module.

Posted by ke4nt1 on Aug. 03 2005,12:01
Once you have setup the device thru the prism2 gui in DSLPanel,
a file called myprism2.sh is created. It is found in /opt ..

Adding the line opt/myprism2.sh to your /home/dsl/.filetool.lst file
will ensure the file is added to your backup, and available every reboot.

Adding the line /opt/myprism2.sh to your /opt/bootlocal.sh file
will run your prism2 config automatically, every reboot.

/opt/bootlocal.sh should already be a part of your .filetool.lst file,
and included in your backup.

As long as the device is plugged in at boottime, you should have
inet access as soon as your backup is restored, right before
you hit the desktop.

73
ke4nt

Posted by cjnodell on Aug. 03 2005,16:04
Awsome. Thanks for all the info. As i understand it, the bootlocal.sh file is the debian equilivant of rc.local? I am asking so many questions for two reasons, one I want to learn, and two, while i love haveing DSL, i still want to try out Debian Sarge, and i figure that after linux-wlan-ng is installed, i will need the same commands to get my adapter up and running. Thanks for all the help. this has been the most helpfull forum i have visited yet!
Posted by cjnodell on Aug. 03 2005,17:47
So, based what you guys have told me, these are the commands i would need when the device is wlan0, channel is 6 and no wep. This all applies to the linux-wlan-ng driver right? I have heard that the kernel has built in support for the prism chipset, is that true? Thanks again for all the help.

modprobe prism2_usb
wlanctl-ng "wlan0" lnxreq_ifstate ifstate=enable
wlanctl-ng "wlan0" lnxreq_wlansniff enable=false channel "6"
wlanctl-ng "wlan0" p2req_channel_info_results channel "6"
wlanctl-ng "wlan0" lnxreq_autojoin ssid="SPEEDY" authtype=opensystem
pump -i "wlan0"
kill `pidof wmnet`
wmnet -w -W "wlan0" &

Posted by tempestuous on Aug. 04 2005,08:47
Your script is almost correct, just delete all the quotation marks.  And wmnet is, of course, optional.  It's a dockapp.  I'm not sure if it displays traffic or signal strength.

wlanctl-ng is the configuration utility of the linux-wlan-ng driver package, so yes, these commands are unique to linux-wlan-ng.

The linux kernel MIGHT have inbuilt support for the prism chipset (possibly older prism chipsets, I think I've seen reference to it in a kernel recompile) but certainly not in the form of linux-wlan-ng drivers.  This driver package is quite separate.

I think bootlocal.sh is a DSL innovation, rather than Debian.

Posted by odbod on Mar. 24 2006,00:23
wait wait wait.. I don't understand.. Can you list step by step waht to do to? I guess the process would be same with a DWL-g120 rev b.
Posted by baeder on Dec. 18 2006,20:25
Just to add here for others...

Yes, using the prisim2 config on the control panel works after you plug in the adapter, but (at least for me) on the reboot, it thought it was an ndiswrapper thing.

So, in addition to the above hints - i.e. use the ":" separator, I just copied the prisim2.sh to the /opt area, added the modprobe for the usb, and pointed the myprisim.sh to the /opt copy.

Thanks again for the tips here!  Now it's on the net!

Scott

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.