[Battlemesh] Routing Tables of Death

[Simon Wunderlich]

It's not exactly stress testing and doesn't apply for the routing protocols 
you mentioned, but maybe you will find the joker interesting:

https://www.open-mesh.org/projects/open-mesh/wiki/Joker

I'm sure that some of those ideas can be adopted for other protocols as well.

Cheers,
      Simon

On Tuesday, March 7, 2017 10:00:31 AM CET Dave Taht wrote:
> I have been stress testing multicast (after getting ATF to work on
> unicast this past year), and ended up rolling a few tools that let me
> abuse it in the case of meshy routing protocols.
> 
> Last night's effort is called "rtod - routing tables of death".
> 
> The initial code is here:
> 
> https://github.com/dtaht/rtod
> 
> I hope you find the README enlightening. Emphatically, do not run rtod
> on a production mesh network. I did. Multiple times. It took hours to
> fix.
> 
> I'd like to add conf files for various daemons (bmx, batman, olsrr)
> that will both enable this tool - and, more importantly,
> configurations that will filter out the routes rtod inserts.
> 
> ...
> 
> It would be "interesting" to run stress tests like these at the next
> battlemesh.
> 
> ...
> 
> If anyone can point me at other routing stress test tools they use,
> or can suggest additional features for rtod, please let me know. I
> have a few features left to add to it as yet.
> 
> My intent was originally to merely to stress out wifi multicast, but....

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20170307/f68fab4e/attachment.pgp>