Joined: Sep. 2005
||Posted: Jan. 10 2008,15:38
1. Since my post in Feb 2007, dsl v4+ has been released, which uses the 2.4.31 kernel. So you don't have to use dsl2.1b anymore if you don't want to in order to use the ipw2200 extension, you can update to dsl4+ and get the benefit of drag and drop and many other improvements that Robert has implemented.
2. Extension installs don't normally persist between boots when running from livecd. You need to load the extension again everytime you boot, and configure your wireless again. If manually loading extensions every boot is tedious for you, you can put your favourite extensions on a vfat or linux partition (say hda2), and use the mydsl=hda2 boot option - those extensions will get loaded automatically during boot. [EDIT: Try reading the "Getting Started" page when dsl first boots!]
I run a little script as root to make starting my ipw2200 easy, which is basically a tidied-up combination of the 2 scripts referred to in the ipw2200 extension info file. It looks like this:
|Code Sample |
if [ -L /lib/modules/2.4.31/modules.dep ]; then
rm -rf /lib/modules/2.4.31/modules.*
cp /KNOPPIX/lib/modules/2.4.31/modules.* /lib/modules/2.4.31
echo "Configuring Wireless LAN Card for $YOUR_ESSID"
iwconfig eth1 essid $YOUR_ESSID key $YOUR_KEY
# dynamic dns
pump -i eth1
## or for static IP
## modify /etc/resolv.conf to include your nameservers
# Set default gateway (not always needed)
route add default gw 192.168.xx.x eth1 # or whatever your router's IP is
I guess you've worked out that the key for the above needs to be in hex.
If entering an ascii key, try putting s: before the key string.
If that doesn't work, you can convert an ascii key to hex using on e of the overabundance ;=) of conversion scripts I posted here: