Operstate management
From: Cedric Debarge <hidden>
Date: 2015-03-16 17:49:26
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