OpenWrt Forum Archive

Topic: No WPA in WET mode?

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

Hardware: 2x Linksys WRT54G Vers 2.2
Software: White Russian RC5
Encryption: WPA

Hi I have 2 WRT54G one is in AP  mode and the other is in wet mode.
If i turn WPA on my client  WRT54G can't connect to the AP.
Other Hardware (PDA, Laptop etc..) work perfekt.
It also works if i use WEP.

My Settings:

AP:
mtd -r erase nvram

nvram set wan_hostname="master"
nvram set lan_ipaddr=192.168.1.2
nvram set lan_dns="192.168.1.1"
nvram set lan_gateway="192.168.1.1"
nvram set wl0_mode=ap
nvram set wl0_ssid=OpenWrt
nvram set wl0_channel=4
ipkg update
ipkg install nas
ipkg remove dnsmasq
nvram unset wl0_crypto
nvram set wl0_wpa_psk="63chars"
nvram set wl0_closed="0"
nvram set wl0_crypto="tkip+aes"
nvram set wl0_akm="psk"
nvram set wl0_wep="disabled"
nvram commit
reboot

Client:
mtd -r erase nvram

nvram set wan_hostname="slave"
nvram set lan_ipaddr=192.168.1.3
nvram set lan_dns="192.168.1.1"
nvram set lan_gateway="192.168.1.1"
nvram set wl0_mode=wet
nvram set wl0_ssid=OpenWrt
nvram set wl0_channel=4
ipkg update
ipkg install nas
ipkg remove dnsmasq
nvram unset wl0_crypto
nvram set wl0_wpa_psk="63chars"
nvram set wl0_closed="0"
nvram set wl0_crypto="tkip"
nvram set wl0_akm="psk"
nvram set wl0_wep="disabled"
nvram commit
reboot

In wet mode the 'wifi' routine will enable the wpa supplicant that is built-in the broadcom driver wl.o.
So no need to load and run nas on the client in wireless extender mode (it is needed on the ap to authenticate wpa).
Make sure wl0_auth=0 as it may have become set through the WEP experiments.

ok.
i remove nas
and set wl0_auth=0
still same problem hmm

eth1      IEEE 802.11-DS  ESSID:""
          Mode:Repeater  Frequency:2.427 GHz  Tx-Power:19 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off

some more things to try:
1) using identical wl0_crypto settings on ap and wet unit (just for elimination of causes; i agree that it should work with the ap allowing both tkip and aes).
2) check setting of wl0_infra to be enabled on both

After making changes, just give 'wifi' command to get the changed parameters to the radio and ping to see whether you get through.
When debugging i use the wl package. 'wl dump' will give you much info.

(Last edited by doddel on 7 Apr 2006, 17:27)

wl0_crypto is set to tkip on both devices
wl0_infra is 1 on both devices

did a little test with two spare v3.1 wrt54g boxes and rc5, one access point and one repeater, and it worked first time in wpa-psk with tkip crypto.
To help your debugging below is what various commands show on my boxes. I had to issue 'wifi' on the client to get it to associate after the ap had been rebooted.
--------------------------------------------------------------
AP (running nas)
"iwconfig eth1" output:
eth1      IEEE 802.11-DS  ESSID:"myessid"
          Mode:Master  Frequency:2.427 GHz  Access Point: 00:14:BF:C4:DF:0A
          Tx-Power:19 dBm
          RTS thr=2346 B   Fragment thr=2346 B
          Encryption key:9E31-947D-none-ofof-your-busi-ness-F4EA-AC5D-2E73-6F00-6967-0000-002E-736F-0000-0000 [2]

'wl dump' output:
resets 5
perm_etheraddr 00:14:bf:c4:df:0a cur_etheraddr 00:14:bf:c4:df:0a
board 0x708, board rev 1.0
wsec 2 auth 0 wsec_index 1 wep_algo 2
rate_override: A 0, B 0
antdiv_override 1 txant 1
current_bss.BSSID 00:14:bf:c4:df:0a
current_bss.SSID "myessid"
associated 1
--------------------------------------------------------------
CLIENT (in wet mode, using built-in broadcom supplicant):
"iwconfig eth1" output:

eth1      IEEE 802.11-DS  ESSID:"myessid"
          Mode:Repeater  Frequency:2.427 GHz  Access Point: 00:14:BF:C4:DF:0A
          Tx-Power:19 dBm
          RTS thr=2346 B   Fragment thr=2346 B
          Encryption key:off
          Link Signal level:-62 dBm  Noise level:-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:9  Invalid misc:0   Missed beacon:0

'wl dump' output:
resets 7
perm_etheraddr 00:14:bf:c4:df:07 cur_etheraddr 00:14:bf:c4:df:07
board 0x708, board rev 1.0
wsec 2 auth 0 wsec_index -1 wep_algo 0
rate_override: A 0, B 0
antdiv_override 1 txant 1
current_bss.BSSID 00:14:bf:c4:df:0a
current_bss.SSID "myessid"
assoc_state 0 associated 1

'wl scan ; sleep 1 ; wl scanresults' output:
SSID: "myessid"
Mode: Managed   RSSI: -64 dBm   noise: -95 dBm  Channel: 4
BSSID: 00:14:BF:C4:DF:0A        Capability: ESS WEP ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 11(b) 18 24(b) 36 54 6(b) 9 12(b) 48 ]
WPA:
        multicast cipher: TKIP
        unicast ciphers(1): TKIP
        AKM Suites(1): WPA-PSK
        WPA Capabilities(0x0): Pairwise, 1 PTK Replay Ctr(s)

(Last edited by doddel on 8 Apr 2006, 15:09)

The discussion might have continued from here.