svn commit: r317728 - head/tools/tools/net80211/scripts

[Adrian Chadd]

Author: adrian
Date: Wed May  3 07:53:15 2017
New Revision: 317728
URL: https://svnweb.freebsd.org/changeset/base/317728

Log:
  [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.

Modified:
  head/tools/tools/net80211/scripts/setup.wdsmain

Modified: head/tools/tools/net80211/scripts/setup.wdsmain
==============================================================================
--- head/tools/tools/net80211/scripts/setup.wdsmain	Wed May  3 05:45:43 2017	(r317727)
+++ head/tools/tools/net80211/scripts/setup.wdsmain	Wed May  3 07:53:15 2017	(r317728)
@@ -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