This adds support for 802.11n data rates on the mesh.
This should improve dataspeeds across the board
MIMO devices like Rocket and NanoStation should be able to use dual chains which allows diverse data transmission on each chain increasing throughput
MCS data rates in theory should cut through noise better than legacy modulation and have higher speeds on each step which should allow overall higher datarate between nodes.
Merging in latest release-3.15.1.0 changes into develop to provide a foundation with recent release fixes for the develop branch.
This should be 3.15.1.0b03 code.
Conflicts:
files/etc/crontabs/root
files/usr/local/bin/wscan
files/www/cgi-bin/sysinfo.json
We don't really need any files in there, and keeping the folder can interfere with the programs that populate /etc/aredn_include on firstboot from uci-default.
This will cause the node to boot up in default mode (with an AP on its interface on the default channels) during its first boot, and than very quickly reboot and come up under the mesh.
Not getting much debug information at moment, would like to put this in uci-defaults but with issues that I can't seem to log at moment (and not having serial cable for this device) I'm going with lets put it in /etc/init.d/local before nvram and similar gets set.
ref AREDN->ticket:115
Old code would set mac on the sub-vlan not the master interface which could cause issues.
Rework to be more functional in the future and to work correctly on vlan interfaces.
ref AREDN->ticket:115
Firewall rules don't get called because vtund is at /usr/sbin/vtund not /usr/bin/vtund
Also make the check if line posix compatible while we are chaning the path to be sure it works in the future too.
Remove the chmod step inside of setup.
Came across one time where this didn't trigger.
In addition this saves us from using additional storage space on the node as a +x creates a duplicate file.
wifi detect is called in /etc/init.d/boot before uci_apply_defaults is called.
Because of this if we don't have the data about the radio0path we need to remove the wifi config file first before calling wifi detect.
Needs to be in uci-defaults to be sure these data sets execute BEFORE the OS boots
We also need to get radio0 path because its mandatory for wifi to work.
Needed for sysupgrade from 3.0.2 to latest version.
Allows nodes to default to a common channel that is in the most common bandplan space for Part 97 usage.
Local cordination is still needed by users to make sure the channel matches the local deployment.
Defaults are as follows:
Band : Channel Freq : Bandwidth
900 : 912MHz : 5MHz
2400 : 1 2412MHz : 20MHz
3400 : 3420MHz : 5MHz
5800 : 149 5745MHz : 5MHz
2.4GHz keeps channel 1 at 20MHz because it is the standard deployment.
All other bands are still 'new' and no standard exist so we are creating one.
5MHz chosen because it better fits the emcomm goal. Smaller width should be stronger allowing for better networks.
Local networks can change as they see fit.
Remove setting RF channel on first boot in uci-defaults.
This should allow the node to use standard wifi channels when it boots allowing mesh setup to be run from a laptop or mobile device.
We will later move them to a real mesh channel during the mesh setup page.
Should also resolv issue where nodes were booting up on channel -2 and similar and wifi would refuse to start due to regdomain.
Config file is present upon initial start and in mesh mode.
Daemon still starts up in other modes but will not function w/o settings.
Firewall:
Permit access for UDP:161 (SNMPD) on WIFI and DTDLINK
Lan is permitted by default allow rules.
Darryl Quinn