Deployment

I'm new to iperf and wonder if my results are good or should I be expecting more.  :)

This test is between two BaseBox5's .... both operating at 27 dbm at a distance of about 5 km.  One is using an mANT 19S sector antenna and the mobile station is working into a mANT 30.  I've attached a couple screen shots ... iperf is reporting about 75 Mbps but when I look at the mesh status page it shows:  100%  100 %  144.3 TxMbps     ... my question is why is one 2X the other?  Clearly I'm missing something fundamental?

It's been about a month since we deployed a version of the AREDN software with a patch designed to mitigate network routing storms across the SoCal network.  Developed by Tim KN6PLV, the patch is actually pretty benign; it just makes OLSR, the routing daemon, somewhat smarter about recognizing storms and suppressing them.  Think of it as a vaccine for the network

It's Linktober!  "Meshoween" is coming :-)

We've found that as networks grow both in node count and complexity, it's almost inevitable that they'll suffer from a packet storm (or storms) eventually.

Now that the patch for mitigating those network packet storms has been rolled into an AREDN nightly build, we've decided that it's time to stress-test our network.  On October 30th (starting at say, 9 a.m. local time) we'll attempt to link as many networks together to see how the network behaves.  If you have a long-haul tunnel that you can bring up, feel free to do so.

 Tim KN6PLV submitted a PR to AREDN containing 16  code optimizations intended for improvement of the Mesh Status page performance.  AREDN merged the commit and nightly build 622 is available containing them. 

If you're interested in the details and discussion, you can read about it here: https://github.com/aredn/aredn/pull/157

Many of you have seen the long-standing issue of an AREDN node upon rebooting, broadcasting only its IP address rather than hostname plus IP address.  It's far more common with newer hardware with faster CPUs than older gear.  An OLSR restart via the Advanced Configuration tab would fix it, but it was really annoying.  It was suspected to be a timing issue but was never resolved - until now.