figure out which one would be "best" for some definitions of best, but
given that the community mesh group in Oslo is so small, I believe it
is best to hook up with the existing one instead of trying to create a
figure out which one would be "best" for some definitions of best, but
given that the community mesh group in Oslo is so small, I believe it
is best to hook up with the existing one instead of trying to create a
batman-adv for now. It sure help me to know that the very cool
<a href="http://www.servalproject.org/">Serval project in Australia</a>
is using batman-adv as their meshing technology when it create a self
batman-adv for now. It sure help me to know that the very cool
<a href="http://www.servalproject.org/">Serval project in Australia</a>
is using batman-adv as their meshing technology when it create a self
(as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
network. One way to think about it is that it provide a mesh based
vlan you can bridge to or handle like any other vlan connected to your
(as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
network. One way to think about it is that it provide a mesh based
vlan you can bridge to or handle like any other vlan connected to your
introduction</a> is available from the Open Mesh project. These are
the key settings needed to join the Oslo meshfx network:</p>
introduction</a> is available from the Open Mesh project. These are
the key settings needed to join the Oslo meshfx network:</p>
<tr><th>Setting</th><th>Value</th></tr>
<tr><td>Protocol / kernel module</td><td>batman-adv</td></tr>
<tr><td>ESSID</td><td>meshfx@hackeriet</td></tr>
<td>Channel / Frequency</td><td>11 / 2462</td></tr>
<td>Cell ID</td><td>02:BA:00:00:00:01</td>
<tr><th>Setting</th><th>Value</th></tr>
<tr><td>Protocol / kernel module</td><td>batman-adv</td></tr>
<tr><td>ESSID</td><td>meshfx@hackeriet</td></tr>
<td>Channel / Frequency</td><td>11 / 2462</td></tr>
<td>Cell ID</td><td>02:BA:00:00:00:01</td>
<p>The reason for setting ad-hoc wifi Cell ID is to work around bugs
in firmware used in wifi card and wifi drivers. (See a nice post from
<p>The reason for setting ad-hoc wifi Cell ID is to work around bugs
in firmware used in wifi card and wifi drivers. (See a nice post from
to figure out a good business plan for mesh networking and as far as I
know have closed down the experiment. Perhaps Telenor or others would
be interested in a cooperation?</p>
to figure out a good business plan for mesh networking and as far as I
know have closed down the experiment. Perhaps Telenor or others would
be interested in a cooperation?</p>
+
+<p><strong>Update 2013-10-12</strong>: I was just
+<a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2013-October/005900.html">told
+by the Serval project developers</a> that they no longer use
+batman-adv (but are compatible with it), but their own crypto based
+mesh system.</p>