upstream/opnsense-src
1
0
Fork 0
mirror of https://github.com/opnsense/src.git synced 2026-04-29 01:59:38 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

[net80211] add another hard-learnt lesson about DWDS setup

Browse source 
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:
Adrian Chadd 2017-05-03 07:53:15 +00:00
parent b0168423b6
commit 75a790cc57
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
tools/tools/net80211/scripts/setup.wdsmain
View file

@ -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