I am attempting to get waproamd to work. After playing around a few hours I can now get waproamd to fire off a script when it associates with an access point. It pulls the correct information from files and sets wlan0 accordingly. Here is the odd thing when waproamd fires up on boot it associates and uses dhcp to get an ip. It gets an IP just fine via using dhclient. But when I try to access the network I get problems with the host being unreachable.

The commands the script runs are the following

ifconfig wlan0 down
iwconfig wlan0 key open ##########
iwconfig wlan0 essid $$$$$$$
iwconfig wlan0 ap any
ifconfig wlan0 up
dhclient -q wlan0

I have also tried

dhclient -r
iwconfig wlan0 key open ##########
iwconfig wlan0 essid $$$$$$$
iwconfig wlan0 ap any
ifconfig wlan0 up
dhclient -q wlan0

If I run these scripts after I login or I restart waproamd it works fine. But on boot it fails to work.

is dhclient -r the best way to release an IP so I get a new one?

I just tried out linux while at a different wirless network and it came up just fine. So i'm thinking I need to add a flag to the dhclient but i'm unsure. At home i'm on a lynksys accesspoint.

Anyone have any suggestions on why I am gettings host is unreachable until I rerun the script?

More information:

the error message I actually get is no route to host

when I type the command route it hangs on the last entry for about a a minute then resolves correctly.

if I do a route del default followed by a route add default gw IPADDY it still hangs

Even more info:

I tried to make the script run 2 minutes after the system booted up. It ran just fine but still I got no route to host errors.

So next I tried to make the script execute as a shell login script. I touched a file and deleted it on shutdown so that only the first login would cause the script to run.

Still I had the same problems.

So it seems like there is some sort of problem with automated scripts. Is there some varaible set when a script is executed by hand versus by an login or startup script?