[MVMA] Meeting at BARC 9:30 AM Saturday

[Chuck Gelm]

Found on the MVMA web site:

/*"Technical Challenges:*// Growth of our network infrastructure has 
enabled us to better understand our mesh performance limitations. //
//While there is no imminent technical threat to our operations, *it is 
clear that the failure of the routing protocol used by AREDN, to 
correctly manage traffic across the mesh, impacts our operations*.  Both 
Chuck Gelm (NC8Q) and Moe Riggins (AB8XA) deserve MVMA hero badges for 
the work they have done to study, define, and document these issues, and 
to find a “work-around” solution that meets our immediate needs. //
//However, I believe the work-around solution forces a tradeoff of 
network performance (link speed and capacity) vs. network resiliency and 
survivability for EmComm applications. //
//These tradeoffs need to be carefully considered by a steering 
committee representing both EmComm and Technical communities. //
//Additional detail regarding my perception of this issue may be found 
at the end of this letter."//
/
IMHO, the AREDNMESH routing protocol works just fine. *It fails when a 
network fails to provide stable links.*
OLSR will not fix an unstable network.

Assuming the same number of node devices; in my view the trade-off is:

(1) a group of nodes with resiliency, but with reduced speed and capacity
.vs.
(2) a group of nodes with speed and capacity, but with reduced redundancy.

(1) Adding more single node sites on 2397 MHz reduces speed and capacity 
throughout the entire network.
      Previously, it was shown that reducing the number of nodes 
increased speed and capacity while reducing redundancy.
      It is shown that a 'work around' can return some measure of speed 
and capacity while reducing redundancy.

(2) Adding DtD'ed multi-node sites increases speed and capacity.
*This may increase redundancy if omni-directional or sector antenna 
patterns are used.**
* *Example: Adding channel 182 nodes increased redundancy, speed, and 
capacity of Beavercreek<>Xenia.**
*
Chuck


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20181108/851ede0e/attachment.html>