Client mode didn't reconect

[pipos]

HI

i had one strange problem,
my Access point goes down sometimes for cca 5-10min due power loss.

but when it comes back UP, my ASUS wl500g fw 1.9.2.7-4 (client mode, ethernet bridge)doesn't reconect automaticali.....
when i logged in and type wl status...it seems everithing is OK, wl bssid returns me MAC of AP.....but i can't ping AP....
i tried wl disassoc; wl assoc....but no change
after reboot of asus everything is OK.

is it possible to solve this?
where i can find the boot connect script?
what exactly do nvram variables wl_join, wl_auth....?

Update:

i use WEP 128
when AP comes back up after power loss
in shared only mode.......i cannto see MAC of my asus client
in open system mode.......i see MAC of my asus, but i can't ping it

after reboot my asus client....everythink is OK in shared mode, or open system.....
with WPA it's the same thing

Could somebody help me?
thanks

[petgun]

..but when it comes back UP, my ASUS wl500g fw 1.9.2.7-4 (client mode, ethernet bridge)doesn't reconect automaticali.....
...after reboot of asus everything is OK.

same to me

[pipos]

Hi

i add this script to /usr/local/sbin
assoc.sh:

#!/bin/sh
ping -c 1 172.16.1.253 >> /dev/null
assoc=`wl bssid|sed 's/bssid is//'`
if [ ${assoc} = "00:00:00:00:00:00" ]
then reboot
elif [ ! $(wl status|grep BSSID)]
then reboot
fi

and to post-boot i add

(while sleep 20s; do /usr/local/sbin/assoc; done)&

this makes a router reboot when it's not associated


Oleg, could you take a look at this problem?
I think, that problem is caused by wrong, or no WEP keys which device used in reconect script.
Were in sources i could find client mode connect scripts? How s client connection do in this firmwares (1.9.2.7-3)
please help