<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.tmplab.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jch</id>
		<title>Tmplab - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.tmplab.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jch"/>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php/Special:Contributions/Jch"/>
		<updated>2026-05-17T17:23:03Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.1</generator>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1300</id>
		<title>Babel</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1300"/>
				<updated>2009-04-10T20:11:19Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Babel versions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Babel =&lt;br /&gt;
&lt;br /&gt;
Babel is one of the three routing protocols tested at the [[Wireless_Battle_Mesh]].  The upstream Babel page: http://www.pps.jussieu.fr/~jch/software/babel/&lt;br /&gt;
&lt;br /&gt;
== Babel versions ==&lt;br /&gt;
&lt;br /&gt;
0.94 is the most recent released version of Babel.  It has some algorithmic changes w.r.t. 0.92 and some bug reports w.r.t. 0.93, and is the version that we intend to test.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
Babel doesn't need much, if any, configuration.  Simply listing the interfaces participating in the mesh is enough:&lt;br /&gt;
&lt;br /&gt;
 babel wlan0 eth0&lt;br /&gt;
&lt;br /&gt;
Exceptions:&lt;br /&gt;
* Babel uses some optimisations on wired interfaces.  If you have interfaces that Babel mis-detects as wired (e.g. weird tunnelling setups, bridging), you need to specify the '''-w''' flag on Babel's command line;&lt;br /&gt;
* Babel assumes bridged interfaces are wireless, i.e. disables the optimisations on bridged interfaces.  The best solution is to un-bridge the interfaces.&lt;br /&gt;
&lt;br /&gt;
== Packaging ==&lt;br /&gt;
&lt;br /&gt;
OpenWrt packages babel version 0.93 and should soon be availble using snapshots, if not, we will post files here.  Babel's author uses ipkg-buildpackage to build his own packages.&lt;br /&gt;
&lt;br /&gt;
[[Image:Babel-ipkg.tgz]]&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1299</id>
		<title>Wireless Battle Mesh</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1299"/>
				<updated>2009-04-10T20:10:48Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Software platform */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Call for Participants ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 :&lt;br /&gt;
* VLANs&lt;br /&gt;
* Captive portal&lt;br /&gt;
* Authentication&lt;br /&gt;
* Admin portal&lt;br /&gt;
&lt;br /&gt;
Concerning the mesh-protocols, selected targeted protocols are :&lt;br /&gt;
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)&lt;br /&gt;
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt&lt;br /&gt;
* 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/)&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
The TMPLAB core team.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes&lt;br /&gt;
* Sat, April 11th : &lt;br /&gt;
** Morning : setting up the nodes on-site and validation of the different subnets&lt;br /&gt;
** Afternoon : first series of tests and measurements with fixed nodes&lt;br /&gt;
* Sun 12th : &lt;br /&gt;
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)&lt;br /&gt;
** Afternoon : Optimization of the protocols and Conclusion&lt;br /&gt;
&lt;br /&gt;
== Evaluation ==&lt;br /&gt;
&lt;br /&gt;
=== Criterion ===&lt;br /&gt;
We will evaluate the routing protocols using the following criterion :&lt;br /&gt;
&lt;br /&gt;
* time to setup a node&lt;br /&gt;
* CPU activity&lt;br /&gt;
* network activity&lt;br /&gt;
* convergence time&lt;br /&gt;
* scalability&lt;br /&gt;
* mobile devices handling&lt;br /&gt;
&lt;br /&gt;
=== Platform ===&lt;br /&gt;
&lt;br /&gt;
The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.&lt;br /&gt;
&lt;br /&gt;
== Hardware platforms ==&lt;br /&gt;
&lt;br /&gt;
We managed to get sponsoring for such hardware :&lt;br /&gt;
&lt;br /&gt;
* Linksys WRT54G/GS&lt;br /&gt;
* Asus WL500G Deluxe/Premium&lt;br /&gt;
* Fon Fonera&lt;br /&gt;
&lt;br /&gt;
For each protocol 25 nodes will be setup, with the following quantities :&lt;br /&gt;
&lt;br /&gt;
* FON : 25 nodes&lt;br /&gt;
* HSB : 32 nodes&lt;br /&gt;
* Wireless-fr : 6 nodes&lt;br /&gt;
* Tmplab : 15 nodes&lt;br /&gt;
* BATMAN : 10 nodes&lt;br /&gt;
* Thus0 : 5 nodes&lt;br /&gt;
&lt;br /&gt;
Total : 93 nodes. In case of problems, spare nodes are highly wanted.&lt;br /&gt;
&lt;br /&gt;
=== Identification ===&lt;br /&gt;
&lt;br /&gt;
For each and every single node in the network, please prepare stickers containing the following informations :&lt;br /&gt;
&lt;br /&gt;
* routing protocol in use&lt;br /&gt;
* MAC address of the Wi-Fi interface&lt;br /&gt;
* IP address in the management network&lt;br /&gt;
* Owner&lt;br /&gt;
* hostname (e.g: node 1-babel)&lt;br /&gt;
&lt;br /&gt;
=== Node parts ===&lt;br /&gt;
&lt;br /&gt;
Each and every single node consists of the following physical parts:&lt;br /&gt;
&lt;br /&gt;
* A wireless router (Linksys, Fon, Asus ...)&lt;br /&gt;
* Antennas screwed on the router (no external unless specified)&lt;br /&gt;
* Power supply unit&lt;br /&gt;
* (Battery)&lt;br /&gt;
&lt;br /&gt;
== Software platform ==&lt;br /&gt;
&lt;br /&gt;
The different software versions in use during the Wireless Battle Mesh are :&lt;br /&gt;
&lt;br /&gt;
* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]&lt;br /&gt;
* olsrd-0.5.6-r4&lt;br /&gt;
* batman-adv-r1220&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Software configuration ===&lt;br /&gt;
&lt;br /&gt;
Every node should be configured with the following settings :&lt;br /&gt;
&lt;br /&gt;
* hostname: node&amp;lt;N&amp;gt;-&amp;lt;routing protocol&amp;gt; (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)&lt;br /&gt;
* user: root&lt;br /&gt;
* password: wbm2009&lt;br /&gt;
&lt;br /&gt;
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 :&lt;br /&gt;
&lt;br /&gt;
* version: 2&lt;br /&gt;
* community: wbm2009&lt;br /&gt;
* permissions: ro&lt;br /&gt;
* allow graph disk/flash activity (e.g: disk /)&lt;br /&gt;
&lt;br /&gt;
=== Package list and repositories ===&lt;br /&gt;
&lt;br /&gt;
A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :&lt;br /&gt;
&lt;br /&gt;
* ntpclient (or busybox's rdate)&lt;br /&gt;
* wprobe&lt;br /&gt;
* snmpd&lt;br /&gt;
&lt;br /&gt;
== Wireless configuration ==&lt;br /&gt;
&lt;br /&gt;
Each node will be working in '''Ad-hoc''' mode using the following settings.&lt;br /&gt;
&lt;br /&gt;
=== For babel ===&lt;br /&gt;
&lt;br /&gt;
* SSID: babel&lt;br /&gt;
* Channel: 1&lt;br /&gt;
* Encryption: none&lt;br /&gt;
&lt;br /&gt;
=== For Batman ===&lt;br /&gt;
&lt;br /&gt;
* SSID: batman&lt;br /&gt;
* Channel: 5&lt;br /&gt;
* Encryption: none&lt;br /&gt;
&lt;br /&gt;
=== For OLSR ===&lt;br /&gt;
&lt;br /&gt;
* SSID: olsr&lt;br /&gt;
* Channel: 11&lt;br /&gt;
* Encryption: none&lt;br /&gt;
&lt;br /&gt;
The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
config wifi-device  wl0&lt;br /&gt;
        option type     broadcom&lt;br /&gt;
        option channel  1&lt;br /&gt;
&lt;br /&gt;
config wifi-iface&lt;br /&gt;
        option device   wl0&lt;br /&gt;
        option network  wifi&lt;br /&gt;
        option mode     adhoc&lt;br /&gt;
        option ssid     babel&lt;br /&gt;
        option encryption none&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For an OLSR node and an Atheros board:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
config wifi-device  wifi0&lt;br /&gt;
        option type     atheros&lt;br /&gt;
        option channel  11&lt;br /&gt;
&lt;br /&gt;
config wifi-iface&lt;br /&gt;
        option device   ath0&lt;br /&gt;
        option network  wifi&lt;br /&gt;
        option mode     sta&lt;br /&gt;
        option ssid     olsr&lt;br /&gt;
        option encryption none&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.&lt;br /&gt;
&lt;br /&gt;
== Network topology ==&lt;br /&gt;
&lt;br /&gt;
There will be different subnets corresponding to different purposes.&lt;br /&gt;
&lt;br /&gt;
=== Protocol wide subnet ===&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* Babel: 192.168.40.0/24&lt;br /&gt;
* Batman: 192.168.30.0/24&lt;br /&gt;
* OLSR: 192.168.20.0/24&lt;br /&gt;
&lt;br /&gt;
An '''/etc/config/network''' file for a Babel node looks like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#### VLAN configuration&lt;br /&gt;
config switch eth0&lt;br /&gt;
        option vlan0    &amp;quot;1 2 3 4 5*&amp;quot;&lt;br /&gt;
        option vlan1    &amp;quot;0 5&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#### Loopback configuration&lt;br /&gt;
config interface loopback&lt;br /&gt;
        option ifname   &amp;quot;lo&amp;quot;&lt;br /&gt;
        option proto    static&lt;br /&gt;
        option ipaddr   127.0.0.1&lt;br /&gt;
        option netmask  255.0.0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#### LAN configuration&lt;br /&gt;
config interface lan&lt;br /&gt;
        option type     bridge&lt;br /&gt;
        option ifname   &amp;quot;eth0.0&amp;quot;&lt;br /&gt;
        option proto    static&lt;br /&gt;
        option ipaddr   192.168.2.1&lt;br /&gt;
        option netmask  255.255.255.0&lt;br /&gt;
&lt;br /&gt;
#### Wi-Fi configuration&lt;br /&gt;
config interface wifi&lt;br /&gt;
        option ifname   &amp;quot;wl0&amp;quot;&lt;br /&gt;
        option proto    static&lt;br /&gt;
        option ipaddr   192.168.40.1&lt;br /&gt;
        option netmask  255.255.255.0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1260</id>
		<title>Babel</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1260"/>
				<updated>2009-04-04T17:11:51Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Babel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Babel =&lt;br /&gt;
&lt;br /&gt;
Babel is one of the three routing protocols tested at the [[Wireless_Battle_Mesh]].  The upstream Babel page: http://www.pps.jussieu.fr/~jch/software/babel/&lt;br /&gt;
&lt;br /&gt;
== Babel versions ==&lt;br /&gt;
&lt;br /&gt;
0.93 is the most recent released version of Babel.  It has some algorithmic changes w.r.t. 0.92, and is the version that we intend to test.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
Babel doesn't need much, if any, configuration.  Simply listing the interfaces participating in the mesh is enough:&lt;br /&gt;
&lt;br /&gt;
 babel wlan0 eth0&lt;br /&gt;
&lt;br /&gt;
Exceptions:&lt;br /&gt;
* Babel uses some optimisations on wired interfaces.  If you have interfaces that Babel mis-detects as wired (e.g. weird tunnelling setups, bridging), you need to specify the '''-w''' flag on Babel's command line;&lt;br /&gt;
* Babel assumes bridged interfaces are wireless, i.e. disables the optimisations on bridged interfaces.  The best solution is to un-bridge the interfaces.&lt;br /&gt;
&lt;br /&gt;
== Packaging ==&lt;br /&gt;
&lt;br /&gt;
The OpenWRT package for Babel is out-of-date.  Babel's author uses ipkg-buildpackage to build his own packages.&lt;br /&gt;
&lt;br /&gt;
[[Image:Babel-ipkg.tgz]]&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1259</id>
		<title>Babel</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1259"/>
				<updated>2009-04-04T17:06:24Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Packaging */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Babel =&lt;br /&gt;
&lt;br /&gt;
The upstream Babel page: http://www.pps.jussieu.fr/~jch/software/babel/&lt;br /&gt;
&lt;br /&gt;
== Babel versions ==&lt;br /&gt;
&lt;br /&gt;
0.93 is the most recent released version of Babel.  It has some algorithmic changes w.r.t. 0.92, and is the version that we intend to test.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
Babel doesn't need much, if any, configuration.  Simply listing the interfaces participating in the mesh is enough:&lt;br /&gt;
&lt;br /&gt;
 babel wlan0 eth0&lt;br /&gt;
&lt;br /&gt;
Exceptions:&lt;br /&gt;
* Babel uses some optimisations on wired interfaces.  If you have interfaces that Babel mis-detects as wired (e.g. weird tunnelling setups, bridging), you need to specify the '''-w''' flag on Babel's command line;&lt;br /&gt;
* Babel assumes bridged interfaces are wireless, i.e. disables the optimisations on bridged interfaces.  The best solution is to un-bridge the interfaces.&lt;br /&gt;
&lt;br /&gt;
== Packaging ==&lt;br /&gt;
&lt;br /&gt;
The OpenWRT package for Babel is out-of-date.  Babel's author uses ipkg-buildpackage to build his own packages.&lt;br /&gt;
&lt;br /&gt;
[[Image:Babel-ipkg.tgz]]&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=File:Babel-ipkg.tgz&amp;diff=1258</id>
		<title>File:Babel-ipkg.tgz</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=File:Babel-ipkg.tgz&amp;diff=1258"/>
				<updated>2009-04-04T17:05:56Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: Files needed to build a Babel 0.93 package with ipkg-buildpackage.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Files needed to build a Babel 0.93 package with ipkg-buildpackage.&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1257</id>
		<title>Babel</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Babel&amp;diff=1257"/>
				<updated>2009-04-04T16:59:04Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: New page: = Babel =  The upstream Babel page: http://www.pps.jussieu.fr/~jch/software/babel/  == Babel versions ==  0.93 is the most recent released version of Babel.  It has some algorithmic change...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Babel =&lt;br /&gt;
&lt;br /&gt;
The upstream Babel page: http://www.pps.jussieu.fr/~jch/software/babel/&lt;br /&gt;
&lt;br /&gt;
== Babel versions ==&lt;br /&gt;
&lt;br /&gt;
0.93 is the most recent released version of Babel.  It has some algorithmic changes w.r.t. 0.92, and is the version that we intend to test.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
Babel doesn't need much, if any, configuration.  Simply listing the interfaces participating in the mesh is enough:&lt;br /&gt;
&lt;br /&gt;
 babel wlan0 eth0&lt;br /&gt;
&lt;br /&gt;
Exceptions:&lt;br /&gt;
* Babel uses some optimisations on wired interfaces.  If you have interfaces that Babel mis-detects as wired (e.g. weird tunnelling setups, bridging), you need to specify the '''-w''' flag on Babel's command line;&lt;br /&gt;
* Babel assumes bridged interfaces are wireless, i.e. disables the optimisations on bridged interfaces.  The best solution is to un-bridge the interfaces.&lt;br /&gt;
&lt;br /&gt;
== Packaging ==&lt;br /&gt;
&lt;br /&gt;
The OpenWRT package for Babel is out-of-date.  Babel's author uses ipkg-buildpackage to build his own packages.&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1256</id>
		<title>Wireless Battle Mesh</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1256"/>
				<updated>2009-04-04T16:50:39Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Software platform */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Call for Participants ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 :&lt;br /&gt;
* VLANs&lt;br /&gt;
* Captive portal&lt;br /&gt;
* Authentication&lt;br /&gt;
* Admin portal&lt;br /&gt;
&lt;br /&gt;
Concerning the mesh-protocols, selected targeted protocols are :&lt;br /&gt;
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)&lt;br /&gt;
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt&lt;br /&gt;
* 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/)&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
The TMPLAB core team.&lt;br /&gt;
&lt;br /&gt;
== Hardware platforms ==&lt;br /&gt;
&lt;br /&gt;
We managed to get sponsoring for such hardware :&lt;br /&gt;
&lt;br /&gt;
* Linksys WRT54G/GS&lt;br /&gt;
* Asus WL500G Deluxe/Premium&lt;br /&gt;
* Fon Fonera&lt;br /&gt;
&lt;br /&gt;
== Software platform ==&lt;br /&gt;
&lt;br /&gt;
The different software versions in use during the Wireless Battle Mesh are :&lt;br /&gt;
&lt;br /&gt;
* babel-0.93, there's also a page about [[Babel]]&lt;br /&gt;
* olsrd-0.5.6-r4&lt;br /&gt;
* batman-adv-r1220&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Network topology ==&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1255</id>
		<title>Wireless Battle Mesh</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&amp;diff=1255"/>
				<updated>2009-04-04T16:50:20Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Software platform */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Call for Participants ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 :&lt;br /&gt;
* VLANs&lt;br /&gt;
* Captive portal&lt;br /&gt;
* Authentication&lt;br /&gt;
* Admin portal&lt;br /&gt;
&lt;br /&gt;
Concerning the mesh-protocols, selected targeted protocols are :&lt;br /&gt;
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)&lt;br /&gt;
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt&lt;br /&gt;
* 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/)&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
The TMPLAB core team.&lt;br /&gt;
&lt;br /&gt;
== Hardware platforms ==&lt;br /&gt;
&lt;br /&gt;
We managed to get sponsoring for such hardware :&lt;br /&gt;
&lt;br /&gt;
* Linksys WRT54G/GS&lt;br /&gt;
* Asus WL500G Deluxe/Premium&lt;br /&gt;
* Fon Fonera&lt;br /&gt;
&lt;br /&gt;
== Software platform ==&lt;br /&gt;
&lt;br /&gt;
The different software versions in use during the Wireless Battle Mesh are :&lt;br /&gt;
&lt;br /&gt;
* babel-0.93, there's also a page about [Babel]&lt;br /&gt;
* olsrd-0.5.6-r4&lt;br /&gt;
* batman-adv-r1220&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Network topology ==&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=User:Jch&amp;diff=1248</id>
		<title>User:Jch</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=User:Jch&amp;diff=1248"/>
				<updated>2009-04-03T23:25:15Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: New page: http://www.pps.jussieu.fr/~jch/software/&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://www.pps.jussieu.fr/~jch/software/&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=OpenWrt_:_une_introduction&amp;diff=1247</id>
		<title>OpenWrt : une introduction</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=OpenWrt_:_une_introduction&amp;diff=1247"/>
				<updated>2009-04-03T23:24:53Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Inscrits/Attendees */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Workshop OpenWrt ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Openwrt-logo.png|right]] Samedi 4 avril 2009 au /tmp/lab ; de 14h30 à 20h30.&lt;br /&gt;
&lt;br /&gt;
Voici les différents points qui seront abordés:&lt;br /&gt;
Sur OpenWrt :&lt;br /&gt;
&lt;br /&gt;
* de comprendre la structure générale d'OpenWrt&lt;br /&gt;
* de construire votre propre image du firmware pour votre cible matérielle&lt;br /&gt;
* de porter un logiciel de votre choix et de le tester&lt;br /&gt;
* de le flasher depuis le firmware original ou depuis une ancienne version &lt;br /&gt;
d'OpenWrt&lt;br /&gt;
&lt;br /&gt;
Sur le Wi-Fi :&lt;br /&gt;
&lt;br /&gt;
* de faire un petit rappel sur les différents modes de fonctionnement &lt;br /&gt;
possibles : Master, Managed, Mesh, Ad-hoc, Monitor&lt;br /&gt;
* de tester ces différents modes de fonctionnement (suivant le matériel)  et &lt;br /&gt;
les configurations correspondantes dans OpenWrt&lt;br /&gt;
&lt;br /&gt;
Sur les protocoles de routage :&lt;br /&gt;
&lt;br /&gt;
* quelques réseaux de tests simples utilisants OLSR, 802.11s et Babel.&lt;br /&gt;
&lt;br /&gt;
== Connaissances nécessaires ==&lt;br /&gt;
Ce workshop s'addresse principalement aux débutants. Il est cependant recommandé de savoir :&lt;br /&gt;
* utiliser les commandes de base du shell Linux (cd, ls, rm...).&lt;br /&gt;
* d'être familier avec la configuration d'une carte Wi-Fi sous Linux&lt;br /&gt;
&lt;br /&gt;
== Inscrits/Attendees ==&lt;br /&gt;
* Animator : [[User:Florian|Florian]]&lt;br /&gt;
* Animator : [[User:Nico|Nico]]&lt;br /&gt;
* [[User:Phil|Philpraxis]]&lt;br /&gt;
* [[User:Loloster|Loloster]]&lt;br /&gt;
* [[User:Kiniou|Kiniou]]&lt;br /&gt;
* [[User:Grospouf93|Grospouf93]]&lt;br /&gt;
* [[User:Jch|Jch]]&lt;br /&gt;
&lt;br /&gt;
Merci de vous inscrire ici afin d'avoir une estimation du nombre de participants. Vous pouvez aussi envoyer un mail à florian at openwrt.org et nico at openwrt.org&lt;br /&gt;
&lt;br /&gt;
== Recommandé ==&lt;br /&gt;
* Amener votre laptop&lt;br /&gt;
* Installer les outils de de développement preréquis par OpenWrt (build-essential, flex, bison ...)&lt;br /&gt;
* Votre équipement à flasher&lt;br /&gt;
* Des adaptateurs USB série et des convertisseurs TTL (3.3V - 12V)&lt;br /&gt;
&lt;br /&gt;
== Equipements ==&lt;br /&gt;
Dispo :&lt;br /&gt;
* 3 cartes Compex WP54G-WRT (3 Florian)&lt;br /&gt;
* 3 Linksys WRT54GS (2 Florian + 1 Nico)&lt;br /&gt;
* 1 Linksys WRT54G (1 Nico)&lt;br /&gt;
* 1 Atmel AVR32 ATNGW100 (1 Nico)&lt;br /&gt;
* 1 Fonera2 (1 Nico)&lt;br /&gt;
* 1 Ubiquiti LiteStation2 (1 Nico)&lt;br /&gt;
* 1 Belkin F5D8231-4 v2 (1 Nico)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wanted :&lt;br /&gt;
* Vidéoprojecteur.&lt;br /&gt;
&lt;br /&gt;
[[Category:Workshop]]&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	<entry>
		<id>https://www.tmplab.org/wiki/index.php?title=OpenWrt_:_une_introduction&amp;diff=1246</id>
		<title>OpenWrt : une introduction</title>
		<link rel="alternate" type="text/html" href="https://www.tmplab.org/wiki/index.php?title=OpenWrt_:_une_introduction&amp;diff=1246"/>
				<updated>2009-04-03T23:24:27Z</updated>
		
		<summary type="html">&lt;p&gt;Jch: /* Inscrits/Attendees */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Workshop OpenWrt ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Openwrt-logo.png|right]] Samedi 4 avril 2009 au /tmp/lab ; de 14h30 à 20h30.&lt;br /&gt;
&lt;br /&gt;
Voici les différents points qui seront abordés:&lt;br /&gt;
Sur OpenWrt :&lt;br /&gt;
&lt;br /&gt;
* de comprendre la structure générale d'OpenWrt&lt;br /&gt;
* de construire votre propre image du firmware pour votre cible matérielle&lt;br /&gt;
* de porter un logiciel de votre choix et de le tester&lt;br /&gt;
* de le flasher depuis le firmware original ou depuis une ancienne version &lt;br /&gt;
d'OpenWrt&lt;br /&gt;
&lt;br /&gt;
Sur le Wi-Fi :&lt;br /&gt;
&lt;br /&gt;
* de faire un petit rappel sur les différents modes de fonctionnement &lt;br /&gt;
possibles : Master, Managed, Mesh, Ad-hoc, Monitor&lt;br /&gt;
* de tester ces différents modes de fonctionnement (suivant le matériel)  et &lt;br /&gt;
les configurations correspondantes dans OpenWrt&lt;br /&gt;
&lt;br /&gt;
Sur les protocoles de routage :&lt;br /&gt;
&lt;br /&gt;
* quelques réseaux de tests simples utilisants OLSR, 802.11s et Babel.&lt;br /&gt;
&lt;br /&gt;
== Connaissances nécessaires ==&lt;br /&gt;
Ce workshop s'addresse principalement aux débutants. Il est cependant recommandé de savoir :&lt;br /&gt;
* utiliser les commandes de base du shell Linux (cd, ls, rm...).&lt;br /&gt;
* d'être familier avec la configuration d'une carte Wi-Fi sous Linux&lt;br /&gt;
&lt;br /&gt;
== Inscrits/Attendees ==&lt;br /&gt;
* Animator : [[User:Florian|Florian]]&lt;br /&gt;
* Animator : [[User:Nico|Nico]]&lt;br /&gt;
* [[User:Phil|Philpraxis]]&lt;br /&gt;
* [[User:Loloster|Loloster]]&lt;br /&gt;
* [[User:Kiniou|Kiniou]]&lt;br /&gt;
* [[User:Grospouf93|Grospouf93]]&lt;br /&gt;
* [[User::Jch]]&lt;br /&gt;
&lt;br /&gt;
Merci de vous inscrire ici afin d'avoir une estimation du nombre de participants. Vous pouvez aussi envoyer un mail à florian at openwrt.org et nico at openwrt.org&lt;br /&gt;
&lt;br /&gt;
== Recommandé ==&lt;br /&gt;
* Amener votre laptop&lt;br /&gt;
* Installer les outils de de développement preréquis par OpenWrt (build-essential, flex, bison ...)&lt;br /&gt;
* Votre équipement à flasher&lt;br /&gt;
* Des adaptateurs USB série et des convertisseurs TTL (3.3V - 12V)&lt;br /&gt;
&lt;br /&gt;
== Equipements ==&lt;br /&gt;
Dispo :&lt;br /&gt;
* 3 cartes Compex WP54G-WRT (3 Florian)&lt;br /&gt;
* 3 Linksys WRT54GS (2 Florian + 1 Nico)&lt;br /&gt;
* 1 Linksys WRT54G (1 Nico)&lt;br /&gt;
* 1 Atmel AVR32 ATNGW100 (1 Nico)&lt;br /&gt;
* 1 Fonera2 (1 Nico)&lt;br /&gt;
* 1 Ubiquiti LiteStation2 (1 Nico)&lt;br /&gt;
* 1 Belkin F5D8231-4 v2 (1 Nico)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wanted :&lt;br /&gt;
* Vidéoprojecteur.&lt;br /&gt;
&lt;br /&gt;
[[Category:Workshop]]&lt;/div&gt;</summary>
		<author><name>Jch</name></author>	</entry>

	</feed>