On 06.01.2014 15:28, Alexandr wrote:
I simply changed key in this listing to secret. Yes, I tried a very
simple configuration, no luck:
network={
ssid=door
psk=secret
}
Try using wpa_passphrase:
man wpa_passphrase.
It should create correct psk.
06.01.2014 16:24, Adrian Chadd пишет:
The
Yup! 11n normally involves going from a non-11n channel (11bg, 11a) to
upgrade to an 11n channel. So yeah, it'll look like 11g, except
it'll also use 11n rates.
-a
On 7 January 2014 12:32, pbtraveller pbtravel...@googlemail.com wrote:
Hi Adrian,
thanks a lot for the quick response and
hi,
please retry with the only network block entries being:
ssid=
psk=
.. and let wpa_supplicant figure it out.
-a
On 7 January 2014 13:07, Peter Ankerstål pe...@pean.org wrote:
Hi!
Im trying to connect from a Lenovo X220 to my FreeBSD router running hostapd.
The router is supporting
Ooops. Missed the important part of client messages. Also I have tried with
different pre-shared keys but it still don’t work.
wlan0: State: ASSOCIATING - ASSOCIATED
wlan0: Associated to a new BSS: BSSID=04:f0:21:01:3d:87
wlan0: No keys have been configured - skip key clearing
wlan0: Associated
Hm, sounds to me like something I fixed in -HEAD. Try -HEAD.
The TL;DR - the EAPOL frames are going out at a much higher transmit
rate than the initial association attempts, which means it associates
fine but it can't authenticate successfully.
Try running -HEAD. I bet it'll work.
-a
On 7
