OpenWrt Forum Archive

Topic: Asus 500gp - Atheros wifi went crazy ??

The content of this topic has been archived on 25 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,
I've just updated my 500gp with the 11462 revision of trunk but I have very unstable wifi. It is configured to wpa but it actually uses WEP, sometimes switches to WPA but the connection is very poor. Before I had v10911 and it was working fine.

root@ap:~# cat /etc/config/wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'channel' '4'
        option 'disabled' '0'
        option 'agmode' '11bg'
        option 'diversity' '0'
        option 'txantenna' '1'
        option 'rxantenna' '1'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'ssid' 'WiFi'
        option 'encryption' 'psk'
        option 'hidden' '0'
        option 'isolate' '0'
        option 'txpower' '15'
        option 'bgscan' '0'
        option 'wds' '0'
        option 'key' 'password'
        option 'macpolicy' 'none'
        option 'bursting' '0'
        option '80211h' '0'
        option 'wmm' '0'
        option 'xr' '0'
        option 'ar' '0'
        option 'turbo' '0'

thanks for your help.

T.

well I tried to set it to wpa2 and set the option "distance" to "2" and now it seems to work better.

Is the distance parameter so important ?

Tex

hmmm it is back again: after a reboot, my network is WEP even if the config says wpa.

airodump shows:

BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB  ENC  CIPHER AUTH ESSID
00:0B:6B:83:xx:xx   60  0        0       77    0   9  54. WPA  WEP    OPN  WiFi

when I reload the config via  /etc/init.d/network reload then it works fine again :

 BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB  ENC  CIPHER AUTH ESSID

 00:0B:6B:83:xx:xx   55 100      289      170    2   9  54. WPA2 CCMP   PSK  WiFi

Do you have an idea where does this come from ??

Thanks,
Tex

(Last edited by Tex-Twil on 15 Jun 2008, 13:08)

So I switched back to v10911 but the problem is still the same :s

As  quick hack, I added a init script which reload the network after the boot but this is just a temporarily solution.

Tex

The discussion might have continued from here.