[net80211] add another hard-learnt lesson about DWDS setup
wlanwds monitors the physical interface for DWDS requests from VAPs, but the clone is created against the physical interface. So, if you have a secondary VAP setup (with a separate, non-physical-default MAC address) which is configured for DWDS, the temporary DWDS VAPs created will have the MAC of the parent physical interface and NOT the actual cloned interface + MAC. This .. stumped me for a few minutes. Maybe I'll fix it. Maybe I won't. At least I now have DWDS+encryption working at home. Tested: * yes, with DWDS 11n repeaters now working on freebsd.
This commit is contained in:
parent
b0168423b6
commit
75a790cc57
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=317728
@ -15,6 +15,13 @@
|
||||
# otherwise frames transmitted from the WDS AP to the WDS STA
|
||||
# will not be encrypted.
|
||||
#
|
||||
# * Because wlanwds is running on the physical interface (for now),
|
||||
# and NOT the parent VAP, it will create cloned interfaces using
|
||||
# the MAC address of the physical interface. So, until that
|
||||
# whole setup is fixed, please only associate DWDS to the first
|
||||
# VAP on a physical interface, which shares the MAC address of
|
||||
# the physical NIC.
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
PATH=.:$PATH
|
||||
|
Loading…
Reference in New Issue
Block a user