OLSR has rare symptoms of live lock and stops
updating routing and host information. Suspect cause is
single threaded implementation with plugins continually
called from mutiple sources. Prior fixes to ensure
read/write calls are properly written may not have
fully resolved the causes. This change will reduce calls
to retrieve olsr data.
Mesh status will show service entries of a remote mesh
node at the top with 0 ETX value. The owning mesh hostname
displays blank across the mesh network.
The root cause is OLSR not propagating the node's hostname due
to the admin assigning a conflicting/duplicate hostname. These
services will no longer show in mesh status.
* Add experimental support for the GL.iNet GL-AR150 - https://openwrt.org/toh/gl.inet/gl-ar150
Mesh networking and tunneling have been confirmed working.
This device has been confirmed capable of operating on channel -1, but /etc/config/wireless has to be manually edited to select this channel.
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150 - seems like only 18 dBm TX power is possible
* Remove Experimental comments and designate as stable
* Configure Ethernet ports & VLANs for GL-AR150, and update README.md
* Fix misunderstanding re README.md
* Patch Upstream OpenWRT GL-AR150 LAN & WAN LED mapping, configure WLAN LED as mesh linked indicator.
* sysinfo.json additions
lua library additions
Dependent on #389 and #391
Replaces #387
* additional check for nil needed
tested on a node with several very marginal RF links (IP, no host name) and it is working, so far.
also removed the decimal point on the n/lq values, we didn't need 10 places of accuracy. :)
* a couple more small changes
* changed neighborLinkInfo() function in aredn.info to show *all* links, not just RF.
Adds additional info for each RF link (tx/rx_rate, noise, signal)
* Removed redundant function.
Removed functions no longer needed.
Reworked getCurrentNeighbor function to add in the additional RF link info if requested.
10MHz channel width is most commonly used. This default
will minimize how many new users are unable to connect
to a local mesh on first try. In 2GHz use ch -2
as only clear part 97 10MHz channel available and
predominently used.
* wscan can output results as json
* added a page for displaying scan results as json
* updated file permissions with +x
* added endpoint for wifi scan
* Revert "updated file permissions with +x"
This reverts commit 6f0a038334fbacc3f585f0a86fb7d9986a47b7d2.
* Revert "added a page for displaying scan results as json"
This reverts commit 4806ad01b6b717e2e02f248309a0257bb390af23.
* Revert "wscan can output results as json"
This reverts commit 75454e7e790a0457a0846182b0a8a44205772368.
* removed hardcoded device name
* exposed freqlist through the api
* moved signal.json code into the api
* old signal page uses /api?page=chart
* removed signal.json
* chart has targets for realtime and archive
* updated old signal page to use new api
* wscan can output results as json
* added a page for displaying scan results as json
* updated file permissions with +x
* added endpoint for wifi scan
* Revert "updated file permissions with +x"
This reverts commit 6f0a038334fbacc3f585f0a86fb7d9986a47b7d2.
* Revert "added a page for displaying scan results as json"
This reverts commit 4806ad01b6b717e2e02f248309a0257bb390af23.
* Revert "wscan can output results as json"
This reverts commit 75454e7e790a0457a0846182b0a8a44205772368.
* removed hardcoded device name
* exposed freqlist through the api
This reverts commit d5be7814b3.
Auto Distance is not ready for a release and will be
reintroduced afterwards. Added logic to reset '0' distance
to 60km so tower nodes will continue to respond after
upgrade if running the experimental auto distance
Joe Ayers