RFC: Current state of using nl80211 control port for rx path (pre-auth issues)

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

 



Hi,

while trying to get rx over nl80211 control port to work, I noticed the
following issue when using pre-auth.

The current kernel behavior is: after enabling control port, ETH_P_PAE
frames and ETH_P_PREAUTH frames
get forwarded to user user space. These frames only have one MAC address
attached from the kernel
API. In the scenario STA s -> AP a1 -> AP a2, where s sends a pre-auth
frame to a2, a1 gets this frame over the
nl80211 control port and only knows its source address (s' address). In
order to forward it to a2 (re-inject it on
a l2_packet interface), knowing the destination mac would be necessary.

I'm currently working on kernel patches, which can use src and dst mac
for forwarding control port frames with
nl80211.

Next steps/possible direction:
As these patches may don't get into mainline or take some time, I will
enable rx over control port only for
wpa_supplicant and disable it for hostapd. I already include code for
hostapd, which deals with src/dst
addresses for forwarding.

Advantages:
Using nl80211 control port made wpa_supplicant connections really fast
in my use cases.



_______________________________________________
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