Generated.

[homepage.git] / blog / data / 2013-10-11-mesh-network-oslo.txt

diff --git a/blog/data/2013-10-11-mesh-network-oslo.txt b/blog/data/2013-10-11-mesh-network-oslo.txt
index 81572467ef11b44518c163fd4843a81299353a2b..41d5283875dfe1940a6330aa6d7a480f005e2c1c 100644 (file)
--- a/blog/data/2013-10-11-mesh-network-oslo.txt
+++ b/blog/data/2013-10-11-mesh-network-oslo.txt
@@ -1,5 +1,5 @@
 Title: Oslo community mesh network - with NUUG and Hackeriet at Hausmania
-Tags: english, nuug, freedombox
+Tags: english, nuug, freedombox, mesh network
 Date: 2013-10-11 14:10
 
 <p>Wireless mesh networks are self organising and self healing
@@ -57,7 +57,7 @@ There are heaps of different protocols, and I am still struggling to
 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
-completely different setup, and thus this have decided to focus on
+completely different setup, and thus I have decided to focus on
 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
@@ -75,7 +75,7 @@ packets across mesh networks, and OLSR, B.A.T.M.A.N. and
 B.A.T.M.A.N. advanced are protocols used by several free software
 based community mesh networks.</p>
 
-</p>The batman-adv protocol is a bit special, as it provide layer 2
+<p>The batman-adv protocol is a bit special, as it provide layer 2
 (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
@@ -85,13 +85,13 @@ least since Debian Wheezy, and it is fairly easy to set up.  A
 introduction</a> is available from the Open Mesh project.  These are
 the key settings needed to join the Oslo meshfx network:</p>
 
-<table>
+<p><table>
 <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>
-</table>
+</table></p>
 
 <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
@@ -125,3 +125,9 @@ commercial companies, even though Telenor discovered that it was hard
 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>