Tmplab - User contributions [en]

Liens vers divers projet que nous pourrions inviter lors d'une conf :

2011-01-29T22:07:24Z

Nico:

* Aurora liquid air: http://www.cooling-masters.com/articles-34-0.html
* DIY SAR radar: http://www.mit.edu/~gr20603/Dr.%20Gregory%20L.%20Charvat%20Projects/$240%20High%20Res%20Rail%20SAR.html
* Jeri Ellsworth (home transistor fab etc.)
* High voltage rock disaggregator: http://www.lucidscience.com/gal-rock%20disaggregator-1.aspx
* Lithography:
http://www.physics.rutgers.edu/ugrad/387/388s06/film_deposition/Musgraves05.pdf
* Thin film machine:
http://www.getupanddiy.com/projects/thin-film-sputtering-machine/index.php
* NSA@home: http://nsa.unaligned.org/
* AEMB (CPU softcore): http://www.aeste.net
* AMSAT: http://www.amsat.org
* S53MV: http://lea.hamradio.si/~s53mv (le GPS est particulièrement impressionnant)
* Tubes à vide: http://paillard.claude.free.fr/
* PWL: http://tubedevices.com/alek/pwl/pwl_e.htm
* Spark Bang Buzz: http://home.earthlink.net/~lenyr/
* Powerlabs: http://www.powerlabs.org
* Degate: http://www.degate.org/
* Ulogic: http://www.ulogic.org
* Flylogic: http://www.flylogic.net
* Teralab: http://www.teralab.org
* STM: http://sxm4.uni-muenster.de/stm-en/
* Stellarator: http://linux06.dnspropio.com/~fusionvic/
* Ed Nisley: http://softsolder.files.wordpress.com/2009/01/diy-diodes-nisley.pdf
* OpenBTS, GNURadio (quoi qu'on les voit déjà assez souvent)

WebOS: développement et hacking

2010-06-15T19:54:43Z

Nico: /* Inscrits */

Le jeudi 17 juin 2010 au /tmp/lab ; à partir de 20H00

== Plan de l'atelier ==
* Présentation de l'architecture de WebOS (qui repose sur Linux),
* Présentation du développement WebOS:
** Le SDK et son contenu
** L'émulateur (à base de VirtualBox)
** L'IDE Web Ares
* Hacking du système
** Modifier une application installée
** Patcher quelques paramètres systèmes
** Modifier une image de l'OS

=== Mise en pratique ===
* Chaque participant pourra s'il le désire, mettre en pratique ce qui aura été présenté en développant une application simple.

== Connaissances nécessaires ==
* Notion de HTML et JavaScript
* Connaissance de base de la ligne de commande Linux (cd, ls, vi, ...)

== Inscrits ==
* Animateur : Lionel

Merci d'inscrire votre pseudo ci-dessous afin d'avoir une estimation du nombre de participants.
* Phil
* Taekysa
* Nico
* <Pseudo ici>

<br>
<br>

== Pré-requis recommandé ==
* Pour la mise en pratique:
** PC sous Windows/Linux ou MacOS
** Avoir installé le SDK depuis cette [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788 URL]
** Disposer d'un Palm Pré ou d'un Palm Pixi est un plus mais ce n'est pas indispensable (l'émulateur suffit)
* Lecture possible avant le workshop: [http://7avoir.over-blog.com/article-un-systeme-d-exploitation-web-web-os-45589955.html ici] et [https://developer.palm.com/index.php?option=com_content&view=article&id=1761&Itemid=42 ici]

== Matériel requis ==
* Vidéoprojecteur

[[Category:Workshop]]
__NOTOC__

VoIP hacking workshop

2010-05-18T15:16:13Z

Nico:

{{Workshop
|title=VoIP hacking workshop
|when=Thursday 20th of May 2010, 8PM (20h00)
|where=/tmp/lab
|intro=Easy way to pentest VoIP infrastructure.

Overview:

* Identification of the VoIP Product
* VLAN hopping, accessing the voice VLAN from the data VLAN
* VoIP accounts enumeration
* Communication wiretapping and injection of sound during a call
* Spoofing of phone profiles and identity spoofing
* UNISTM attack on Cisco IP phones
* Bypass of call restrictions and voice gateway abuse
* Grab of SIP or IAX credentials
* Denial of Service on VoIP servers and IP phones

Prerequisites:

* Python >= 2.5
* An editor > vi
* Scapy
* Wireshark (optional)

Participants:
* Sn0rky
* Phil
* Jo
* Kugg
* Err404
* Jm
* Tealck
* Nico

|by=[[User:Sn0rkY|Sn0rkY]]
}}

Réseau : de la conception d'une architecture IPv4 locale à son déploiement

2010-01-13T16:24:08Z

Nico:

Apparemment une vieille idée, que {Nico}, tAd et deadr0m1 reprennent petit à petit :) ''Pour intégration comme nouveau réseau du /tmp/lab ?''

L'idée est de proposer un workshop pragmatique mettant tout particulièrement en avant les travaux pratiques.

Nous pensions découper le groupe de participants en petits groupes de travail en harmonisant les niveaux. Chaque groupe
de travail pourra alors participer à la conception, en débattant les idées et concepts.

L'idée de fond serait le déploiement d'une architecture un peu travaillée :

* Plusieurs sous-réseaux dont le découpage et la configuration feraient l'objet d'une réflexion préliminaire.
** Ce découpage devra être idéalement évolutif : souplesse dans l'allocation des sous-réseaux, avec croissance possible.

* Des VLANS, pour assurer la séparation physique des différents sous-réseaux en fonction de leur rôle/criticité

Au niveau du matériel : Cisco Catalyst 2924-XL (?) - De quoi jouer avec les vlans et un peu de sécurité.

''To be continued''

'''--- Vrac, 1er jet, "1er niveau" ---'''

'''.:: Notions de bases réseau ::.'''

'''Topo:'''

*différents niveaux de connaissance, bases nécessaires pour le premier workshop: null

*basé sur ateliers pratiques.

*chacun sa machine/matériel à configurer.

*but: pondre un document le plus précis/complet possible.

Accompagner chaque config/concept de commandes de base (Windows, UN*X), i.e.:

Windows UN*X Desc.
*ipconfig (/all) ifconfig Connaitre la configuration réseau
*ping ping possibilité de connexion?
*tracert traceroute par où je passe (latence)

----

'''.: Premier niveau - LAN d'un particulier:.'''

'' '''Idée:'''Une personne vient de recevoir sa *Box de connexion au réseau Internet. "C'est quoi ça? pourquoi ça?"''

*Physique:
**Box (ETH, wifi, USB?)
**poste client (ETH, wifi, USB?)
**cables (ETH, USB)
**switch/hub (ETH)
**Medias: cuivre, air, fibre optique (OSI Niveau 1)

--> Penser l'architecture du réseau local, que choisir (cuivre, wifi, USB?): (PC -> Box (cuivre|wifi)) ou (multiPC -> SW -> Box (cuivre))

--

*Conf réseau:
**Adresse IP: où suis-je? (//adresse postale)
**DHCP: obtention d'un adresse IP automatiquement délivrée par la Box.
**passerelle/GW: Interconnexion d'un réseau à un autre.
**Masque réseau: taille du réseau, qui communique avec qui.
**DNS: correlation URL/@IP
**Firewall: Notion de filtrage de flux, pourquoi, comment ça se configure (@IP SRC/DST, Port)

==> (cible) consulter une page web sur Internet.

--

Modèle OSI simplifié (sans insister) mais présenter les différentes couches interessantes (Physique(Cables, Switch/Hub), IP, TCP/UDP).

Qu'est-ce qu'un protocole? (TCP, IP, UDP, ICMP)
*Notions de base à propos :
**Adresse IP
**port
**le TCP de TCP/IP
**UDP (flux live)
**ICMP (ping, pourquoi?)
**Adresse MAC (interface physique)

--

*OSI Simplifié:
.-------------.
| Application | Navigateur, client mail, ...
.-------------.
| Transport | TCP, UDP, ...
.-------------.
| Réseau | @IP
.-------------.
| Liaison | @MAC (eth)
.-------------.
| Physique | Cuivre, air, fibre optique

Workshops

2010-01-13T12:00:48Z

Nico:

Here are the Workshops happening @ /tmp/lab

== Workshops Schedule ==
* Nothing planned yet

== Upcoming Workshops ==
* [[Réseau : de la conception d'une architecture IPv4 locale à son déploiement]] (contacter {Nico}, tAd ou deadr0m1)
* Programmation comparée (contacter {Nico})
* OpenWrt (contacter {Nico})

== Wanted Workshops ==
So, you want to give or take a workshop, but it's not scheduled yet? Open a page for it :)

* [[RF Jammer advanced]]
* [[Workshop Serial Level Shifter & Router Debrick]]
* [[Awesome Window Manager]]
* [[Ruby for beginners]]
* [[Ruby On Rails]]
* [[Linux Virtualization]] (KVM, Linux-Vserver, OpenVZ)
* [[Vacuum tubes]]
* [[puredata]]
* [[Python : Taste the code]]
* [[Blender : An Open 3D Content Creation Suite]]
* [[DIY AUDIO 3 : easy and efficient mic building]]
* [[OCaml made Obvious]]
* [[BootstrapPIC]]
* PC Rehab
* Church of Security
* DoS, DDoS & Co.
* /tmp/van brico
* Biodiesel
* [[SuperCollider Part II]]
* GIT
* SCTPscan QA & release hacknight
* EGPL release
* CFP-submit workshop
* Secure Server Building from Scratch
* Introduction à l'Electronique
* GPG, TOR and OTR for Privacy on the Internet
* Using your phone for weird goals
* DNS fun
* Histoire, fonctionnement et comment s'amuser avec internet.

== Past Workshops ==
* 21/12/2009 - OpenWrt/Milkymist coding party
* 19/02/2009 - [[Python for beginners]]
* 26/02/2009 - [[DIY audio]]
* 12/03/2009 - [[La soudure pour les nuls]]
* 20/03/2009 - [[DIY audio 2]] la suite!
* 21/03/2009 - [[Workshop Introduction aux FPGA]]
* 23/03/2009 - [[Church of Security at SIANA INT]]
* 26/03/2009 - [[Présentation Livecoding]]
* 28/03/2009 - [[FPGA: la suite]]
* 02/04/2009 - [[SuperCollider Part I]]
* 04/04/2009 - [[Workshop OpenWrt]]
* 14/05/2009 - [[Workshop hacking et grand public]]
* 09/07/2009 - [[Workshop post-HSF Open Source Video Editing]]
* 25-26/07/2009 - [[Atelier-Tour de table RepRap et Usinettes, buts du nouveau "FabLab"]]
* 29/08/2009 - [[FPGA Workshop #3: Computer Architecture]]
* ??/09/2009 - [[Défouraille ta Fonera]]
* 10/09/2009 - [[Distributed Crypto SAT Solving]]
* 07/11/2009 - [[Développement logiciel embarqué sur Milkymist]]
* 08/11/2009 - [[FPGA Workshop 4: Behind the Scenes]]
* 26/11/2009 - [[FPGA : une introduction (bis)]] à La Suite Logique

== Adding a Workshop ==
Anybody can create a workshop, this is auto-organization.

# Create a new page on the wiki prefixed with your workshop's keyword, such as "MediaWiki : Why It Doesn't Suck That Much"
## Use the [[Template:Workshop]] :)
## Make sure you add an Attendees section before saving, so that nobody will edit the template itself!
# Add your workshop link on this page with its date
# Add a link in /tmp/lab shared calendar on G00gle Gr0ups
# Announce it on the /tmp/lab mailing list
# Announce it on the #frlab IRC channel and optionnally add it to the topic if it's the next workshop.
# If your workshop involve handling of chemical products, check [http://www.inchem.org/ IPCS (International Programme on Chemical Safety)] for proper handling/disposal instructions

26C3

2009-11-15T23:14:28Z

Nico: /* Participants */

Pour faire simple, faisons un seul convoi au départ de Paris pour le /tmp/lab, la Suite Logique, et tout les copains.

== Outline ==

On va essayer d'organiser un covoiturage pour aller à Berlin, mais si vous choisissez une autre solution, libre à vous. On devrait avoir des contacts pour atterrir dans un squat berlinois, mais il faut savoir combien on sera. Enfin, tant qu'à etre a Berlin a la fin décembre, autant y passer le nouvel an !

'''Inscrivez vous avant le 19 novembre pour etre sur d'avoir une place dans le squat'''

== Participants ==

{|border="1"
! Nom !! Squat !! Permis de conduire !! Voiture !! Départ !! Nouvel An !! Matos
|-
| dermiste || Oui || Non || Non || possible le 25 aprem || Oui ! || Switch 100Mb 16 ports
|-
| guyzmo || Oui || Oui || A condition que CT et Revisions soient faites (donc a envisager en cas de besoin)
|| à confirmer le 25 aprem, sûr à partir du 26 || Of course ! || La patate, à Boire, à manger, coussins, ce qu'on aura préparé pour l'event et ce que LSL pourra apporter (grappes de cables, NAS...)
|-
| Deubeuliou || Oui || En cours || Non || possible de 25 aprem || Oui !!! || sheevaplug
|-
| Phil || Oui || Oui || ? || ? || ? || brainfuck programming manual
|-
| Hellekin || Oui || Oui || Non || ? || Oui || !! Départ de Munich !!
|-
| Beretta_V || Oui || Oui || Oui || possible le 26 || Oui ||
|-
| Urs || Oui || Oui || ....selon son humeur... || || Oui ||
|-
| lekernel || Oui || Oui || Hell yes! (Deuscheiße Bahn+MessyJet = never again) || 25 décembre (départ de Laon-1h30 en train de Paris) arrivée le 26 || Oui!! || [http://www.milkymist.org Milkymist] board + écran
|-
| Nina || Oui || Non || Non || 25 décembre, arrivée le 26 || Oui || -
|-
| marina || oui || non || non || le 26 || oui ||
|-
| Nico || non || oui || non || le 25 au soir ou le 26 || oui ||absynthe & routeurs WiFi
|}

== Transport Covoiturage ==

Paris - Berlin = 1100 km, 10-12h de route.
1 vehicule = 260€ AR max, a partager en 4 => 65€/personne

volontaires:
# dermiste
# guyzmo
# lekernel (départ de Laon, sur 2 jours, étapes Bochum à l'aller et Francfort au retour)
# deubeuliou

=== autres transports ===

Train : minimum 160€/personne. ATTENTION: réserver l'aller et le retour en France et se tenir aux dates. Si vous prenez les billets en Allemagne ou essayez de changer de date: billet pouvant monter à 408€ (aller simple) et très grosses difficultés de réservation. Si l'un et/ou l'autre de ces problèmes se produit, montez dans le train sans billet: si le controleur ne vous fout pas dehors à la prochaine gare, vous paierez au final moins cher (tarif bord = 125€ aller simple).

Minibus loué : rajoute 100€/personne

Avion : minimum 120€/personne, capacité limitée, réchauffement climatique, traité comme du bétail, dispositif sécuritaire ...

Berlin Linien Bus: 129€ aller-retour pour les courageux prêt a faire 12H de bus ...

== Logement ==

Dépend du nombre de personnes qui ont confirmé.
Plus d'infos a partir du 19/11.
Annoncé : 15 personnes dans les squats.
Si on est vraiment 15, il se peut qu'on soit séparés dans deux lieux.

== Matos ==

Il faut surtout ramener de quoi poser son cul, ya pas beaucoup de canapés ... matelas ou boudin gonflable, ou une autre connerie de ce genre ?

Ramener aussi des nourrices, des switches et des cables.

HowToUseTheTracer

2009-11-13T02:04:59Z

Nico: New page: = How to use the (fscking) tracer = The tracer is an HP DesignJet 750C Plus with an embedded JetDirect (J4100A) network interface module. == Network Settings == IP: 10.0.0.8 Name: trace...

= How to use the (fscking) tracer =

The tracer is an HP DesignJet 750C Plus with an embedded JetDirect (J4100A) network interface module.

== Network Settings ==

IP: 10.0.0.8
Name: tracer

== On Windows ==

1. Install the HP port monitor
ftp://ftp.hp.com/pub/softlib/software10/COL25578/jd-65723-1/HPTcpMon.zip

2. Install the HP printer driver
ftp://ftp.hp.com/pub/softlib/software3/COL3190/pl-10683-3/pl532en.exe

3. Run the "Add printer..." wizard

4. Choose to add a local printer, make sure that "Autocrappy discovery of Plug-and-Pray printers" is not selected

5. Create a new printing port using "HP Standard TCP/IP port", use "tracer" or "10.0.0.8" for the printer name and whatever you find relevant for the port name

6. On the driver list, click "Have disk..." and select the directory where you install the HP printer driver, then select "HP" in the manufacturer list and "HP DesignJet 750C+ (D/A1) by HP" in the printer list

7. You're done

Main Page

2009-11-13T01:49:16Z

Nico: /* Documentation */

This is the Wiki from [http://www.tmplab.org/ /tmp/lab]. You can freely edit this, you just need to register and validate your account with your email address to prevent spam. Thanks!

<div style="float:left; width:48%;"> 
= Intro =
* [http://www.tmplab.org/about/ About /tmp/lab & FAQ]
* [http://www.tmplab.org/contact/ Coming to /tmp/lab & contact information]
* [http://www.tmplab.org/ Blog & news]
* /tmp/lab is located near a [http://ec.europa.eu/environment/seveso/index.htm Seveso] classified pharmaceutical plant ([http://www.portalanglais.com/spip.php?article132 lire l'article en français])
* [[A little history of /tmp/lab]] (en) ([http://www.tmplab.org/wiki/index.php/A_little_history_of_/tmp/lab#Fran.C3.A7ais Un petit historique du /tmp/lab])
* [[Press]]
* [[Administratif]]
* [http://www.tmplab.org/2009/07/31/stages-au-tmplab-internships/ Stages / Internships]

= Living =
* [http://www.tmplab.org/wiki/index.php//tmp/lab_How_To How To]
* [[Borrowed things]]
* [[KineKlub]]
* [[Conferences]]
* [[Workshops]]
* [[D&Co]]

= Events =
* [[Wireless Battle Mesh]]
* [[HackerSpaceEuroTour|HackerSpace Euro Tour, May 2009]] see [[HackerSpaceEuroTours]]
* [[HackerSpaceEuroTour2|HackerSpace Euro Tour 2, June 2009]] see [[HackerSpaceEuroTours]]
* [[HackerSpaceEurasianTour|HackerSpace Eurasian Tour]]
* [http://www.hackerspace.net/ Hacker Space Fest 2009]
* /tmp/lab hors les murs au Palais de Tokyo (4, 11 et 18 Juin 2009)
* [[Hackers at CERN]] (Février/Mars 2010)
* [[26C3]]

</div>

<div style="float:right; width:48%;"> 

= Projects =
* [[OLPC France]]
** [[OLPC Emulation]]
** [[Backtrack3 on EEE]]
** [[OLPC Live]]
** [[Sugar Xubuntu on EEE]]
** [[FlashEEE]]
* [[Hacker Space Fest]]
** [[HSF Organization]]
** [[HSF Task List]]
** [[HSF Spaces]]
* BioEco
** [[Toxic Gas Sensor]]
** [[/tmp/flower]]
* [[/tmp/van]]
* [[Chip Reverse Engineering]]
* [[FreeTvPerso video relay]]
* [[Domoverse platform]]
* [http://dev.tmplab.org/wiki/tmp-usine /tmp/usine: RepRap @ /tmp/lab]
** [[Dream Devices]]
* [[Freedom Not Fear]]
* [[esonoclaste upgrade]]
* [[/tmp/net dn42]]
* '''/tmp/demoscene'''
** [[DemoParty Compo with MilkyMist]]

= Documentation =

* [[MediaWikiLinks]]
* [[Information Design]]
* [[GIT Cheat Sheet]]
* [[BackTrack]]
* [[RFID]]
* [[Pure Data]]
* [[Mobile Phone Chargers]]
* [[Ruby on Rails]]
* [[Python]]
* [[Business Methods]]
* [[HowToUseTheTracer]]
</div>

Main Page

2009-11-13T01:48:32Z

Nico: /* Documentation */

Things and borrowed things

2009-10-22T21:21:27Z

Nico:

Rule of the Library :
'''Ask all the borrowers by email to return the stuff before borrowing something yourself ;-)'''

* <strike>Tournevis - Antonin/Daniel</strike>
* <strike>Book [http://www.amazon.fr/Gu%C3%A9rilla-kit-techniques-nouvelles-anticapitalistes/dp/2707154059/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1203087206&sr=8-1 "Guérilla kit" ] - Lyle</strike>
* Book - "Hacking - the art of exploitation" - massoud
* <strike>Book - "Du mode d'existence des objets techniques" - HK</strike>
* <strike>Book - "AI Application Programming, by M. Tim Jones" - AlbanC</strike>
* Book - "Python Cookbook, O'Reilly" - Alex K
* CD - Windows XP SP2 - Christian 6Bis
* Book - "guide to open content licenses v1.2" - Spamforfree Thiago
* Clavier Mac - Far
* Multimetre - Massoud
* book : Pierre Tilman, Filiou, nationalité poète, les presses du réel_ Ursula
* book : Core... _Ursula
* book : Art Critical Ensemble, éditions de l'éclat _Ursula
* book : "L'homme et ses trois éthiques" - Stéphane Lupasco + "Sociologie des réseaux sociaux" Pierre Mercklé - Karim
* book : Programming Ruby - The Pragmatic Programmers' Guide, de Dave Thomas avec Chad Fowler et Andy Hunt - Matthieu mbrANTieISPnd_at_gmaAMil.com
* book : Agile Web Development with Rails, de Dave Thomas et David Heinemeier Hansson - Matthieu mbrANTieISPnd_at_gmaAMil.com
* Kiniou's USB Keyboard - Fred photographe du 6bis
* <strike>book : Introduction a la guerre civile, Tiqqun - Nico nicolas <__AT__> littlecleaver <DOT> com</strike>
* book : Retour au meilleur des mondes - Ursula
* book : Storytelling - Padawan
* book : Quand les banlieues brûlent - Padawan
* book : Du mode d'existence des objets techniques - Padawan
* book : La France A Peur, une histoire sociale de l'"Insécurité" - Padawan

Press

2009-08-20T18:31:26Z

Nico: /* 2009 */

= /tmp/lab in the news =

== 2009 ==

=== Published ===
* 2009-08-19 http://www.liberation.fr/culture/0101586015-les-hackers-generation-debrouille
* 2009-08-10 http://tempsreel.nouvelobs.com/actualites/vu_sur_le_web/20090727.OBS5575/hackers_pirates_cyberpunks__la_resistance_du_web.html
* 2009-07-21 http://www.arte.tv/fr/Comprendre-le-monde/ARTE-info/2768232.html (MPEG: http://www.tmplab.org/arte-info-20090721-excerpt-hadopi.mpg )
* 2009-07-10 http://www.sicw-news.com/2009/07/le-routeur-hadopi-nest-plus-une-blague.html
* 2009-07-10 http://torrentfreak.com/hackers-undermine-piracy-evidence-with-hadopi-router-090709/
* 2009-07-10 http://www.numerama.com/magazine/13427-HostileWRT-le-vrai-nom-du-vrai-faux-34routeur-Hadopi34.html (correction et explication face au bullshit de Le Monde)
* 2009-07-10 http://www.numerama.com/magazine/13422-Le-vrai-routeur-Hadopi-prouve-la-dangerosite-de-la-loi-Hadopi.html (reprise du bullshit de Le Monde)
* 2009-07-09 http://sites.radiofrance.fr/chaines/france-culture/emissions/sur_docks/fiche.php?diffusion_id=74876 (mp3: http://media.radiofrance-podcast.net/podcast09/10177-09.07.2009-ITEMA_20187750-0.mp3 )
* 2009-07-08 http://www.lemonde.fr/archives/article/2009/07/08/les-nouvelles-tribus-du-net_1216676_0_1.html (bullshit and wrong information...)
* 2009-07-05 http://www.rue89.com/2009/07/05/au-hacker-space-festival-une-autre-securite-informatique-est-possible HSF
* 2009-07-05 http://www.poptronics.fr/A-Vitry-un-festival-hacker-ouvert HSF
* 2009-07-03 http://numuscus.pascsaq.org/?p=59 http://numuscus.pascsaq.org/?p=107 HSF
* 2009-07-03 http://www.telerama.fr/techno/l-affaire-est-dans-le-hack,44851.php HSF
* 2009-07-02 http://www.cnis-mag.com/hsf-2009-4-jours-de-hacking-echeveles-et-chevelus.html HSF
* 2009-06-29 http://blog.cultureordinaire.net/post/2009/06/28/Hacker-Space-Festival HSF
* 2009-06-26 http://fr.readwriteweb.com/2009/06/26/divers/hacking-institutions-une-interview-de-philippe-langlois-du-tmplab/
* 2009-06-11 http://www.lesnumeriques.com/news_id-9214.html HSF
* 2009-06-09 http://it.slashdot.org/story/09/06/09/0117220/Paris-Hosts-the-Second-Hacker-Space-Festival HSF
* 2009-05-28 http://www.cnis-mag.com/fr/accueil.html HSF
* 2009-05-28 http://www.cnis-mag.com/fr/hacker-space-festival-2-juin-sera-binaire-et-forensic-a-vitry/evenements1.html HSF
* 2009-04-30 http://www.lemonde.fr/technologies/article/2009/04/30/nous-sommes-tous-des-hackers_1187555_651865.html
* 2009-05-07 Envoyé Spécial, France 2. http://tmplab.org/Envoye-Special-Cybercriminalite.mpg
* 2009-04-20 http://television.telerama.fr/television/envoye-special,41933.php
* 2009-01-27 http://www.ecrans.fr/Dorkbot-s-auto-replique-ce-soir-a,6225.html

== 2008 ==
* http://gadgets.boingboing.net/2008/12/18/mitch-altman-travels-3.html
* http://www.monde-diplomatique.fr/2008/09/MANACH/16295
* http://www.monde-diplomatique.fr/2008/09/MANACH/16226
* http://blog.wired.com/sterling/2008/03/hacker-space-fe.html

= Communiqué de presse =

== Publiés ==
Aucun.

== Projet de communiqué ==
* [[Le Monde manipule t'il l'opinion publique contre les hackers]]

Press

2009-08-20T18:31:06Z

Nico: /* 2009 */

= /tmp/lab in the news =

== 2009 ==

=== Upcoming ===
* Nouvel Obs? Le 9 aout m'a t'elle dit [Phil]

=== Published ===
* 2009-08-19 http://www.liberation.fr/culture/0101586015-les-hackers-generation-debrouille
* 2009-08-10 http://tempsreel.nouvelobs.com/actualites/vu_sur_le_web/20090727.OBS5575/hackers_pirates_cyberpunks__la_resistance_du_web.html
* 2009-07-21 http://www.arte.tv/fr/Comprendre-le-monde/ARTE-info/2768232.html (MPEG: http://www.tmplab.org/arte-info-20090721-excerpt-hadopi.mpg )
* 2009-07-10 http://www.sicw-news.com/2009/07/le-routeur-hadopi-nest-plus-une-blague.html
* 2009-07-10 http://torrentfreak.com/hackers-undermine-piracy-evidence-with-hadopi-router-090709/
* 2009-07-10 http://www.numerama.com/magazine/13427-HostileWRT-le-vrai-nom-du-vrai-faux-34routeur-Hadopi34.html (correction et explication face au bullshit de Le Monde)
* 2009-07-10 http://www.numerama.com/magazine/13422-Le-vrai-routeur-Hadopi-prouve-la-dangerosite-de-la-loi-Hadopi.html (reprise du bullshit de Le Monde)
* 2009-07-09 http://sites.radiofrance.fr/chaines/france-culture/emissions/sur_docks/fiche.php?diffusion_id=74876 (mp3: http://media.radiofrance-podcast.net/podcast09/10177-09.07.2009-ITEMA_20187750-0.mp3 )
* 2009-07-08 http://www.lemonde.fr/archives/article/2009/07/08/les-nouvelles-tribus-du-net_1216676_0_1.html (bullshit and wrong information...)
* 2009-07-05 http://www.rue89.com/2009/07/05/au-hacker-space-festival-une-autre-securite-informatique-est-possible HSF
* 2009-07-05 http://www.poptronics.fr/A-Vitry-un-festival-hacker-ouvert HSF
* 2009-07-03 http://numuscus.pascsaq.org/?p=59 http://numuscus.pascsaq.org/?p=107 HSF
* 2009-07-03 http://www.telerama.fr/techno/l-affaire-est-dans-le-hack,44851.php HSF
* 2009-07-02 http://www.cnis-mag.com/hsf-2009-4-jours-de-hacking-echeveles-et-chevelus.html HSF
* 2009-06-29 http://blog.cultureordinaire.net/post/2009/06/28/Hacker-Space-Festival HSF
* 2009-06-26 http://fr.readwriteweb.com/2009/06/26/divers/hacking-institutions-une-interview-de-philippe-langlois-du-tmplab/
* 2009-06-11 http://www.lesnumeriques.com/news_id-9214.html HSF
* 2009-06-09 http://it.slashdot.org/story/09/06/09/0117220/Paris-Hosts-the-Second-Hacker-Space-Festival HSF
* 2009-05-28 http://www.cnis-mag.com/fr/accueil.html HSF
* 2009-05-28 http://www.cnis-mag.com/fr/hacker-space-festival-2-juin-sera-binaire-et-forensic-a-vitry/evenements1.html HSF
* 2009-04-30 http://www.lemonde.fr/technologies/article/2009/04/30/nous-sommes-tous-des-hackers_1187555_651865.html
* 2009-05-07 Envoyé Spécial, France 2. http://tmplab.org/Envoye-Special-Cybercriminalite.mpg
* 2009-04-20 http://television.telerama.fr/television/envoye-special,41933.php
* 2009-01-27 http://www.ecrans.fr/Dorkbot-s-auto-replique-ce-soir-a,6225.html

== 2008 ==
* http://gadgets.boingboing.net/2008/12/18/mitch-altman-travels-3.html
* http://www.monde-diplomatique.fr/2008/09/MANACH/16295
* http://www.monde-diplomatique.fr/2008/09/MANACH/16226
* http://blog.wired.com/sterling/2008/03/hacker-space-fe.html

= Communiqué de presse =

== Publiés ==
Aucun.

== Projet de communiqué ==
* [[Le Monde manipule t'il l'opinion publique contre les hackers]]

Toxic Gas Sensor

2009-07-23T18:49:28Z

Nico: /* Proposal */

Artificial nose? Helping industry trace their leaks? MRTG for toxic gas?

Welcome to the wonderful world of post-chemistry.

= Sniffing =
* Carbon Monoxide (CO), Hydrogen (H)
* Hydrogen (H), Ethanol (C2H6O), Iso-butane (CH3CH(CH3)2), Carbon Monoxide (CO), Methane (CH4)
* Toluene (C7H8), Hydrogen Sulfide (H2S), Ethanol (C2H6O), Ammonia (NH3), Hydrogen (H)
* Ethanol (C2H6O), Hydrogen (H), Iso-butane (CH3CH(CH3)2), Carbon Monoxide (CO), Methane (CH4)

= Using =
* Electronic components sensing various gaseous substances : http://www.selectronic.fr/soussousfamille.asp?fam_ref=05&sfam_ref=98&ssfam_ref=32
* http://www.nexsens.com/support/user_manuals.htm
* http://www.freeduino.org/
* http://www.rosiedaniel.com/2007/04/gas-sensors.html
* http://itp.nyu.edu/physcomp/sensors/Reports/GasSensors

= Proposal =
* Sensors: cheap sensors made by a company called Figaro - one TGS2600 + one TGS2602. Available at Radiospares and Diltronic (St Germain en Laye)
* Those sensors are already used by http://fridav.ljudmila.org (that's how we found them)
* Based on a Fonera which could connect to the /tmp/lab wireless network and directly post results on the internet
* Using SPI with Fonera: http://www.larsen-b.com/Article/262.html
* ADC: LTC2496 (lekernel: I have an evaluation kit)
* My LTC2496 driver for Linux (lekernel)

= Resources =

http://www.airparif.asso.fr/pages/polluants/surveillance
http://w2.airparif.asso.fr/cgi-bin/station_files.pl?station=VITRY

Press

2009-07-08T15:17:26Z

Nico: /* Published */

= /tmp/lab in the news =

== 2009 ==

=== Upcoming ===
* Nouvel Obs? Le 9 aout m'a t'elle dit [Phil]

=== Published ===
* 2009-07-08 http://www.lemonde.fr/archives/article/2009/07/08/les-nouvelles-tribus-du-net_1216676_0_1.html
* 2009-07-05 http://www.rue89.com/2009/07/05/au-hacker-space-festival-une-autre-securite-informatique-est-possible HSF
* 2009-07-05 http://www.poptronics.fr/A-Vitry-un-festival-hacker-ouvert HSF
* 2009-07-03 http://numuscus.pascsaq.org/?p=59 http://numuscus.pascsaq.org/?p=107 HSF
* 2009-07-03 http://www.telerama.fr/techno/l-affaire-est-dans-le-hack,44851.php HSF
* 2009-07-02 http://www.cnis-mag.com/hsf-2009-4-jours-de-hacking-echeveles-et-chevelus.html HSF
* 2009-06-29 http://blog.cultureordinaire.net/post/2009/06/28/Hacker-Space-Festival HSF
* 2009-06-26 http://fr.readwriteweb.com/2009/06/26/divers/hacking-institutions-une-interview-de-philippe-langlois-du-tmplab/
* 2009-06-09 http://it.slashdot.org/story/09/06/09/0117220/Paris-Hosts-the-Second-Hacker-Space-Festival
* 2009-05-28 http://www.cnis-mag.com/fr/accueil.html
* 2009-05-28 http://www.cnis-mag.com/fr/hacker-space-festival-2-juin-sera-binaire-et-forensic-a-vitry/evenements1.html
* 2009-04-30 http://www.lemonde.fr/technologies/article/2009/04/30/nous-sommes-tous-des-hackers_1187555_651865.html
* 2009-05-07 Envoyé Spécial, France 2. http://tmplab.org/Envoye-Special-Cybercriminalite.mpg
* 2009-04-20 http://television.telerama.fr/television/envoye-special,41933.php
* 2009-01-27 http://www.ecrans.fr/Dorkbot-s-auto-replique-ce-soir-a,6225.html

== 2008 ==
* http://gadgets.boingboing.net/2008/12/18/mitch-altman-travels-3.html
* http://www.monde-diplomatique.fr/2008/09/MANACH/16295
* http://www.monde-diplomatique.fr/2008/09/MANACH/16226
* http://blog.wired.com/sterling/2008/03/hacker-space-fe.html

KineKlubEdition3

2009-05-26T21:36:18Z

Nico: New page: __NOTOC__ <div style="float:left; width:48%;"> = Français = Quand : le 12/06/2009 Où : ? </div> <div style="float:right; width:48%;"> = English = When: le 12/06/2009 Where: ? </div...

__NOTOC__
<div style="float:left; width:48%;">

= Français =

Quand : le 12/06/2009
Où : ?

</div>
<div style="float:right; width:48%;">

= English =

When: le 12/06/2009
Where: ?

</div>

KineKlub

2009-05-26T18:19:21Z

Nico:

__NOTOC__
<div style="float:left; width:48%;"> 

= Français =

==KinéKlub ==

Le KinéKlub est entièrement dédié aux Hackers au sens très large du terme comprenant toutes les tendances du genre : hackers affirmés, refoulés, compulsifs, taciturnes ou loquaces, circonspects ou passionnés, hésitants, arrogants, torturés, enthousiastes, pour ne parler que des aptitudes les plus répandues. C'est donc dans ce contexte de Hacking « augmenté » que le KinéKlub a choisi de se développer et de s'épanouir. Il s'est façonné son berceau dans un laboratoire au coeur d'une zone industrielle, et par chance au coeur d'un des plus beaux paysages d'île de France où sont massivement produits nos médicaments, et dont il émane perpétuellement des parfums surprenants d'une teneur mystérieuse et changeante, mais incontestablement stupéfiante.
Fort de cette atmosphère dont les effets indéniables sur ces occupants sont encore à étudier, le KinéKlub s'est donné pour mission d'engager des débats esthétiques qui sont en latence dans les productions même du laboratoire. Ce Klub tend à les rendre plus explicites et à les partager avec convivialité.
Ainsi le KinéKlub, inauguré lors de son édition « proche de zéro », proposera très bientôt des séances consacrées au Lettrisme, à l'Internationale situationniste, au chantier dans l'art ou à l'art du chantier, à travers de l'oeuvre d'artiste comme Gordon Matta Clark, aux systèmes cosmologiques passés et à venir, et à bien d'autres centres d'intérêts qui s'imposeront d'eux-mêmes au moment opportun.
En souhaitant ardemment vous retrouver à ces prochaines éditions du KinéKlub et sûre que pris d'un naturel engouement vous en deviendrez les membres, lecteurs, lectrices de ce wiki, je vous salue.

Ursula de la Jaquinière

</div><div style="float:right; width:48%;">

= English =

== KinéKlub ==

The Kinéklub is totally dedicated to Hackers in the broadest sense including every subgenres : hackers who are proud, in denial, compulsive, taciturn or loquacious, cautious or passionate, hesitant, arrogant, tortured, enthusiastic, to quote only the most common attitudes. The KinéKlub has chosen to grow and flourish in this context of "augmented" Hacking. It fashioned its cradle in a laboratory at the core of an industrial zone, luckily situated in the middle of one of the most pretty landscapes of Île de France, where our medicine are mass-produced and where floats perpetually surprising scents of mysterious and changing fragrance that are incontestably stupefying.
In this atmosphere, whose effects on inhabitants are yet to be studied, the KinéKlub chose the mission to engage into aesthetics debates that are dormant in the laboratory's own productions. This Klub aims to make them more explicit and to share them with conviviality.
The Kinéklub, with its "close to zero" edition, will so offer very soon sessions dedicated to the "lettrisme", the "Internationale situationniste", to the work site of art or the art of the work site, through the oeuvre of artists like Gordon Matta Clark, to cosmological systems past and future, and many other interests that will impose themselves at the appropriate moment.
Looking forward to meeting you at the next edition of Kinéklub and being sure that, taken by a genuine craze, you will become its members, readers of this wiki, I salute you.

Ursula de la Jaquinière

</div><div style="clear:both;"></div>

= Prochaine Edition / Next Edition =

* [[KineKlubEdition3|Edition 3]]

= Editions précédentes / Previous editions =

* [[KineKlubEdition2|Edition 2 : "Chantier & Hétérotopie"]]
* [[KineKlubEdition1|Edition 1 : "IL versus IS"]]
* [[KineKlubEdition0|Edition 0 : "Proche de zéro"]]

KineKlubEdition2

2009-05-26T16:09:27Z

Nico: New page: __NOTOC__ <div style="float:left; width:48%;">  = Français = A la cité des arts, Paris 18ème : Programmation du vendredi 17 ...

__NOTOC__
<div style="float:left; width:48%;"> 

= Français =

A la cité des arts, Paris 18ème : Programmation du vendredi 17 avril 2009 de 19H30 jusqu'à l'aube...

Chantiers & Hétérotopies

Du chantier dans l'art ou l'art du chantier.
Toujours en cours de construction ou en cours de démolition , le cœur de la création se tient plus souvent dans le temps et l'espace de sa gestation que dans son aboutissement ultime et son objet final. Nous nous intéresserons pour ce prochain KinéKlub à des œuvres qui mettent délibérément en avant ce temps et cet espace que nous désignons par le terme de « chantier ». Nous tracerons alors librement une perspective qui nous mène d'un espace public comme celui de la ville et du chantier qui œuvre à sa transformation permanente, à celui plus intérieur de l'atelier, comme un espace organisé pour une construction ou une destruction à venir. Mais l'atelier est aussi le lieu privilégié du détournement où sont possibles les digressions, les tentatives, et où se mesure l'étendue d'un désœuvrement dans une suspension du temps et la quête d'un ré-enchantement, d'une épiphanie. C'est ce moment de l'impulsion, cette origine où la pensée de l'artiste et la matière sont mises à vif et se mettent en branle, que nous rechercherons; principalement, à travers le travail de Gordon Matta Clark mais aussi à travers certaines œuvres de Gregor Schneider, Jean-Pierre Raynaud, John Baldessari,Thomas Hirshhorn, Peter Fischli et David Weiss, Chris Burden, Kurt Schwitters et de collectifs comme Art Workers Coalition et W.A.G.E.

Programmation :

Le chantier : la ville en dé-construction

- Gordon Matta-Clark :
Splitting / Bingo / Underground Daylies (1974-1976)

- Audrey Bartis : Crude Making (Thinking) : Esthétique du Chantier (perfo-conférence 2006-2009)

- Gordon Matta-Clark : Conical Intersect (1975)

- Gordon Matta-Clark :Tree Dance (1971)

- Gordon Matta-Clark :Fresh Kill (1972)

- Gordon Matta-Clark :Day’s End (1975)

- Gordon Matta-Clark :City Slivers (1976)

- Audrey Bartis : le chantier comme hétérotopie (MP3 du texte Hérérotopies, des espaces autres, de Michel Foucault, 1967 + slideshow)

- Chris Burden : The Flying Steamroller (2006)
L’atelier, chantier perpétuel

- Ursula : Kurt Schwitters, Jean-Pierre Raynaud, Gregor Schneider (slide-show)

- Fischli & Weiss : Der Lauf des Dinge (1987)

- Bruce Nauman : Pinch / Neck + Walking In An Exagereted Manner Around The Perimeter Of A Square (1967 – 1968)

- Bruce Nauman : Stamping in The Studio (extrait, 1968)

- John Baldessari : Six Colorfull Inside Jobs (1971)

- Art Safari : Gregor Schneider (émission TV UK, 2007)

Artist @ work :

- Ursula : AWC, Art Workers Coalition
- W.AG.E.

Atelier de Benoît Pingeot
24 rue Norvins
75018 Paris
(métro: Lamarck Caulaincourt ou Abbesses)

code 43 28 A
2eme étage
atelier D3

Pensez à apporter des victuailles sur le thème : pain / fromages / vin / fruits
et un coussin pour votre confort!

A vendredi!

</div><div style="float:right; width:48%;">

= English =

'''Chantier / Hétérotopie'''
schedule of 17th April 2009 at 8pm till dawn
(This schedule changes often, come to check it !)

</div>

KineKlubEdition1

2009-05-26T16:03:52Z

Nico: New page: __NOTOC__ <div style="float:left; width:48%;">  = Français = Edition 1 au Tmplab : Programmation du 13 mars 2009 à 20H00 jusq...

__NOTOC__
<div style="float:left; width:48%;"> 

= Français =

Edition 1 au Tmplab : Programmation du 13 mars 2009 à 20H00 jusqu'à l'aube....

'''"IL versus IS"'''

Isidore Isou / Maurice Lemaître / François Dufrêne / Gil J Wolman / Guy Debord / Raoul Vaneigem / René Viénet / Constant / Asger Jorn et rien d'autre...

et pour commencer :

Traité de bave et d'éternité, Isidore Isou, 1951

Pour faire un film, Maurice Lemaître, 1963

Hurlements en faveur de Sade, Guy Debord, 1952

In girum imus nocte et consumimur igni, Guy Debord, 1978

Intermèdes musicaux de François Dufrêne et d'Isidore Isou

et notre invité d'honneur : Giovanni Martedi

http://www.derives.tv/spip.php?article175

http://www.objectif-cinema.com/spip.php?article3747

http://www.lightcone.org/en/filmmaker-205-giovanni-martedi.html

Attention! NOTA BENE :

Puisque nous programmons une oeuvre super-temporelle de Maurice Lemaître, il va de soi que nous respections les volontés du réalisateur quant à la manière dont la séance doit se dérouler. Il n'est pas dans l'esprit du KinéKlub de montrer des oeuvres comme des documents éculés, sortis un instant de vidéothèques, de bibliothèques, ou de toutes autres oubliettes. Si elles font partie de la programmation du KinéKlub c'est au contraire parce qu'elles gardent intégralement leur puissance esthétique et qu'il est nécessaire de les montrer, en respectant certains protocoles quand celles-ci le demandent. Afin de satisfaire ces exigences, j'invite donc les spectateurs du prochain KinéKlub (n° 1 du Vendredi 13 mars au Tmplab) a venir muni du matériel de son choix, le matériel qu'il jugera adéquat pour cette séance super-temporelle exceptionnelle.
Il me reste à vous décrire ce qu'attend de son spectateur une oeuvre super-temporelle. L' oeuvre de cinéma super-temporelle demande à son public de participer à son principe-même de création. Chaque spectateur est invité à venir à la séance de projection muni de ses propres films, de bandes sonores, qui seront diffusés à un moment déterminé et chacun sera alors encouragé à intervenir de manière créative afin de donner corps à cette oeuvre super-temporelle.

</div><div style="float:right; width:48%;">

= English =

Edition 1 at the Tmplab : schedule of 13th February 2009 at 8pm till dawn

'''"IL versus IS"'''

Isidore Isou / Maurice Lemaître / François Dufrêne / Gil J Wolman / Guy Debord / Raoul Vaneigem / René Viénet / Constant / Asger Jorn et rien d'autre...

As a start :

Traité de bave et d'éternité, Isidore Isou, 1951

Pour faire un film, Maurice Lemaître, 1963

Hurlements en faveur de Sade, Guy Debord, 1952

In girum imus nocte et consumimur igni, Guy Debord, 1978

Intermèdes musicaux de François Dufrêne et d'Isidore Isou

and a special guest : Giovanni Martedi

http://www.derives.tv/spip.php?article175

http://www.objectif-cinema.com/spip.php?article3747

Warning! NOTA BENE :

As we schedule a super-temporal work of Maurice Lemaître, it goes without saying that we will respect his will regarding the way the session should be made. It is not the KinéKlub's spirit to show works as outdated documents, escaping shortly from the videoclub, the library or similar oubliettes. If they are part of the Kinéklub's program, that is because, on the contrary, they keep intact their aesthetic power and that it is necessary to show them according to some protocols when they so require it. In order to comply, I encourage the spectators of the next KinéKlub (Friday Mars 13th at the Tmplab) to come with some materials of his own choice that he would judge adequate for this exceptional super-temporal session.
I still have to describe what awaits a spectator of a super-temporal work. A super-temporal cinematographic work asks to its public to participate into its own creation. Each spectator is invited to come at the session with his/her own movies, audio recordings, that will be played at a particular time and everyone will then be encouraged to participate in a creative way in order to give shape to this super-temporelle work.

</div>

KineKlubEdition0

2009-05-26T16:01:26Z

Nico:

__NOTOC__
<div style="float:left; width:48%;"> 

= Français =

Edition 0 au Tmplab : Programmation du 06 février 2009 à 20H00

'''''Proche de zéro '''''

''Hand-Catching-Lead'', Richard Serra, 1968

''4'33"'', John Cage joué en 2006

Une émission TV des années 50 "I've got a secret" invite John Cage à jouer en direct

''Anémic cinéma'', Marcel Duchamp, 1926

''Island song'', Charlemagne Palestine, 1976

''Question pour un champion'', ''La ville est un trou'', 2007, Charles Pennequin

</div><div style="float:right; width:48%;">

= English =

Edition 0 at the Tmplab : schedule of 6th February 2009 at 8pm

'''''Proche de zéro '''''

''Hand-Catching-Lead'', Richard Serra, 1968

''4'33"'', John Cage played in 2006

A 50s TV show named "I've got a secret" invites John Cage to play live.

''Anémic cinéma'', Marcel Duchamp, 1926

''Island song'', Charlemagne Palestine, 1976

''Question pour un champion'', ''La ville est un trou'', 2007, Charles Pennequin

</div>

KineKlubEdition0

2009-05-26T15:57:23Z

Nico: New page: <div style="float:left; width:48%;">  = Français = Edition 0 au Tmplab : Programmation du 06 février 2009 à 20H00 '''''Proc...

<div style="float:left; width:48%;"> 

= Français =

Edition 0 au Tmplab : Programmation du 06 février 2009 à 20H00

'''''Proche de zéro '''''

''Hand-Catching-Lead'', Richard Serra, 1968

''4'33"'', John Cage joué en 2006

Une émission TV des années 50 "I've got a secret" invite John Cage à jouer en direct

''Anémic cinéma'', Marcel Duchamp, 1926

''Island song'', Charlemagne Palestine, 1976

''Question pour un champion'', ''La ville est un trou'', 2007, Charles Pennequin

</div><div style="float:right; width:48%;">

= English =

Edition 0 at the Tmplab : schedule of 6th February 2009 at 8pm

'''''Proche de zéro '''''

''Hand-Catching-Lead'', Richard Serra, 1968

''4'33"'', John Cage played in 2006

A 50s TV show named "I've got a secret" invites John Cage to play live.

''Anémic cinéma'', Marcel Duchamp, 1926

''Island song'', Charlemagne Palestine, 1976

''Question pour un champion'', ''La ville est un trou'', 2007, Charles Pennequin

</div>

Workshop hacking et grand public

2009-05-13T18:06:22Z

Nico: /* Inscrits/Attendees */

= Summary =
* Titre: Hacking et Grand Public
* Par: Phil
* Date: 14 Mai 2009
* Lieu: /tmp/lab

= Theme =
Table ronde et workshop:
* Quels sont les avantages et inconvénients de présenter le hacking au grand public?
* Est-ce le rôle d'un hacker space comme le /tmp/lab?
* Quel est le role du /tmp/lab et des hackerspaces dans des combats comme celui de HADOPI?
* Quels sont les enseignements à tirer des expériences médias précédentes?
* Quelles sont les futures actions a mettre en oeuvre?
* Qu'en est il du respect de la vie privée des membres du /tmp/lab?

== Inscrits/Attendees ==
Steering : [[User:Phil|Phil]]
* Hellekin
* Nico

[[Category:Workshop]]

Wireless Battle Mesh2009 Report

2009-04-21T18:39:03Z

Nico:

'''This page is gathering the results and feedbacks from the WirelessBattleMesh2009'''

* Configuration feedbacks

* Topology of the test

* Links :
** https://www.open-mesh.net/wiki/2009-04-19-wbm2009-aftermath
** http://hsb.wikidot.com/wbm2009
** http://lists.alioth.debian.org/pipermail/babel-users/2009-April/000229.html

* Photos / Videos :

* TCPDUMP files for "offline" analysis

Wireless Battle Mesh

2009-04-12T23:57:07Z

Nico: /* script for broadcom iwconfig */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009' (but not on all routers *g)
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- to do passwordless login from one node to the next, you may use [[Image:Battle_ssh.tgz]] (contains above key in dropbear format)
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, Fonera
* 00:18:84:25:df:50, , 192.168.30.24, Fonera
* 00:18:84:28:90:78, , 192.168.30.26, Fonera
* 00:18:84:25:1A:60, , 192.168.30.27, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3, WRT54GL
* 192.168.40.11, 00:16:B6:40:F2:D8, WRT54GL
* 192.168.40.13, 00:16:B6:40:F2:D2, WRT54GL
* 192.168.40.14, 00:15:f2:32:f0:84, ASUSWLHDD
* 192.168.40.15, 00:11:D8:58:9F:6E, ASUSWLHDD
* 192.168.40.16, 00:13:D4:D2:09:01, ASUSWLHDD
* 192.168.40.18, 00:11:D8:58:A0:9F, ASUSWLHDD
* 192.168.40.19, 00:11:D8:58:9E:b9, ASUSWLHDD
* 192.168.40.20, 00:11:D8:58:9e:75, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD
* 192.168.40.23, 00:18:84:1C:F7:4C, Fonera
* 192.168.40.24, 00:18:84:25:28:E4, Fonera
* 192.168.40.25, 00:18:84:13:A5:50, Fonera
* 192.168.40.26, 00:18:84:12:F7:2C, Fonera
* 192.168.40.27, 00:18:84:11:A1:E4, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

== Layer 2 measurement ==

As with '''any''' Wifi Network - layer 2 is the most important. If layer 2 does not work properly, there is little sense in working with any layer 3 routing protocol: it would not work anyway.
So here is a script which can interpret the iwconfig command on broadcom based systems (linksys WRT54G* etc):

How to use the script:
while $TRUE; do
for h in $hosts; do
ssh $h iwconfig wl0 >> $outfile
done
sleep 1
done

=== script for broadcom iwconfig ===
<pre>
#!/usr/bin/perl
# Copyright 2009 (C) by L. Aaron Kaplan <aaron@lo-res.org> all rights reserved
#

use strict;
use Time::HiRes;

# format iwconfig
#wl0 IEEE 802.11-DS ESSID:"wbm2009-olsr"
# Mode:Ad-Hoc Frequency:2.412 GHz Cell: CA:CA:FE:CA:CA:20
# Bit Rate=54 Mb/s Tx-Power:32 dBm
# Retry min limit:7 RTS thr:off Fragment thr:off
# Power Management:off
# Link Quality=5/5 Signal level=-49 dBm Noise level=-94 dBm
# Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
# Tx excessive retries:2 Invalid misc:0 Missed beacon:0

my $essid;
my $mode;
my $cell;
my $freq;
my $bitrate;
my $txpower;
my $radio_lq;
my $signal;
my $noise;
my $ts;

my $debug = 0;
$ts = Time::HiRes::time;
print "ts = $ts, localtims(ts)=" . localtime($ts) . "\n" if $debug;

while (<>) {
my $line = $_;
chomp($line);

# if ($line =~ /^$/) { last; } # done

if ($line =~ /ESSID:\"([^\"]+)/) {
$essid = $1;
}

if ($line =~ /Mode:\s*([^ ]+)/) {
$mode = $1;
}
if ($line =~ /Frequency:\s*([^ ]+)\s*GHz/) {
$freq = $1;
}
if ($line =~ /Cell:\s*([^ ]+)/) {
$cell = $1;
}
if ($line =~ /Bit Rate=\s*([^ ]+)\s*Mb\/s/) {
$bitrate = $1;
}
if ($line =~ /Tx-Power:\s*([^ ]+)\s*dBm/) {
$txpower = $1;
}
if ($line =~ /Link Quality=\s*([^ ]+)/) {
$radio_lq = $1;
}
if ($line =~ /Signal level=\s*([^ ]+)/) {
$signal = $1;
}
if ($line =~ /Noise level=\s*([^ ]+)/) {
$noise = $1;
}

}

print <<EOT;
timestamp;ESSID;mode;cell;freq;bitrate;txpower;radio_lq;signal;noise
$ts;$essid;$mode;$cell;$freq;$bitrate;$txpower;$radio_lq;$signal;$noise
EOT

</pre>

=== Data Gathering ===

Here's the script that was used on 3 Fonera 2202 to collect tcpdump raw capture files on USB sticks:
<pre>
#!/bin/sh /etc/rc.common
# Copyright (C) 2009 OpenWrt.org

START=99
STOP=99

DATA_DIR=/mnt/usbdrive
DUMP_FILE=$(mktemp $DATA_DIR/tcpdump-XXXXXXXX)
PID_FILE=/var/run/tcpdump.pid
IF=$(uci get network.wifi.ifname)

start() {
local i=1
while [ ! -d $DATA_DIR ]; do
sleep 1
[ $i -ge 9 ] && exit 0
i=$(($i + 1))
done
tcpdump -i $IF -w $DUMP_FILE -s 0 >/dev/null 2>&1 &
echo $! >$PID_FILE
}

stop() {
[ -f $PID_FILE ] && {
kill -TERM $(cat $PID_FILE)
rm -f $PID_FILE
}
}
</pre>

Wireless Battle Mesh

2009-04-12T15:36:27Z

Nico: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, Fonera
* 00:18:84:25:df:50, , 192.168.30.24, Fonera
* 00:18:84:28:90:78, , 192.168.30.26, Fonera
* 00:18:84:25:1A:60, , 192.168.30.27, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3, WRT54GL
* 192.168.40.11, 00:16:B6:40:F2:D8, WRT54GL
* 192.168.40.13, 00:16:B6:40:F2:D2, WRT54GL
* 192.168.40.14, 00:15:f2:32:f0:84, ASUSWLHDD
* 192.168.40.15, 00:11:D8:58:9F:6E, ASUSWLHDD
* 192.168.40.16, 00:13:D4:D2:09:01, ASUSWLHDD
* 192.168.40.18, 00:11:D8:58:A0:9F, ASUSWLHDD
* 192.168.40.19, 00:11:D8:58:9E:b9, ASUSWLHDD
* 192.168.40.20, 00:11:D8:58:9e:75, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD
* 192.168.40.23, 00:18:84:1C:F7:4C, Fonera
* 192.168.40.24, 00:18:84:25:28:E4, Fonera
* 192.168.40.25, 00:18:84:13:A5:50, Fonera
* 192.168.40.26, 00:18:84:12:F7:2C, Fonera
* 192.168.40.27, 00:18:84:11:A1:E4, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

Wireless Battle Mesh

2009-04-12T14:59:22Z

Nico: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, Fonera
* 00:18:84:25:df:50, , 192.168.30.24, Fonera
* 00:18:84:27:7e:e0, , 192.168.30.25, Fonera
* 00:18:84:28:90:78, , 192.168.30.26, Fonera
* 00:18:84:25:1A:60, , 192.168.30.27, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3, WRT54GL
* 192.168.40.11, 00:16:B6:40:F2:D8, WRT54GL
* 192.168.40.13, 00:16:B6:40:F2:D2, WRT54GL
* 192.168.40.14, 00:15:f2:32:f0:84, ASUSWLHDD
* 192.168.40.15, 00:11:D8:58:9F:6E, ASUSWLHDD
* 192.168.40.16, 00:13:D4:D2:09:01, ASUSWLHDD
* 192.168.40.18, 00:11:D8:58:A0:9F, ASUSWLHDD
* 192.168.40.19, 00:11:D8:58:9E:b9, ASUSWLHDD
* 192.168.40.20, 00:11:D8:58:9e:75, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD
* 192.168.40.23, 00:18:84:1C:F7:4C, Fonera
* 192.168.40.24, 00:18:84:25:28:E4, Fonera
* 192.168.40.25, 00:18:84:13:A5:50, Fonera
* 192.168.40.26, 00:18:84:12:F7:2C, Fonera
* 192.168.40.27, 00:18:84:11:A1:E4, Fonera
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD
* XX:XX:XX:XX:XX:XX, , 192.168.20.166, LAPTOP

Wireless Battle Mesh

2009-04-12T12:00:17Z

Nico: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.30.1, Fonera (kappa)
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, Fonera
* 00:18:84:25:df:50, , 192.168.30.24, Fonera
* 00:18:84:27:7e:e0, , 192.168.30.25, Fonera
* 00:18:84:28:90:78, , 192.168.30.26, Fonera
* 00:18:84:25:1A:60, , 192.168.30.27, Fonera

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3, WRT54GL
* 192.168.40.11, 00:16:B6:40:F2:D8, WRT54GL
* 192.168.40.13, 00:16:B6:40:F2:D2, WRT54GL
* 192.168.40.14, 00:15:f2:32:f0:84, ASUSWLHDD
* 192.168.40.15, 00:11:D8:58:9F:6E, ASUSWLHDD
* 192.168.40.16, 00:13:D4:D2:09:01, ASUSWLHDD
* 192.168.40.18, 00:11:D8:58:A0:9F, ASUSWLHDD
* 192.168.40.19, 00:11:D8:58:9E:b9, ASUSWLHDD
* 192.168.40.20, 00:11:D8:58:9e:75, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD
* 192.168.40.23, 00:18:84:1C:F7:4C, Fonera
* 192.168.40.24, 00:18:84:25:28:E4, Fonera
* 192.168.40.25, 00:18:84:13:A5:50, Fonera
* 192.168.40.26, 00:18:84:12:F7:2C, Fonera
* 192.168.40.27, 00:18:84:11:A1:E4, Fonera

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-12T11:41:39Z

Nico: /* Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.30.1, Fonera (kappa)
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, fonera
* 00:18:84:25:df:50, , 192.168.30.24, fonera
* 00:18:84:27:7e:e0, , 192.168.30.25, fonera
* 00:18:84:28:90:78, , 192.168.30.26, fonera

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3, WRT54GL
* 192.168.40.11, 00:16:B6:40:F2:D8, WRT54GL
* 192.168.40.13, 00:16:B6:40:F2:D2, WRT54GL
* 192.168.40.14, 00:15:f2:32:f0:84, ASUSWLHDD
* 192.168.40.15, 00:11:D8:58:9F:6E, ASUSWLHDD
* 192.168.40.16, 00:13:D4:D2:09:01, ASUSWLHDD
* 192.168.40.18, 00:11:D8:58:A0:9F, ASUSWLHDD
* 192.168.40.19, 00:11:D8:58:9E:b9, ASUSWLHDD
* 192.168.40.20, 00:11:D8:58:9e:75, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD
* 192.168.40.23, 00:18:84:1C:F7:4C, Fonera
* 192.168.40.24, 00:18:84:25:28:E4, Fonera
* 192.168.40.25, 00:18:84:13:A5:50, Fonera
* 192.168.40.26, 00:18:84:12:F7:2C, Fonera
* 192.168.40.27, 00:18:84:11:A1:E4, Fonera

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-12T11:09:41Z

Nico: /* Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:11:D8:58:9E:92, , 192.168.20.14, ASUSWLHDD
* 00:11:D8:43:6B:5D, , 192.168.20.15, ASUSWLHDD
* 00:11:D8:58:9C:84, , 192.168.20.16, ASUSWLHDD
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:11:D8:58:9D:94, , 192.168.20.18, ASUSWLHDD
* 00:11:D8:58:A0:A0, , 192.168.20.19, ASUSWLHDD
* 00:11:D8:58:9D:7B, , 192.168.20.20, ASUSWLHDD
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL
* 00:13:D4:D2:09:24, , 192.168.20.22, ASUSWLHDD
* 00:18:84:00:70:13, , 192.168.20.23, FONERA
* 00:18:84:22:A2:DC, , 192.168.20.24, FONERA
* 00:18:84:27:19:5C, , 192.168.20.25, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:21:6B:8C, , 192.168.20.26, FONERA
* 00:18:84:1C:EB:28, , 192.168.20.27, FONERA

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.30.1, Fonera (kappa)
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:14:bf:d2:65:86, , 192.168.30.11, WRT54GL
* 00:14:bf:d2:65:9e, , 192.168.30.12, WRT54GL
* 00:11:D8:43:6A:27, , 192.168.30.14, ASUSWLHDD
* 00:11:2F:9D:1B:E4, , 192.168.30.15, ASUSWLHDD
* 00:11:D8:58:9D:9A, , 192.168.30.16, ASUSWLHDD
* 00:14:bf:d2:6c:04, , 192.168.30.17, WRT54GL
* 00:11:D8:58:9D:10, , 192.168.30.18, ASUSWLHDD
* 00:11:D8:43:6A:C9, , 192.168.30.19, ASUSWLHDD
* 00:11:D8:13:D4:D2, , 192.168.30.20, ASUSWLHDD
* 00:11:D8:58:9F:1D, , 192.168.30.22, ASUSWLHDD
* 00:18:84:25:69:50, , 192.168.30.23, fonera
* 00:18:84:25:df:50, , 192.168.30.24, fonera
* 00:18:84:27:7e:e0, , 192.168.30.25, fonera
* 00:18:84:28:90:78, , 192.168.30.26, fonera

CONFLICTING (find it and change ip) :
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

* 192.168.40.1, 00:0F:66:24:EE:2F, WRT54G
* 192.168.40.2, 00:10:72:88:7F:BE, WRT54GS
* 192.168.40.3, 00:12:17:26:EB:84, WRT54G v2
* 192.168.40.5, 00:13:10:30:21:9G, WRT54GS 1.1
* 192.168.40.6, 00:16:B6:40:F9:F2, WRT54GLgl 1.1
* 192.168.40.7, 00:14:BF:D2:65:A1, WRT54GL
* 192.168.40.8, 00:16:B6:40:F2:C6, WRT54GL
* 192.168.40.9, 00:0F:66:C7:B9:6F, WRT54GS
* 192.168.40.10, 00:16:B6:40:F2:C3
* 192.168.40.11, 00:16:B6:40:F2:D8
* 192.168.40.13, 00:16:b6:40:f2:d2
* 00:15:f2:32:f0:84, , 192.168.40.14, ASUSWLHDD
* 00:11:D8:58:9f:6e, , 192.168.40.15, ASUSWLHDD
* 00:13:d4:d2:09:01, , 192.168.40.16, ASUSWLHDD
* 00:11:D8:58:a0:9f, , 192.168.40.18, ASUSWLHDD
* 00:11:D8:58:9E:b9, , 192.168.40.19, ASUSWLHDD
* 00:11:D8:58:9e:75, , 192.168.40.20, ASUSWLHDD
* 192.168.40.21, 00:11:2F:9D:15:86, ASUS WL500GD

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T19:03:35Z

Nico: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 */

[[Image:DSC00007.JPG|400px]]
hackers preparing

[[Image:DSC00008.JPG|400px]] and flashing linksyses

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.30.0/24 ====

* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.30.1, Fonera (kappa)
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.30.2, Fonera (dzeta)
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.30.3, Fonera (eta)
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.30.4, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.30.5, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.30.6, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.30.7, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.30.8, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.30.9, WRT54GL
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.30.10, WRT54GS
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T15:33:29Z

Nico: /* Setup */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:
<pre>
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
</pre>

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1

==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 ====

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T14:04:26Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1

==== Channel: 5, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 ====

==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.O/24 ====

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T12:46:37Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

==== Channel: 1, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:10, IP: 192.168.x.10/16 ====

* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.101.10, WRT54G v1.1

==== Channel: 1, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.x.20/16 ====

==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:30, IP: 192.168.x.30/16 ====

==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T10:28:38Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD

Wireless Battle Mesh

2009-04-11T08:24:45Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera

Wireless Battle Mesh

2009-04-11T08:04:25Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera

Wireless Battle Mesh

2009-04-11T06:12:47Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>
00:18:84:21:6B:8C
(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera

Wireless Battle Mesh

2009-04-11T05:50:48Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera

Wireless Battle Mesh

2009-04-11T05:03:54Z

Nico: /* Wireless IP adresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera

Wireless Battle Mesh

2009-04-11T04:57:37Z

Nico: /* For OLSR */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node on an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device wifi0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2

Wireless Battle Mesh

2009-04-11T04:47:03Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

== Setup ==

Nodes have been flashed with custom firmware images:
- root password is set to 'wbm2009'
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/
- LAN configuration was not changed and default to 192.168.1.1/24
- Default wireless configuration is:
- ssid: wbm2009
- mode: adhoc
- encryption: none

=== Wireless IP adresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2

Wireless Battle Mesh

2009-04-11T03:15:19Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2

Wireless Battle Mesh

2009-04-11T03:08:41Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1

Wireless Battle Mesh

2009-04-11T02:42:31Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1

Wireless Battle Mesh

2009-04-11T02:38:08Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.44.132, WRT54G v1.1

Wireless Battle Mesh

2009-04-11T02:29:42Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1

Wireless Battle Mesh

2009-04-11T02:26:02Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1

Wireless Battle Mesh

2009-04-11T02:21:32Z

Nico: /* Addresses */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS

Wireless Battle Mesh

2009-04-11T02:03:19Z

Nico: /* WRT54GSv4 */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

==== WRT54GL ====
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120

==== WRT54GSv4 ====
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128

Wireless Battle Mesh

2009-04-11T01:51:39Z

Nico: /* WRT54GSv4 */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

==== WRT54GL ====
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120

==== WRT54GSv4 ====
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127

Wireless Battle Mesh

2009-04-11T01:34:49Z

Nico: /* WRT54GSv4 */

== Call for Participants ==

We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.

The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.

OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :
* VLANs
* Captive portal
* Authentication
* Admin portal

Concerning the mesh-protocols, selected targeted protocols are :
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)

Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).

The TMPLAB core team.

== Agenda ==

* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes
* Sat, April 11th :
** Morning : setting up the nodes on-site and validation of the different subnets
** Afternoon : first series of tests and measurements with fixed nodes
* Sun 12th :
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)
** Afternoon : Optimization of the protocols and Conclusion

== Evaluation ==

=== Criterion ===
We will evaluate the routing protocols using the following criterion :

* time to setup a node
* CPU activity
* network activity
* convergence time
* scalability
* mobile devices handling

=== Platform ===

The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.

== Hardware platforms ==

We managed to get sponsoring for such hardware :

* Linksys WRT54G/GS
* Asus WL500G Deluxe/Premium
* Fon Fonera

For each protocol 25 nodes will be setup, with the following quantities :

* FON : 25 nodes
* HSB : 32 nodes
* Wireless-fr : 6 nodes
* Tmplab : 15 nodes
* BATMAN : 10 nodes
* Thus0 : 5 nodes

Total : 93 nodes. In case of problems, spare nodes are highly wanted.

=== Identification ===

For each and every single node in the network, please prepare stickers containing the following informations :

* routing protocol in use
* MAC address of the Wi-Fi interface
* IP address in the management network
* Owner
* hostname (e.g: node 1-babel)

=== Node parts ===

Each and every single node consists of the following physical parts:

* A wireless router (Linksys, Fon, Asus ...)
* Antennas screwed on the router (no external unless specified)
* Power supply unit
* (Battery)

== Software platform ==

The different software versions in use during the Wireless Battle Mesh are :

* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]
* olsrd-0.5.6-r4
* batman-adv-r1220

OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.

=== Software configuration ===

Every node should be configured with the following settings :

* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)
* user: root
* password: wbm2009

We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :

* version: 2
* community: wbm2009
* permissions: ro
* allow graph disk/flash activity (e.g: disk /)

=== Package list and repositories ===

A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :

* ntpclient (or busybox's rdate)
* wprobe
* snmpd

== Wireless configuration ==

Each node will be working in '''Ad-hoc''' mode using the following settings.

=== For babel ===

* SSID: babel
* Channel: 1
* Encryption: none

=== For Batman ===

* SSID: batman
* Channel: 5
* Encryption: none

=== For OLSR ===

* SSID: olsr
* Channel: 11
* Encryption: none

The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:

<pre>
config wifi-device wl0
option type broadcom
option channel 1

config wifi-iface
option device wl0
option network wifi
option mode adhoc
option ssid babel
option encryption none
</pre>

For an OLSR node and an Atheros board:

<pre>
config wifi-device wifi0
option type atheros
option channel 11

config wifi-iface
option device ath0
option network wifi
option mode sta
option ssid olsr
option encryption none
</pre>

Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.

== Network topology ==

There will be different subnets corresponding to different purposes.

=== Protocol wide subnet ===

This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:

* Babel: 192.168.40.0/24
* Batman: 192.168.30.0/24
* OLSR: 192.168.20.0/24

An '''/etc/config/network''' file for a Babel node looks like this:

<pre>
#### VLAN configuration
config switch eth0
option vlan0 "1 2 3 4 5*"
option vlan1 "0 5"

#### Loopback configuration
config interface loopback
option ifname "lo"
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0

#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.2.1
option netmask 255.255.255.0

#### Wi-Fi configuration
config interface wifi
option ifname "wl0"
option proto static
option ipaddr 192.168.40.1
option netmask 255.255.255.0
</pre>

=== Addresses ===

you can set the addres this way:
<pre>
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit
</pre>

(LAN MAC, WiFi MAC, WiFi IP)

==== WRT54GL ====
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120

==== WRT54GSv4 ====
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125