lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 16 Mar 2015 18:07:01 +0100
From:	"Cedric Debarge" <cedric.debarge@...sys.fr>
To:	<netdev@...r.kernel.org>
Subject: Operstate management

Hi all,

I have a problem with the Mac80211 driver and Wpa_supplicant in
operstate management.

My sta is connected to AP1 and I launch iperf from the sta to a computer
(behind the AP).
I force a handover from AP1 to AP2 and the sta sends an arp packed
during the WPA Handshake.

The tcpdump capture is given below:
17:43:12.964096 EAPOL key (3) v2, len 95
17:43:12.998439 EAPOL key (3) v1, len 117
17:43:13.062409 ARP, Request who-has 10.32.61.100 tell 10.32.0.1, length
28
17:43:13.079989 EAPOL key (3) v2, len 151
17:43:13.082764 EAPOL key (3) v1, len 95
17:43:14.062381 ARP, Request who-has 10.32.61.100 tell 10.32.0.1, length
28
17:43:14.127101 ARP, Reply 10.32.61.100 is-at b8:88:e3:45:1d:c6 (oui
Unknown), length 46
17:43:14.127123 IP 10.69.1.201.41690 > 10.32.61.100.5001: UDP, length
1470
17:43:14.127136 IP 10.69.1.201.41690 > 10.32.61.100.5001: UDP, length
1470

I checked the wireless interface state during WPA Handshake, the
Operstate during WPA Handshake is set to IF_OPER_DORMANT.

Is it normal that the local IP stack sends a frame with this operstate ?
If I've correctly understood this state, the Local IP stack should wait
the IF_OPER_UP to transfert data. Is it right?

What is the link between the operstate and link_mode?

Any help will be appreciatted.

Cedric Voncken

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ