[MVMA] [socal-hamnet-users] AREDN Nightly Build updates

[Chuck Gelm]

On 8/30/20 4:01 PM, Orv W6BI wrote:
>
> The latest AREDN nightly release has some nice changes:
>
>   * Those confusing check boxes on the Advanced Configuration page
>     have been changed to sliders to make their use a bit clearer.
>
>   * AREDN has added Local Alerts capabilities. Nodes can now subscribe
>     to a URL (defined in Advanced Configuration) to retrieve any local
>     alert messages.
>
>
> This results in something like this:
>
> Configuring it and the alert server are explained very well at the 
> bottom of this page: 
> https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_config.html. 
> Note that local alerts can be configured for specific nodes, or all 
> nodes watching a given alert server.
>
> If you elect to put the alert text files on a web server, the alerts 
> directory will have to be under the root of the web server.  In the 
> above example, the directory aredn_alerts is actually 
> /var/www/html/aredn_alerts (standard for the Apache web server).
>
>   * The Advanced Configuration warning banner has been made slightly
>     wider to distinguish it from the Alerts banner.  A WARNING has
>     been added and the text color has been made pure white for contrast.
>
>   * And maybe most importantly, you're now able to choose whether or
>     not to have your nodes DHCP leased host names & IP addresses
>     propagated over the rest of the mesh network or not.  It defaults
>     to allowing them propagate.
>
> The host name/IP will still be resolvable from the localnode and will 
> show up in the list of hosts on the localnode only. This allows for 
> selected local AREDN network devices (e.g., switches, routers, 
> cameras) to not be available over the rest of the mesh network.
>
> In this example, I've stopped the addresses and host names of a local 
> switch and wireless access point from propagating.
>
> As it's adopted and applied across the network this will shrink the 
> size of the mesh status page, making it a bit easier to review.  (Here 
> in Southern California there are about 500 nodes and a thousand lines 
> on the mesh status page).
>
> More importantly, it will shrink the size of the OLSR routing table 
> (and thus the size of the routing broadcast), easing the load on 
> older, lower-performance nodes and potentially help stabilize large 
> networks.
>
> Comment from the author, KG6WXC:
>
> "This will work immediately for new DHCP leases when the checkbox is 
> selected.  For existing DHCP leases, it may take a while for the 
> network to update, if ever.
> To speed up the process of full network OLSR DNS updating, reboot all 
> the nearest neighbor device(s) to the node you made these changes to.  
> That seems to get the changes "out" to the rest of the network faster 
> than normal."
>
> I encourage everyone to consider updating to this nightly build and 
> utilizing the Do Not Propagate feature as it makes sense for your QTH.
>
> 73
>
> Orv W6BI
>
> _._,_._,_
> ------------------------------------------------------------------------
> Groups.io Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#1401) 
> <https://groups.io/g/socal-hamnet-users/message/1401> | Reply To Group 
> <mailto:socal-hamnet-users at groups.io?subject=Re:%20%5Bsocal-hamnet-users%5D%20AREDN%20Nightly%20Build%20updates> 
> | Reply To Sender 
> <mailto:orv.beach at gmail.com?subject=Private:%20Re:%20%5Bsocal-hamnet-users%5D%20AREDN%20Nightly%20Build%20updates> 
> | Mute This Topic <https://groups.io/mt/76520875/1794240> | New Topic 
> <https://groups.io/g/socal-hamnet-users/post>
>
> Your Subscription 
> <https://groups.io/g/socal-hamnet-users/editsub/1794240> | Contact 
> Group Owner <mailto:socal-hamnet-users+owner at groups.io> | Unsubscribe 
> <https://groups.io/g/socal-hamnet-users/leave/8344379/595799297/xyzzy>
>
> _._,_._,_

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200830/18cf8ba2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llmmhhljbmkoggba.png
Type: image/png
Size: 44766 bytes
Desc: not available
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200830/18cf8ba2/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ldfdkglbnkeefcfb.png
Type: image/png
Size: 34967 bytes
Desc: not available
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200830/18cf8ba2/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gmhebaonkdaoglfm.png
Type: image/png
Size: 28448 bytes
Desc: not available
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200830/18cf8ba2/attachment-0005.png>