Re: Building from source: authentication error + DS Params mismatch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Jouni
I realized than when it is working (same hostapd.conf, difference is running hostapd from compiled from source or from package manager)

from package manager :
pnic_wlan: Event EAPOL_TX_STATUS (38) received
IEEE 802.1X: e8:50:8b:03:f4:bf TX status - version=2 type=3 length=95 - ack=1
WPA: EAPOL-Key TX status for STA e8:50:8b:03:f4:bf ack=1
WPA: Increase initial EAPOL-Key 1/4 timeout by 1000 ms because of acknowledged frame
pnic_wlan: Event EAPOL_RX (24) received
IEEE 802.1X: 121 bytes from e8:50:8b:03:f4:bf
   IEEE 802.1X: version=1 type=3 length=117
WPA: Received EAPOL-Key from e8:50:8b:03:f4:bf key_info=0x10a type=2 key_data_length=22


from source :
pnic_wlan: Event EAPOL_TX_STATUS (38) received
IEEE 802.1X: e8:50:8b:03:f4:bf TX status - version=2 type=3 length=95 - ack=1
WPA: EAPOL-Key TX status for STA e8:50:8b:03:f4:bf ack=1
WPA: Increase initial EAPOL-Key 1/4 timeout by 1000 ms because of acknowledged frame
pnic_wlan: STA e8:50:8b:03:f4:bf WPA: EAPOL-Key timeout
WPA: e8:50:8b:03:f4:bf WPA_PTK entering state PTKSTART
pnic_wlan: STA e8:50:8b:03:f4:bf WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=1 kde_len=0 keyidx=0 encr=0)
WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02
WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 2)
pnic_wlan: Event EAPOL_TX_STATUS (38) received
...

I realise now that I don't have the
pnic_wlan: Event EAPOL_RX (24) received

So the station tries until reaching timeout..
Is there anything I should activate on my .config which is not activated by default on the source to make the authentication through EAPOL ?

many thanks


On 02/19/2016 02:21 PM, Jouni Malinen wrote:
On Fri, Feb 19, 2016 at 12:39:39PM +0100, Benoit wrote:
When I start hostapd in debuging mode I keep receiving this message
(and I am not able to connect to AP from my stations)

Ignore Probe Request due to DS Params mismatch: chan=1 != ds.chan=2
Ignore Probe Request due to DS Params mismatch: chan=1 != ds.chan=3
That message is correct and expected behavior.

EAP authentication never success...

Any idea from where I can start troubleshoot this?
Look at the other messages than that note about ignoring Probe Request
frames on foreign channels.




_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux