In comp.os.linux.networking can2002 <can2002@nospammaildotnet>:
> Hi,
> I've got my ipw2100 wireless card working on my Tosh laptop and if I
> manually type out a series of iwconfig commands I get it to connect to
> my Access Point, as shown below:
[..]
> #!/bin/bash
> sudo iwconfig eth1 essid wireless
> sudo iwconfig eth1 key [3] s:1234567890123
> sudo iwconfig eth1 key [3] restricted
> sudo iwconfig eth1 key [3]
> sudo dhclient eth1
> The above script will not work - I don't get an IP address and if I run
> 'iwconfig eth1' it indicates encryption is not enabled. If I then try
> running the iwconfig commands again manually it's fine.
I'd put all commands without sudo in a script and call this via
sudo, just make sure your user has no write permissions to the
dir you put it in.
#!/bin/bash
# Bring up wireless interface
ifcf="/sbin/ifconfig"
iwdev="ra0"
iwcf="/usr/local/sbin/iwconfig"
/sbin/modprobe rt2500
$ifcf $iwdev inet 192.168.3.22 up
$iwcf $iwdev mode Ad-Hoc
$iwcf $iwdev enc restricted
$iwcf $iwdev key xxxxxxxxxxxxx
$iwcf $iwdev ap 00:00:22:22:22:22
$iwcf $iwdev essid "blah"
$iwcf $iwdev rate 54M
# Turn on wireless operation
$iwcf $iwdev mode 1
###
Just a quick hack, put together in a few minutes, I'm not using
wlan serious, just played around with it. The above works just
fine for my purposes. There's an ipw2200 card in a laptop, found
the wireless device among the most unstable/crappy devices ever
used. Probably because of the proprietary firmware, dmesg says
frequently "ipw2200: Firmware error detected. Restarting." This
is the moment wireless operation start to suck. Hope your card
works more reliable?
Good luck
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo
(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 203: Write-only-memory subsystem too slow for
this machine. Contact your local dealer.