[Battlemesh] Battlemesh Test & Results Documentation

[Dave Taht]

On Thu, Jul 30, 2015 at 10:22 AM, Nemesis <nemesis at ninux.org> wrote:
> I guess it's copied from last year's tests, which in the end didn't
> include the babel results because a misconfiguration made the tests with
> babel invalid.
>
> See http://ml.ninux.org/pipermail/battlemesh/2015-April/003411.html

Well, this time I would like to make sure it is included, and
configured properly. Are configurations in a repo somewhere?

About the only babel dependencies are the babel daemon itself, a
consistent BSSID, and telling it what channel(s) it is on manually (as
autodetection is broken currently)

I imagine ipv6 is not on the test plan?

hnetd would be a goodness, also... but if it isn't already in there,
would be difficult to add.

> Federico
>
>
> On 07/30/2015 10:19 AM, Dave Taht wrote:
>> is there some reason why babel is not listed on any of the
>>
>> http://battlemesh-test-docs.readthedocs.org/v8/5-the-crossed-streams-jeopardy.html
>>
>> On Thu, Jul 30, 2015 at 10:16 AM, Nemesis <nemesis at ninux.org> wrote:
>>> So, Amadeus, you were looking for feedback regarding the test docs, here's a
>>> good piece of feedback.
>>>
>>> @Thijs van Veen: could you try to write a patch that shows practically what
>>> you mean?
>>> For example, this page:
>>> http://battlemesh-test-docs.readthedocs.org/v8/2-the-powerlan-conundrum.html
>>> Can be edited directly on github here:
>>> https://github.com/nemesisdesign/battlemesh-test-docs/edit/master/v8/2-the-powerlan-conundrum.rst
>>>
>>> I'll follow the developments of the tests at the event and I'll update the
>>> docs as we go. Anybody else wants to help out with this task? Having good
>>> test docs and results will surely improve the overall impact of the event.
>>>
>>> Federico
>>>
>>>
>>>
>>> On 07/29/2015 08:01 PM, Thijs van Veen wrote:
>>>
>>> Hi Federico,
>>>
>>> It looks like a great start.
>>>
>>> I like the very brief description of the hidden node issue, but I find the
>>> other descriptions a bit lacking (more focused on the setup than what the
>>> issue is).
>>> I think it might be nice to include a more formatted description of the
>>> issues.
>>> Something along the lines of:
>>> 1. What is the scenario called?
>>> 2. When/Why does this scenario occur?
>>> 3. What is the topology of the network?
>>> 4. Why is this problematic?
>>>
>>> For example, for the PowerLAN, it simply says "You create a PowerLAN setup
>>> with 3 adapters lined up like this" and goes on to say many people can
>>> benefit from it.
>>> It doesn't really specify WHY people would benefit from it.
>>>
>>> I believe this can be a very simple step towards making things more
>>> approachable for people new to networking.
>>>
>>>
>>>
>>> Also, are there any plans for testing mobility?
>>> Seeing as it is a rather difficult scenario to replicate reliably, I can
>>> understand if it's not in the scope for this year.
>>> Either way, I think it would be nice to open up this topic (how to test) for
>>> discussion at the event.
>>>
>>>
>>> --
>>>   Thijs van Veen
>>>   dicht at operamail.com
>>>
>>>
>>>
>>> On Wed, Jul 29, 2015, at 19:40, Nemesis wrote:
>>>
>>> In previous threads [1] [2] we discussed the need of having the
>>> documentation of tests and results in human readable, easily reproducible
>>> format.
>>>
>>> Today I've taken some time to help amadeus and convert his google docs to
>>> this type of format.
>>>
>>> Here I wrote a short wrap up, please read:
>>> http://nemesisdesign.net/blog/thoughts/battlemesh-test-docs/
>>>
>>> The documentation is hosted at:
>>>
>>> http://battlemesh-test-docs.readthedocs.org/
>>>
>>> Sources are available at:
>>>
>>> https://github.com/nemesisdesign/battlemesh-test-docs
>>>
>>> Feedback welcome! I hope you like it, if you do, I'll put effort to improve
>>> it during the event, hopefully showing to somebody else how to update it,
>>> it's very easy, lazy people can do it from github too!
>>>
>>> If you like it, I would like to move the ownership of the repo to the
>>> battlemesh github organization, but to do that I need temporary owner
>>> permissions on the org. Let me know what you think.
>>> My github account is: https://github.com/nemesisdesign
>>>
>>> Cheers!
>>>
>>> [1]: http://ml.ninux.org/pipermail/battlemesh/2015-June/003429.html
>>> [2]: http://ml.ninux.org/pipermail/battlemesh/2015-April/003407.html
>>> _
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh



-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast