<div dir="ltr">Hi,<div><br></div><div>as I said when you contacted me I like the work you did for the graphs...</div><div><br></div><div>oh, I also uploaded my whole "battlemesh" folder to Google Drive... it contains my measurement scripts, the configuration of all 10 mesh nodes and the results of all tests.</div><div><br></div><div><a href="https://drive.google.com/file/d/0B73bEek-LDc5MWZRZGprZXhwc2s/view?usp=sharing">https://drive.google.com/file/d/0B73bEek-LDc5MWZRZGprZXhwc2s/view?usp=sharing</a><br></div><div><br></div><div>it is ~ 1.5 MByte</div><div><br></div><div>Henning</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 21, 2015 at 8:24 PM, Benjamin Henrion <span dir="ltr"><<a href="mailto:zoobab@gmail.com" target="_blank">zoobab@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, Aug 21, 2015 at 7:47 PM, Nemesis <<a href="mailto:nemesis@ninux.org">nemesis@ninux.org</a>> wrote:<br>
> Hi everybody,<br>
><br>
> this is a request for feedback: comments, suggestions and pull requests.<br>
><br>
> See here:<br>
> <a href="http://battlemesh-test-docs.readthedocs.org/v8/index.html" rel="noreferrer" target="_blank">http://battlemesh-test-docs.readthedocs.org/v8/index.html</a><br>
><br>
> Before starting to work on it I exchanged a few ideas via chat with Amadeus<br>
> and Henning.<br>
><br>
> Here's a quick recap:<br>
><br>
> having all the results on one page would have made it quite hard to read<br>
> so the tests have been split in 3 pages<br>
><br>
> mesh of adversity: one single stream from client (connected to A) to server<br>
> (connected to K)<br>
><br>
> reboot<br>
> ping<br>
> ping + iperf<br>
><br>
> crossed streams jeopardy: two streams, client A to server K and node D to<br>
> node H<br>
><br>
> 10 mbit iperf streams<br>
> 100 mbit iperf streams<br>
><br>
> blowing up the network: tests performed with Flent by Toke<br>
><br>
> Realtime Response Under Load (RRUL)<br>
> Realtime Response Under Load Best Effort (RRUL_BE)<br>
> 8-stream download test<br>
> TCP upload<br>
> TCP download<br>
><br>
> As you can see, there are quite a few things that can be improved!<br>
><br>
> some graphs are missing (some purposely and some I was not able to generate<br>
> properly)<br>
> english needs to be checked<br>
> it would be good to provide some additional explanation to the graphs<br>
> shall we add a conclusion section to each page? if yes, anybody willing to<br>
> propose a conclusion?<br>
> shall we add a last "lessons learned" page with all the things that went<br>
> wrong and the proposed solutions for the next edition?<br>
<br>
</div></div>From what I have heard in the videos, none of the routing protocols<br>
resists network saturation.<br>
<br>
Maybe adding a QOS rule for packets belonging to routing protocols would help?<br>
<br>
--<br>
Benjamin Henrion <bhenrion at <a href="http://ffii.org" rel="noreferrer" target="_blank">ffii.org</a>><br>
FFII Brussels - +32-484-566109 - +32-2-4148403<br>
"In July 2005, after several failed attempts to legalise software<br>
patents in Europe, the patent establishment changed its strategy.<br>
Instead of explicitly seeking to sanction the patentability of<br>
software, they are now seeking to create a central European patent<br>
court, which would establish and enforce patentability rules in their<br>
favor, without any possibility of correction by competing courts or<br>
democratically elected legislators."<br>
_______________________________________________<br>
Battlemesh mailing list<br>
<a href="mailto:Battlemesh@ml.ninux.org">Battlemesh@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/battlemesh" rel="noreferrer" target="_blank">http://ml.ninux.org/mailman/listinfo/battlemesh</a><br>
</blockquote></div><br></div>