[Battlemesh] About a testbed - what is the status

[Pau]

The protocol developers or teams who want to include their protocol into
the experiment should check, include or modify the scripts of this
repository [1]. This scripts will remain inside a packet named
wibed-battlemesh-experiment which will be installed in the base firmware
(wibed-openwrt) or any other base firmware which may be used.

My two cents.

[1]
https://github.com/battlemesh/wibed-battlemesh-experiment/tree/master/packages/wibed-battlemesh-experiment/files/etc/wbm/protos

On 28/07/15 21:03, Mitar wrote:
> Hi!
> 
> Could we assure this things work before the event? Not that we spend
> debugging the issues during?
> 
> So could you compile images for all the devices we are having at the
> event so that people can try them in advance?
> 
> Also, which documents are there now for what would be the topology of
> the testbed? What I worry is that we should not be generating the
> traffic with same nodes we are doing routing with. So is this separated?
> Some nodes are doing only routing, other have a independent WiFi channel
> to communicate control plane over, and then we have dedicated edge
> machines which generate test traffic.
> 
> Again, sorry if this is all already taken care of. I am just a bit
> worried we will again spend 5 days of the conference just to get things
> running.
> 
> 
> Mitar
> 
>> Hi Dave,
>>
>> WiBed currently supports mostly netgear wndr4300.
>> In the last battlemesh there have been effort to compile for different
>> devices, facing mostly image size issues. It would be nice if you could
>> assist us during the event in compiling wibed images for other devices.
>>
>> Cheers,
>> Manos
>>
>> On 07/28/2015 03:04 PM, Dave Taht wrote:
>>> I am bringing 2 nanostation M5s, 2 picostations, 1 netgear wndr4300,
>>> toke's linksys 1200ac. We may end up with more nanostations.
>>> I also have an edgerouter or two.
>>>
>>> What I typically do is arrange the m5 + pico as a "pod" that can fail
>>> over either way to an ethernet connected device (like a laptop).
>>>
>>> At the moment these have a custom build with minstrel-blues and the
>>> minstrel-minimum variance patches and run babel only.
>>>
>>>
>>> On Tue, Jul 28, 2015 at 2:49 PM, Simon Wunderlich
>>> <sw at simonwunderlich.de> wrote:
>>>> On Tuesday 28 July 2015 05:44:01 Mitar wrote:
>>>>> Hi!
>>>>>
>>>>> What is the status of the testbed preparations? Who is working on it?
>>>>> Amadeus, you are coordinating things? Do you need any help? Manos, how
>>>>> is the firmware status?
>>>>>
>>>>> For easier planing, here is the map of the venue:
>>>>>
>>>>> https://www.dropbox.com/s/ddhbfs5sklc0tmi/MapPekre.pdf?dl=0
>>>>>
>>>>> X are where power sockets are.
>>>>>
>>>>> Here is the list of hardware we have:
>>>>>
>>>>> http://battlemesh.org/BattleMeshV8#Hardware
>>>>>
>>>>> Will there be any other hardware? Please update the wiki, if you are
>>>>> bringing anything, so that firmware team can know what to expect.
>>>>
>>>> We have another section and several people will bring WDR4300 to the
>>>> event:
>>>>
>>>> http://battlemesh.org/BattleMeshV8#List_of_the_Hardware_Available
>>>>
>>>> maybe we should merge it with the other section? Hardware in that
>>>> section is
>>>> just lent, not "sponsored", though, and people will take them back
>>>> after the
>>>> event. :)
>>>>
>>>> Cheers,
>>>>      Simon
>>>> _______________________________________________
>>>> Battlemesh mailing list
>>>> Battlemesh at ml.ninux.org
>>>> http://ml.ninux.org/mailman/listinfo/battlemesh
>>>>
>>>
>>>
>>>
>> _______________________________________________
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/battlemesh
> 

-- 
./p4u

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20150728/bfec4b94/attachment-0001.sig>