Search Linux Wireless

Reassociation is broken via CMD_CONNECT

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

 



Hi,

Based on the documentation for PREV_BSSID:

"previous BSSID, to be used in ASSOCIATE and CONNECT commands to
specify a request to reassociate within an ESS, i.e., to use
Reassociate Request frame"

But this actually isn't true when using CMD_CONNECT. The kernel does a
full re-connect if PREV_BSSID is provided (easily verified by kernel
logs which show an Authenticate frame being sent).

This is due to, in part, cfg80211_sme_connect() calling
cfg80211_get_conn_bss() which sets the connection state to
CFG80211_CONN_AUTHENTICATE_NEXT.

I tried hacking this to set it to CFG80211_CONN_ASSOCIATE_NEXT if
prev_bssid was set, but was unable to reassociate. I think the
CMD_CONNECT path just needs to call rdev_assoc directly if PREV_BSSID
is included? or some other modifications to cfg80211_sme_connect()?

Thanks,
James





[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux