Hi Johannes,
On 12/07/2016 12:48 AM, Johannes Berg wrote:
On Wed, 2016-12-07 at 00:40 -0600, Denis Kenzior wrote:
No, this is the part you didn't understand. Simply authenticating
doesn't actually create anything like a "link" to the AP. The only
Okay, but it is then a bit misleading that iw link reports us being
'connected' during this time for example.
It doesn't!
# iw wlan0 auth <ssid> <bssid> open 2462
-> iw event reporting
wlan0 (phy #0): auth <localMAC> -> <bssid> status: 0: Successful
# iw wlan0 link
Not connected.
Yes, you're right. It is iw info that shows us 'connected'
< Request: Get Interface (0x05) len 8 [ack] 35235.316448
Interface Index: 3 (0x00000003)
> Result: New Interface (0x07) len 108 35235.316455
Interface Index: 3 (0x00000003)
Interface Name: wlp2s0
Wiphy: 0 (0x00000000)
Interface Type: 2 (0x00000002)
Wireless Device: 1 (0x0000000000000001)
Generation: 5 (0x00000005)
Wiphy Frequency: 2417 (0x00000971)
Wiphy Channel Type: 1 (0x00000001)
Channel Width: 1 (0x00000001)
Center Frequency 1: 2417 (0x00000971)
Wiphy TX Power Level: 2200 (0x00000898)
> Response: Get Interface (0x05) len 4 35235.316457
Status: Success (0)
Fair enough. I think we can live with that since we're not using
CMD_AUTHENTICATE unless we need to roam using FT.
That seems like a very strange decision, but it's obviously up to you
:)
Care to elaborate ?
Regards,
-Denis
