From eaf2e420e0afb77d255fecfdbcc9d939686a1ff6 Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen
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 @@ -105,13 +105,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/archive/2013/10/10.rss b/blog/archive/2013/10/10.rss index e7f49f6498..a64e779fe3 100644 --- a/blog/archive/2013/10/10.rss +++ b/blog/archive/2013/10/10.rss @@ -84,7 +84,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 @@ -94,13 +94,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 diff --git a/blog/archive/2013/10/index.html b/blog/archive/2013/10/index.html index 572a797649..70a329d973 100644 --- a/blog/archive/2013/10/index.html +++ b/blog/archive/2013/10/index.html @@ -102,7 +102,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.
-The batman-adv protocol is a bit special, as it provide layer 2 +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 @@ -112,13 +112,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/index.html b/blog/index.html index 2028bfd7c8..e1868facf1 100644 --- a/blog/index.html +++ b/blog/index.html @@ -95,7 +95,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.
-The batman-adv protocol is a bit special, as it provide layer 2 +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 @@ -105,13 +105,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/index.rss b/blog/index.rss index 8b48b5c329..802d6c2f07 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -84,7 +84,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 @@ -94,13 +94,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 diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index b5e1bb8647..90a1d45a07 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -84,7 +84,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 @@ -94,13 +94,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 diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 744495caa0..e2f5cee4ca 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -101,7 +101,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.
-The batman-adv protocol is a bit special, as it provide layer 2 +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 @@ -111,13 +111,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/tags/freedombox/freedombox.rss b/blog/tags/freedombox/freedombox.rss index 5ca3fa5981..1294554835 100644 --- a/blog/tags/freedombox/freedombox.rss +++ b/blog/tags/freedombox/freedombox.rss @@ -84,7 +84,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 @@ -94,13 +94,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 diff --git a/blog/tags/freedombox/index.html b/blog/tags/freedombox/index.html index 29a32b4310..8f3faefb7d 100644 --- a/blog/tags/freedombox/index.html +++ b/blog/tags/freedombox/index.html @@ -101,7 +101,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.
-The batman-adv protocol is a bit special, as it provide layer 2 +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 @@ -111,13 +111,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/tags/nuug/index.html b/blog/tags/nuug/index.html index 17155da89d..c765abdbf1 100644 --- a/blog/tags/nuug/index.html +++ b/blog/tags/nuug/index.html @@ -101,7 +101,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.
-The batman-adv protocol is a bit special, as it provide layer 2 +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 @@ -111,13 +111,13 @@ least since Debian Wheezy, and it is fairly easy to set up. A introduction is available from the Open Mesh project. These are the key settings needed to join the Oslo meshfx network:
-Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | Cell ID | 02:BA:00:00:00:01 | -
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 diff --git a/blog/tags/nuug/nuug.rss b/blog/tags/nuug/nuug.rss index 3b1a6ff768..df00db7113 100644 --- a/blog/tags/nuug/nuug.rss +++ b/blog/tags/nuug/nuug.rss @@ -84,7 +84,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 @@ -94,13 +94,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 diff --git a/blog/tags/offentlig innsyn/index.html b/blog/tags/offentlig innsyn/index.html index 242566a2d6..81dc253aec 100644 --- a/blog/tags/offentlig innsyn/index.html +++ b/blog/tags/offentlig innsyn/index.html @@ -1037,7 +1037,7 @@ til å levere hver uke. Har ikke undersøkt noen av de andre.