Had attempt to optimize restarting olsrd by putting more tunnel devices
in the config file by default. Unfortunately, olsrd can't cope with too
many and performs poorly.
Added a comment at the top of /etc/config.mesh/network to inform node
admins how to override the network configuration for unusual and unique
network configurations. See issue #995 for explanation of when overrides
may be useful.
Relates-to: #995
Signed-off-by: Gerard Hickey <hickey@kinetic-compute.com>
* Support antenna selection and allow heading to be specified
* More antennas
* Heading -> Azimuth
* Ubiquiti's catalog
* Add Mikrotik builtin antennas
* Some Ubiquiti builtins
* JP Performance Antennas
* Added Altelix
* More Altelix
* More radios
* Add elevation
* Add generic omnis, sectors and dishes
* Improve selection
* Improve display for non-wireless devices
* Improve omni and builtin setup
* mode -> model typo in antennas.json
* Typos
* Fix bad gateway when saving
* Add antenna height above ground level.
Fix more bad gateways
* Update antennas.json
* More radio antennas
* More antennas
* Enable dd-wrt firmware for Ubiquiti devices
* Dont include the wifi monitoring interface by default
We dont use it for anything
* Remove package which clashes with new firmware
* Disable chatty warning message
* Missed patch
* Wireguard tunnel support
* Fix wireguard firewall rules
* Add Wireguard tunnels to LQM
* Filter vlans on main bridge
* If you paste a tunnel config into any field, it will auto-populate all fields correctly
* Fix bad password keyword
* Fix bad feeds change
* Fix bad merge
* 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.
* A scan, especially if we have to do both active and passive, essentially mutes
the radio to AREDN traffic for 10-20 seconds, which isn't good. If the radio is completely
deaf then it doesn't matter, but particularly on the 9K radios we do this when
things are looking a bit dodgy, though not deaf.
* Provide hook to reset ath9k from userspace. This hook is attributed to:
Linus Lüssing <ll@simonwunderlich.de>
* User /sys reset hooks rather than iw scan
* Make admin and user bar menus pluggable
* Realign header block to stop is moving around
* Remove ref
* Use modular nav to disable ineligable options during initial install
* Dont offer tunnel menus options when no tunnel daemon installed.
This is for low-memory devices
* Simplify
* Improve messaging when running ram image
* Disable rather than hide vpn menu items on tiny memory devices
* Move menu navs
* Use LQM information to filter out neighbors we dont care about.
These can cause false rejoin events and degrade the network.
* Only use active station monitor with LQM info.
* Resolve unresponsive node problems with Mikrotik AC devices.
Mikrotik AC devices get into a state where they wont communicate with
non-AC devices .. sometimes. Leaving and rejoinging the network resets
everything. We monitor for this situation and rejoin the network when detected
to resolve the issue.
* Make reporting less chatty
* General station monitor service.
It turns out this station bug is not limited to the ath10k driver, so
make this monitor service wifi generic.
(I've now seen this at both ends of the Mikrotik AC <-> Rocket pair)
* New logs
* Just monitor for now
There appears to be a bug in the ath10k firmware for Mikrotik devices (maybe others)
where a station will associate but only broadcast traffic will be passed - unicast traffic
will fail. This code detects this situation and forces the device to reassociate which
fixes the problem.
When people are using the filters on the mesh page, they sometimes
hit RETURN. This submit the page (which is a form) causing the page
to reload, lossing the filter, and as a side effect, setting the page
to auto-refresh.
* Track validation state of hosts and services. Only remove a host/service if it fails multiple times in a row.
* Let new addresses/services be valid for a while regardless
* Initially unknown addresses will be valid for a while
* Reset validation state when services updated
* Fix the bandwidth reporting for ath10k devices
* Use 'iw' for all TxMbps reporting.
As we cannot account for error rates in the ath10k driver, to be consistent
we now use the same system to retrieve tx rates for both ath9k and ath10k.
* Remove unused rate tables
On small networks there are not a lot of OLSR name changes. While
dnsmasq watches for changes and updates itself, it will sometimes miss
them. On busy networks this doesnt matter as the next change will catch
it up. But on smaller network (esp. test networks) a missed change can
stop name resolution working for some time. So now, if no changes are
detected for > 60 seconds, we force dnsmasq to reload its tables.
For some reason, there was code in the driver to block the setting of
the coverage when a previous setting wasn't a particular value.
It's unclear what this was trying to achieve or prevent, but it stopped AC
devices operating efficiently (by a factor of 10x or more).
This cryptic bit of shell script adds a maximum timeout for the iperf client
to run as it appears it can get stuck occasionally. The server has a built-in
timeout (not available in client mode)
Tim Wilkinson