Hello,

im using two OpenWrt Kamikaze router, based on WRT54GL hardware.
One router is configured as access point and one as client.

Everything is working fine, if I'm starting first the access point and then the client.
If I reverse the order or if I restart the client, it doesn't associate to the AP anymore.

When it is not working iwconfig writes the following:
wl0       IEEE 802.11-DS  ESSID:""
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated
          Bit Rate:54 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:5  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If I do:
iwconfig wl0 essid "XXX_XXX"

It is working again, like I would have started AP and client in the right order:

wl0       IEEE 802.11-DS  ESSID:"XXX_XXX"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:18:F8:XX:XX:XX
          Bit Rate=54 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=4/5  Signal level=-64 dBm  Noise level=-91 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

However I think that the the AP is setup correctly:

config 'wifi-device' 'wl0'
        option 'type' 'broadcom'
        option 'channel' '6'
        option 'disabled' '0'

config 'wifi-iface'
        option 'device' 'wl0'
        option 'network' 'wifi'
        option 'mode' 'sta'
        option 'ssid' 'XXX_XXX'
        option 'encryption' 'wep'
        option 'hidden' '0'
        option 'isolate' '0'
        option 'bgscan' '0'
        option 'wds' '0'
        option 'key' '1'
        option 'key1' 'xxxxxxxxxxxxxxxxxxxxx'
        option 'macpolicy' 'none'

To me it seems that, if the client can't find the AP on the first try, it stops trying to associate to the AP.
Is there some way to change this behavior?

With best regards
            Markus

Hello,

today I detected,  that beside the error explained above I have another problem.
Sometimes the client associates to the AP, but it is still impossible to ping the AP.

After this (client side)

iwconfig wl0 essid "XXX_XXX"

everything worked again.

Has someone a idea what might cause this behaviour?

With best regards
             Markus

I have the same problems!!

After boot, if I do "wifi<enter>" all works well.

the wifi command without paramters is the same as "wifi boot", and it config and puts up the wifi iface.

regards

Hello all ,
I have Installed kamikaze_7.09 on a WRT54GS here and have similar Problems , wifi does not work on startup , yes i have commented out the line
option disabled '1'
in /etc/config/wireless  , if i do "wifi" i get the following message :
wl0(broadcom)  Interface type not supported

damn , everyone know how that can happen ?
have flashed the router back to whiterussian 0.9 and all works well

Problem solved : forgotten to install wlc ...argghhhhhh .....