* Enable RTS/CTS when we detect hidden nodes
* Only change rts setting when we need to
* RTS advanced config option
* Include neighbors blocked neighbors (they still transmit)
* Bump default RTS threashold
* Report list of hidden node rather than yes/no
* Canonical hostnames
* When we enable RTS, enable it for all traffic by default
* Show hidden neighbors in display
* Default RTS threshold to -1 (always off)
The connec timeout did not include DNS looksup, and if DNS is broken this can hang forever. Add
a maxmimum timeout so this call will eventually terminate regardless.
When a tunnel is idle, binding to the tun* device fails; so remove it.
As we have a direct tunnel route in the routing table (not OLSR table 30)
created by vtun, we will still correctly route the quality testing traffic.
* Tag devices which must be reinstalled.
Looks like the NAND layout for a few Mikrotik devices has changed
sufficiently that they cannot be easily upgrade and must be reinstalled
from scratch. Note this in the SUPPORTED_DEVICES matrix.
* Improved language
There's a bug where 2.4GHz channels will associate incorrectly with other 2.4 channels
even though they are on different frequencies. The problem appears to be triggered during
scans when scan probes are sent and received on many different frequencies, but are then
reported as as they arrive as if they come from the selected frequency of the device, causing
incorrect stations to be created. This can only occur for IBSS (adhoc) mode, when the
IBSS frequency is fixed, and when the SSID is also fixed. We do all this for AREDN.
Fortunately these probe contains (but *only* on 2.4 GHz) the actual frequency of the sending
device, so we can avoid incorrectly creating stations which are not really a match.
This situation does not seem to happen on 5GHz channels.
e Please enter the commit message for your changes. Lines starting