Search Linux Wireless

[RFC wireless-next 0/2] wifi: allow tagged control packets

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

 



Hello,

Base on EasyMesh spec:
If a Multi-AP Agent configures a Primary VLAN ID, the Multi-AP Agent
shall send EtherType 0x888E frames on a Wi-Fi link in a Multi-AP Profile-2
Network Segment with an 802.1Q C-Tag with VLAN ID equal to the Primary VLAN ID.

Today I see BRCM agents already tag EAP frames when we enable
EasyMesh traffic separation.

This is initial version I tested using Mediatek mt7915e and hostapd.
Guys please check/comment.


Janusz Dziedzic (2):
  wifi: cfg80211: allow send/recv tagged EAPOL
  wifi: mac80211: allow tagged control packets

 include/net/cfg80211.h       |  3 ++-
 include/uapi/linux/nl80211.h |  5 +++++
 net/mac80211/cfg.c           |  3 +++
 net/mac80211/ieee80211_i.h   |  3 ++-
 net/mac80211/iface.c         |  2 ++
 net/mac80211/rx.c            | 40 ++++++++++++++++++++++++++++++++++++
 net/mac80211/tx.c            | 24 +++++++++++++++++-----
 net/wireless/nl80211.c       | 11 +++++++++-
 net/wireless/rdev-ops.h      |  5 +++--
 9 files changed, 86 insertions(+), 10 deletions(-)

-- 
2.43.0





[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