* 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
* 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.
Bug: Changing the NTP setting in the new UI did nothing. Now it does.
Feature: Add 'continually' mode which is traditional always running NTP.
Dont use on nodes with limited RAM.
* Add missing required fields to static WAN setup
* Dont display 'null' for missing wan fields
* Provide default static wan addresses otherwise the new UI cant set them
The UI uses opkg to check package status which can cause a lock clash
if the reinstall script is running. Retry opkg commands in the script
if this happens, and also avoid reading package status in the UI until
the reinstall is complete.
* First draft of advanced DHCP option specification on Ports tab.
Allows the node administrator to specify additional DHCP options that
will be supplied to LAN clients in specific circumstances. This change
adds two tables to the Ports configuration tab.
The "Tags for Advanced DHCP Options" table allows the administrator to
specify DHCP tags that will be assigned to clients that identify
themselves with specific values for properties such as Vendor Class or
MAC address.
The "Advanced DHCP Options" table allows the administrator to specify
arbitrary DHCP options to send to any client, or only to clients with a
specific tag. Option numbers can be entered directly or chosen from a
list of well-known options. Option values are manually entered by the
administrator.
In-browser validation is implemented for all input fields with easily
recognizable content such as host names, MAC addresses, and port and
option numbers. Placeholders are also supplied for input fields, such as
MAC addresses with wildcard matching, that might otherwise be difficult
to describe.
Issues with the current version:
- Sending DHCP options not requested by the client is implemented using
the dhcp_option_force UCI configuration option, but does not currently
work.
- Tagging by client host name is supported by dnsmasq, but not yet by
UCI.
- DHCP option values must be entered manually by the administrator, but
are not currently validated.
* Better validation, placeholders, and hints for existing input fields.
* Remove junk accidentally inserted in comment.
* Preserve Advanced DHCP options across updates.
Tim Wilkinson