* Add files via upload
* Update SUPPORTED_DEVICES.md
Change "AC 5" and similar identifiers for selected UBNT 5GHz AC nodes to match UBNT catalog descriptionsl
* Delete SUPPORTED_DEVICES.md.5ACedit.txt
* Enable AltNet support
* Fix pattern
* Remove dhcp_limit
* Rework LAN start/end for larger or smaller subnets
* Improve subtext help around settings
* Whitespace
* Add locking around operations which change the configuration.
Avoid any potential race conditions when changing the configuration
by putting a lock around any non-GET operations.
* Add a sync before a 'reboot' operation
* Remove old UI
* Remove old ui link from new ui
* Remove unused library
* Trim luci.http
* Remove old firmware path
* Remove protected pages that no longer exist
* Mobile layout work
* Title bar
* Test dialogs
* Login/logout
* Mobile formatting
* More space in dialogs
* Mesh page
* Deselect keyboard
* Mobile formatting
* More field changes
* Nightly build fixes.
Restarting the nightly build with many changes resulted in updates
failing to be applied on some hardware platforms. This resulted in nodes
reverting to first use state. These changes fixes those problems.
* Fix authentication
* Improve the initial nrvam setup
* More fallbacks
* Rebuild the initial setup and upgrade of a node.
This is mostly about removing duplicated effort and data, which should
make it easier to add things in the future.
* Re-setup and repair the node on each reboot.
By running this every time we reboot, we have a chance to repair problems in the configuration
automatically. We can detect changes and force a reboot only when necessary.
* Improve startup and upgrade
* Remove debug delays
* Move after telnet (for emergency access)
* Ignore ubootenv file when diffing
When update-clock is run periodically, if ntpd is running continuously,
check whether it is actually in sync, as measured by a reported stratum
of less than 16.
If it's not in sync, run the full manual clock sync algorithm otherwise
used for our periodic-only synchronization.
This should help with hosts that expect to synchronize from an NTP server
on the internet, for example, when they've temporarily lost the internet
connection. Or alternately, if configured to use a mesh-based NTP server
that has disappeared from the mesh.