Dirk Nehring <[EMAIL PROTECTED]> wrote:
> In my test setup I haven't got WPA2 working in client mode. I need a
> volunteer to support this. In my opinion nas needed to be started as
> followed:
>
> nas -P /tmp/nas.lan.pid -H 34954 -i eth1 -S -m YYY -k xxxxxx -s xxxxx -w YYY
> -g 3600
>
> Then check "wl sta_info". Please try it with psk2 and aes.
Sorry, my hostapd ist configured to support WPA2 and CCMP only. [1]
Anyway, I get the following:
[EMAIL PROTECTED]:~# nas -P /tmp/nas.lan.pid -H 34954 -i eth1 -S -m 64 -k
<pre-shared-key> -s <my-essid> -w AES -g 3600
eth1: ignore i/f due to error(s)
Different values for -m switch did not change the errormessage.
[EMAIL PROTECTED]:/# wl sta_info 00:0E:2E:74:3C:3A
STA 00:0E:2E:74:3C:3A:
rateset [ 1 2 5.5 11 18 24 36 48 54 ]
idle 288 seconds
in network 0 seconds
state :
flags 0x0
With 00:0E:2E:74:3C:3A beeing the IP-adress of the machine running
hostap.
eth1 is not part of a bridge at the moment.
Sven
[1] hostapd.conf for madwifi can be provided on request
--
"Software is like sex; it's better when it's free"
(Linus Torvalds)
/me is [EMAIL PROTECTED], http://sven.gegg.us/ on the Web
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
