* Initial OpenWRT 23.05.0 merge
* Fix get_rfchannels for new iwinfo format
* Fix initial wlan name
* Move patches to 5.15 from 5.10
* Fix flash write problem on Ubiquiti devices
* Use new ssl patch
* Reduce binary sizes
* Have to have hostapd installed now, even on tiny builds
* Simplify device support
* Revert Mikrotik NAND sysupgrade system.
OpenWRT doesnt really support Mikrotik NAND devices after 2019 and the
new support appeared broken. So reverted to the 2022 mechanism which does
work and avoid upgrade problems.
* Fixes for tiny builds
* More tiny shrinking
* Fix newly added firewall rules
* Update permanent packages
* Update permanent packages
* Support for Nanobeam 2AC (2.4GHz) device. 20MHz channels only.
* Update support
* Add GL.iNet B1300
* Add to radios.json
* Update supported devices
* Dont force the LAN DHCP to run
* Revert CURL SSL test
* Fix radio count when there are no radios
* Switch the lan ports on the gl-b1300
* Add support for GL.iNET Beryl MT1300
* Fix visual lat/lon setting bug
* Make the setup "Save Changes" button also save the location data
* Fix location/map system with geo location fallback
* Recolor
* Fix default bandwidth selection
* Support multi-band radios
* Generic mechanism to set compat version to 1.1
* Switch ethernet ports
* 20 MHz channels only
* Update docs
* Add ham channels to Mediatek chips (20MHz only)
* Automatically update the permpkg list when we upgrade
* Fix 10MHz mode for Ubiquiti AC devices
* Fix tiny builds
* Bump the watch timeout for restarting olsrd
olsrd is reliable these days, and very occasionally this
was restarting it unnecessarily
* Remove vestigial getServicesBy* methods
getServicesByNode is only a dummy method.
getServicesByService doesn't even exist.
Remove the last remaining references to them from cgi-bin/api, and remove the last traces of getServicesByNode from aredn/olsr.lua
Fixes#948Fixes#949
* Bump API version
Breaking change, removing parameters services=bynode,byservice
* Subdomain check too slow for realtime
so now do it in the namecheck service instead.
* Dont commit to VPN address until we set the DNS name
helps supernode setup
* Supernode option
* Change supernode 10/8 route injection.
Identify supernode in sysinfo.json
* Supernode tunnels use port 5526
* Advertise supernode-ness
* Update DNS if supernodes are available
* Open up supernodes DNS service to incoming mesh requests
* Simply nameserver update
* Support supernodes on hap ac2
* Improve supernode nameserver update reliability
* Rework how supernode nameservers are managed
* Improve supernode dns advertising
* Add super mesh button
* User supernode name not ip in advert
* Less intustive way to identify supernode dns
* Add supernode ignore options
Change supernode enabled -> enable
* Improve DNS updates
* Remove tunnels when switching to/from supernode mode
* Blackhole any unknown routes on the supernode to avoid recursing packets
* Add explicit reverse lookup rule for supernode when available
* Just use dnsmasq changes for both forward and reverse names
* Improve supernode detection
So it doesnt keep writing to flash
* Add reverse tunnel ip lookup to supernode
* enabled => enable
* Supernode tunnels start 172.30
* Remove supernode switch
* Simplify supernode check
* Fix nav test
* Unify mesh status search functionality
* Remove colored titles
* Fix highlight colors
* Removed use of CSS :has(...) operator which Firefox doesnt support
* Make identifying tunnels more general
* Delay search while typing
The arp cache keeps wifi entries long past them being associated with
the node, so now use wifi assoc list to find nodes, and the arp cache
to get their IPs.
This is an attempt to unify all the station monitoring and make it work
better as one. We're trying to square a circle here somewhat, with taking
steps to kick nodes when problems are detected, but not kick them too quickly
or often in case we're mis-identifing issues.
We've seen these issue manifest themselves which nodes messing VoIP services
as well as resets causing nodes to get into unrecoverable states when there
was no real problems in the first place.
This will probably need to evolve before the next release, but would be good
to get some milage on the new code.
Coverage is handled by modifying firmware state, and the driver stores
the values the first time it is set. When we reset this state might be lost
so it will be reloaded from the firmware. We set the coverage back to 0
so the reloaded value will be the default again.
We also remove a check which can fail incorrectly.
Tim Wilkinson