freebsd-skq

History

adrian a1e2ea9f0a [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.		2017-05-03 07:53:15 +00:00
..
bsdbox	DIRDEPS_BUILD: Build crunchide for the host.	2016-09-01 23:52:25 +00:00
build	Remove NATM configuration bits and assorted NATM and ATM remnants.	2017-04-25 21:59:34 +00:00
bus_space	Add an example program (in Python) for the AMD Am79c900 (ILACC)	2015-08-02 21:24:03 +00:00
debugscripts	Assorted grammar, spelling and punctuation fixes.	2015-12-15 13:04:44 +00:00
diag	Fix LDADD/DPADD that should be LIBADD.	2015-12-04 03:17:47 +00:00
ifnet
kerneldoc	Remove EISA bus support for add-in cards. Remove related kernel and	2017-02-16 21:57:35 +00:00
KSE
LibraryReport
regression	gctl_test.t: catch errors with the mdcfg directive	2017-04-23 02:30:06 +00:00
sched	Add a dtrace script for collecting schedgraph data	2016-11-18 02:29:09 +00:00
test	Eliminate a "format string is not a string literal" warning.	2017-03-21 22:21:29 +00:00
tools	[net80211] add another hard-learnt lesson about DWDS setup	2017-05-03 07:53:15 +00:00
install.sh	Use -n to ln(1) which is compatible with GNU ln(1).	2015-11-16 23:27:44 +00:00
make_libdeps.sh	Avoid rs(1) hitting LINE_MAX with custom trees that have large dependencies.	2014-09-08 17:01:30 +00:00
README
tinder.sh	Remove the old depend (mkdep) code and make FAST_DEPEND the one true way.	2016-03-30 23:50:23 +00:00

README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.