[Battlemesh] Mesh Routing Protocol Comparison

Dave Taht dave.taht at gmail.com
Sat May 2 03:00:25 CEST 2020


The core of a simple test with your setup, is merely to try carrying
1000+ routes. You don't need
more nodes.

On Fri, May 1, 2020 at 5:50 PM Moritz Warning <moritzwarning at web.de> wrote:
>
> Hi Dave,
>
> thanks for the input.
> I really hope that I can test 1000-2000 nodes at some point. I find scaling properties of networks to be the most interesting aspect.
> But testing is hard, of course.
>
> Testing under load can be tried when I limit link quality. So far they are unlimited.
>
> On 5/1/20 6:27 PM, Dave Taht wrote:
> > I keep hoping y'all will actually test networks like this under load,
> > rather than idle.
> >
> > The flent rrul test is always a good start, and the rtt_fair tests in
> > particular, let you exercise multiple nodes on the network. Monitoring
> > convergence time under that kind of repeatable load, is quite
> > fascinating.
> >
> > also you should update to babel 1.9.2 and fiddle with the unicast mode.
> >
> > You can have even more fun with my infamous "rtod" tool (
> > https://github.com/dtaht/rtod ). If you are at all like me, it's
> > really exciting to see what happens when you put more than 1000+
> > routes on the network (mostly ipv6). I don't know what actually
> > happens with all these other routing protocols, but then again, I was
> > always the kind of kid that tossed lithium in water or aimed bottle
> > rockets at my friends...
> >
> > On Fri, May 1, 2020 at 4:17 AM Moritz Warning <moritzwarning at web.de> wrote:
> >>
> >> Hi folks,
> >>
> >> I wrote a virtual test setup that supports multiple mesh routing protocols and produces nice graphs.
> >> The whole setup is based on Linux network namespaces:
> >>
> >> https://github.com/mwarning/meshnet-lab
> >>
> >> So far, there are some preliminary results with a focus on convergence, mobility and scalability.
> >>
> >> https://github.com/mwarning/meshnet-lab/blob/master/results/README.md
> >>
> >> Keep in mind that these results are not "final" yet, as hardware limitations and pathological behavior play a dominat factor in some of the results.
> >> I hope to be able to present the refined results at the next Battlemesh and have a lively discussion!
> >>
> >> Best,
> >> mwarning
> >>
> >> Btw.: if you happen to have beefy server with good CPU/IO speed - let me know.
> >> _______________________________________________
> >> Battlemesh mailing list
> >> Battlemesh at ml.ninux.org
> >> https://ml.ninux.org/mailman/listinfo/battlemesh
> >
> >
> >
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> https://ml.ninux.org/mailman/listinfo/battlemesh



-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729


More information about the Battlemesh mailing list