Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 09c9ccd44f97120b98d39f054a36a867fa8bc925..fa3eea5ed675dba021d0258d3656121c939d0482 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,132 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <title>Running TP-Link MR3040 as a batman-adv mesh node using openwrt</title>
+               <link>http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html</guid>
+                <pubDate>Sun, 10 Nov 2013 23:00:00 +0100</pubDate>
+               <description>&lt;p&gt;Continuing my research into mesh networking, I was recommended to
+use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
+bought arrived on Friday.  Here are my notes on how to set up the
+MR3040 as a mesh node using
+&lt;a href=&quot;http://www.openwrt.org/&quot;&gt;OpenWrt&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;I started by following the instructions on the OpenWRT wiki for
+&lt;a href=&quot;http://wiki.openwrt.org/toh/tp-link/tl-mr3040&quot;&gt;TL-MR3040&lt;/a&gt;,
+and downloaded
+&lt;a href=&quot;http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin&quot;&gt;the
+recommended firmware image&lt;/a&gt;
+(openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
+uploaded it into the original web interface.  The flashing went fine,
+and the machine was available via telnet on the ethernet port.  After
+logging in and setting the root password, ssh was available and I
+could start to set it up as a batman-adv mesh node.&lt;/p&gt;
+
+&lt;p&gt;I started off by reading the instructions from
+&lt;a href=&quot;http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine&#39;s_Research&quot;&gt;Wireless
+Africa&lt;/a&gt;, which had quite a lot of useful information, but
+eventually I followed the recipe from the Open Mesh wiki for
+&lt;a href=&quot;http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config&quot;&gt;using
+batman-adv on OpenWrt&lt;/a&gt;.  A small snag was the fact that the
+&lt;tt&gt;opkg install kmod-batman-adv&lt;/tt&gt; command did not work as it
+should.  The batman-adv kernel module would fail to load because its
+dependency crc16 was not already loaded.  I
+&lt;a href=&quot;https://dev.openwrt.org/ticket/14452&quot;&gt;reported the bug&lt;/a&gt; to
+the openwrt project and hope it will be fixed soon.  But the problem
+only seem to affect initial testing of batman-adv, as configuration
+seem to work when booting from scratch.&lt;/p&gt;
+
+&lt;p&gt;The setup is done using files in /etc/config/.  I did not bridge
+the Ethernet and mesh interfaces this time, to be able to hook up the
+box on my local network and log into it for configuration updates.
+The following files were changed and look like this after modifying
+them:&lt;/p&gt;
+
+&lt;p&gt;&lt;tt&gt;/etc/config/network&lt;/tt&gt;&lt;/p&gt;
+
+&lt;pre&gt;
+
+config interface &#39;loopback&#39;
+        option ifname &#39;lo&#39;
+        option proto &#39;static&#39;
+        option ipaddr &#39;127.0.0.1&#39;
+        option netmask &#39;255.0.0.0&#39;
+
+config globals &#39;globals&#39;
+        option ula_prefix &#39;fdbf:4c12:3fed::/48&#39;
+
+config interface &#39;lan&#39;
+        option ifname &#39;eth0&#39;
+        option type &#39;bridge&#39;
+        option proto &#39;dhcp&#39;
+        option ipaddr &#39;192.168.1.1&#39;
+        option netmask &#39;255.255.255.0&#39;
+        option hostname &#39;tl-mr3040&#39;
+        option ip6assign &#39;60&#39;
+
+config interface &#39;mesh&#39;
+        option ifname &#39;adhoc0&#39;
+        option mtu &#39;1528&#39;
+        option proto &#39;batadv&#39;
+        option mesh &#39;bat0&#39;
+&lt;/pre&gt;
+
+&lt;p&gt;&lt;tt&gt;/etc/config/wireless&lt;/tt&gt;&lt;/p&gt;
+&lt;pre&gt;
+
+config wifi-device &#39;radio0&#39;
+        option type &#39;mac80211&#39;
+        option channel &#39;11&#39;
+        option hwmode &#39;11ng&#39;
+        option path &#39;platform/ar933x_wmac&#39;
+        option htmode &#39;HT20&#39;
+        list ht_capab &#39;SHORT-GI-20&#39;
+        list ht_capab &#39;SHORT-GI-40&#39;
+        list ht_capab &#39;RX-STBC1&#39;
+        list ht_capab &#39;DSSS_CCK-40&#39;
+        option disabled &#39;0&#39;
+
+config wifi-iface &#39;wmesh&#39;
+        option device &#39;radio0&#39;
+        option ifname &#39;adhoc0&#39;
+        option network &#39;mesh&#39;
+        option encryption &#39;none&#39;
+        option mode &#39;adhoc&#39;
+        option bssid &#39;02:BA:00:00:00:01&#39;
+        option ssid &#39;meshfx@hackeriet&#39;
+&lt;/pre&gt;
+&lt;p&gt;&lt;tt&gt;/etc/config/batman-adv&lt;/tt&gt;&lt;/p&gt;
+&lt;pre&gt;
+
+config &#39;mesh&#39; &#39;bat0&#39;
+        option interfaces &#39;adhoc0&#39;
+        option &#39;aggregated_ogms&#39;
+        option &#39;ap_isolation&#39;
+        option &#39;bonding&#39;
+        option &#39;fragmentation&#39;
+        option &#39;gw_bandwidth&#39;
+        option &#39;gw_mode&#39;
+        option &#39;gw_sel_class&#39;
+        option &#39;log_level&#39;
+        option &#39;orig_interval&#39;
+        option &#39;vis_mode&#39;
+        option &#39;bridge_loop_avoidance&#39;
+        option &#39;distributed_arp_table&#39;
+        option &#39;network_coding&#39;
+        option &#39;hop_penalty&#39;
+
+# yet another batX instance
+# config &#39;mesh&#39; &#39;bat5&#39;
+#       option &#39;interfaces&#39; &#39;second_mesh&#39;
+&lt;/pre&gt;
+
+&lt;p&gt;The mesh node is now operational.  I have yet to test its range,
+but I hope it is good.  I have not yet tested the TP-Link 3600 box
+still wrapped up in plastic.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Debian init.d boot script example for rsyslog</title>
                <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
        <item>
                <title>Debian init.d boot script example for rsyslog</title>
                <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>


@@ -695,23 +821,5 @@ me know. :)&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Finally, Debian Edu Wheezy is released today!</title>
-               <link>http://people.skolelinux.org/pere/blog/Finally__Debian_Edu_Wheezy_is_released_today_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Finally__Debian_Edu_Wheezy_is_released_today_.html</guid>
-                <pubDate>Sun, 29 Sep 2013 10:20:00 +0200</pubDate>
-               <description>&lt;p&gt;A few hours ago, the announcement for the first stable release of
-Debian Edu Wheezy went out from the Debian publicity team.  The
-complete announcement text can be found at
-&lt;a href=&quot;http://www.debian.org/News/2013/20130928&quot;&gt;the Debian News
-section&lt;/a&gt;, translated to several languages.  Please check it out.&lt;/p&gt;
-
-&lt;p&gt;There is one minor known problem that we will fix very soon.  One
-can not install a amd64 Thin Client Server using PXE, as the /var/
-partition is too small.  A workaround is to extend the partition (use
-lvresize + resize2fs in tty 2 while installing).&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>