+ <item>
+ <title>Dugnadsnett for alle stiller på Oslo Maker Faire i januar 2014</title>
+ <link>http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle_stiller_p__Oslo_Maker_Faire_i_januar_2014.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle_stiller_p__Oslo_Maker_Faire_i_januar_2014.html</guid>
+ <pubDate>Tue, 10 Dec 2013 19:20:00 +0100</pubDate>
+ <description><p>Helga 18. og 19. januar 2014 arrangeres
+<a href="http://makerfaireoslo.no/no/program/dugnadsnett">Oslo Maker
+Faire</a>, og <a href="http://www.dugnadsnett.no/">Dugnadsnett for
+alle</a> har fått plass! Planen er å ha et bord med en plakat der vi
+forteller om hva Dugnadsnett for alle er for noe, og et lite verksted
+der vi hjelper folk som er interessert i å få opp sin egen mesh-node.
+Jeg gleder meg til å se hvordan prosjektet blir mottatt der.</p>
+
+<p>Målet med dugnadsnett for alle i Oslo er å få på plass et datanett
+for kommunikasjon ved hjelp av radio-repeaterstasjoner (kalt
+mesh-noder) som gjør at en kan direkte kommunisere med slekt, venner
+og bekjente i Oslo via andre som deltar i dugnadsnettet, samt gjøre
+det mulig komme ut på internett via dugnadsnettet. Første delmål er å
+kunne sende SMS-meldinger vha. IP-telefoni løsningen
+<a href="http://www.servalproject.org/">Serval project</a> mellom
+deltagerne i Dugnadsnett for alle i Oslo. Formålet er å ta tilbake
+kontrollen over egen nett-infrastruktur og gjøre det dyrere å bedrive
+massiv innsamling av informasjon om borgernes bruk av datanett.</p>
+
+<p>Høres dette interessant ut? Bli med på prosjektet, fortell oss
+hvor du kunne tenke deg å sette opp en radio-repeater (slik at folk i
+nærheten kan finne hverandre ved hjelp av
+<a href="http://flynor.net/mesh/mesh.php">kartet over planlagte og
+eksisterende radio-repeatere</A>), bli med på epostlisten
+<a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
+(at) nuug.no</a> og stikk innom
+<a href="irc://irc.freenode.net/#dugnadsnett.no">IRC-kanalen
+#dugnadsnett.no</a>. Så langt er det planlagt over 40
+radio-repeatere, med VPN-forbindelser via Internet for å la de delene
+av nettet som ikke når hverandre via radio kunne snakke med hverandre
+likevel.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Dugnadsnett for alle, a wireless community network in Oslo, take shape</title>
+ <link>http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle__a_wireless_community_network_in_Oslo__take_shape.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle__a_wireless_community_network_in_Oslo__take_shape.html</guid>
+ <pubDate>Sat, 30 Nov 2013 10:10:00 +0100</pubDate>
+ <description><p>If you want the ability to electronically communicate directly with
+your neighbors and friends using a network controlled by your peers in
+stead of centrally controlled by a few corporations, or would like to
+experiment with interesting network technology, the
+<a href="http://www.dugnadsnett.no/">Dugnasnett for alle i Oslo</a>
+might be project for you. 39 mesh nodes are currently being planned,
+in the freshly started initiative from NUUG and Hackeriet to create a
+wireless community network. The work is inspired by
+<a href="http://freifunk.net/">Freifunk</a>,
+<a href="http://www.awmn.net/">Athens Wireless Metropolitan
+Network</a>, <a href="http://en.wikipedia.org/wiki/Roofnet">Roofnet</a>
+and other successful mesh networks around the globe. Two days ago we
+held a workshop to try to get people started on setting up their own
+mesh node, and there we decided to create a new mailing list
+<a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
+(at) nuug.no</a> and IRC channel
+<a href="irc://irc.freenode.net/#dugnadsnett.no">#dugnadsnett.no</a> to
+coordinate the work. See also the NUUG blog post
+<a href="http://www.nuug.no/news/E_postliste_og_IRC_kanal_for_Dugnadsnett_for_alle_i_Oslo.shtml">announcing
+the mailing list and IRC channel</a>.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Lets make a wireless community network in Oslo!</title>
+ <link>http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html</guid>
+ <pubDate>Wed, 13 Nov 2013 21:00:00 +0100</pubDate>
+ <description><p>Today NUUG and Hackeriet announced
+<a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
+plans to join forces and create a wireless community network in
+Oslo</a>. The workshop to help people get started will take place
+Thursday 2013-11-28, but we already are collecting the geolocation of
+people joining forces to make this happen. We have
+<a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
+locations plotted on the map</a>, but we will need more before we have
+a connected mesh spread across Oslo. If this sound interesting to
+you, please join us at the workshop. If you are too impatient to wait
+15 days, please join us on the IRC channel
+<a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
+right away. :)</p>
+</description>
+ </item>
+
+ <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><p>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
+<a href="http://www.openwrt.org/">OpenWrt</a>.</p>
+
+<p>I started by following the instructions on the OpenWRT wiki for
+<a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
+and downloaded
+<a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
+recommended firmware image</a>
+(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.</p>
+
+<p>I started off by reading the instructions from
+<a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
+Africa</a>, which had quite a lot of useful information, but
+eventually I followed the recipe from the Open Mesh wiki for
+<a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
+batman-adv on OpenWrt</a>. A small snag was the fact that the
+<tt>opkg install kmod-batman-adv</tt> 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
+<a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> 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.</p>
+
+<p>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:</p>
+
+<p><tt>/etc/config/network</tt></p>
+
+<pre>
+
+config interface 'loopback'
+ option ifname 'lo'
+ option proto 'static'
+ option ipaddr '127.0.0.1'
+ option netmask '255.0.0.0'
+
+config globals 'globals'
+ option ula_prefix 'fdbf:4c12:3fed::/48'
+
+config interface 'lan'
+ option ifname 'eth0'
+ option type 'bridge'
+ option proto 'dhcp'
+ option ipaddr '192.168.1.1'
+ option netmask '255.255.255.0'
+ option hostname 'tl-mr3040'
+ option ip6assign '60'
+
+config interface 'mesh'
+ option ifname 'adhoc0'
+ option mtu '1528'
+ option proto 'batadv'
+ option mesh 'bat0'
+</pre>
+
+<p><tt>/etc/config/wireless</tt></p>
+<pre>
+
+config wifi-device 'radio0'
+ option type 'mac80211'
+ option channel '11'
+ option hwmode '11ng'
+ option path 'platform/ar933x_wmac'
+ option htmode 'HT20'
+ list ht_capab 'SHORT-GI-20'
+ list ht_capab 'SHORT-GI-40'
+ list ht_capab 'RX-STBC1'
+ list ht_capab 'DSSS_CCK-40'
+ option disabled '0'
+
+config wifi-iface 'wmesh'
+ option device 'radio0'
+ option ifname 'adhoc0'
+ option network 'mesh'
+ option encryption 'none'
+ option mode 'adhoc'
+ option bssid '02:BA:00:00:00:01'
+ option ssid 'meshfx@hackeriet'
+</pre>
+<p><tt>/etc/config/batman-adv</tt></p>
+<pre>
+
+config 'mesh' 'bat0'
+ option interfaces 'adhoc0'
+ option 'aggregated_ogms'
+ option 'ap_isolation'
+ option 'bonding'
+ option 'fragmentation'
+ option 'gw_bandwidth'
+ option 'gw_mode'
+ option 'gw_sel_class'
+ option 'log_level'
+ option 'orig_interval'
+ option 'vis_mode'
+ option 'bridge_loop_avoidance'
+ option 'distributed_arp_table'
+ option 'network_coding'
+ option 'hop_penalty'
+
+# yet another batX instance
+# config 'mesh' 'bat5'
+# option 'interfaces' 'second_mesh'
+</pre>
+
+<p>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.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
+ <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
+ <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
+ <description><p>The
+<a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a>
+program is a a very nice system to create virtual machine images. It
+create a image file, add a partition table, mount it and run
+debootstrap in the mounted directory to create a Debian system on a
+stick. Yesterday, I decided to try to teach it how to make images for
+<a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part
+of a plan to simplify the build system for
+<a href="https://wiki.debian.org/FreedomBox">the FreedomBox
+project</a>. The FreedomBox project already uses vmdebootstrap for
+the virtualbox images, but its current build system made multistrap
+based system for Dreamplug images, and it is lacking support for
+Raspberry Pi.</p>
+
+<p>Armed with the knowledge on how to build "foreign" (aka non-native
+architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
+code and adjusted it to be able to build armel images on my amd64
+Debian laptop. I ended up giving vmdebootstrap five new options,
+allowing me to replicate the image creation process I use to make
+<a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
+Jessie based mesh node images for the Raspberry Pi</a>. First, the
+<tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
+call debootstrap with --foreign and to copy the handler into the
+generated chroot before running the second stage. This allow
+vmdebootstrap to create armel images on an amd64 host. Next I added
+two new options <tt>--bootsize size</tt> and <tt>--boottype
+fstype</tt> to teach it to create a separate /boot/ partition with the
+given file system type, allowing me to create an image with a vfat
+partition for the /boot/ stuff. I also added a <tt>--variant
+variant</tt> option to allow me to create smaller images without the
+Debian base system packages installed. Finally, I added an option
+<tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux
+as a boot loader. It is not needed on the Raspberry Pi and probably
+most other non-x86 architectures. The changes were accepted by the
+upstream author of vmdebootstrap yesterday and today, and is now
+available from
+<a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
+upstream project page</a>.</p>
+
+<p>To use it to build a Raspberry Pi image using Debian Jessie, first
+create a small script (the customize script) to add the non-free
+binary blob needed to boot the Raspberry Pi and the APT source
+list:</p>
+
+<p><pre>
+#!/bin/sh
+set -e # Exit on first error
+rootdir="$1"
+cd "$rootdir"
+cat &lt;&lt;EOF > etc/apt/sources.list
+deb http://http.debian.net/debian/ jessie main contrib non-free
+EOF
+# Install non-free binary blob needed to boot Raspberry Pi. This
+# install a kernel somewhere too.
+wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
+ -O $rootdir/usr/bin/rpi-update
+chmod a+x $rootdir/usr/bin/rpi-update
+mkdir -p $rootdir/lib/modules
+touch $rootdir/boot/start.elf
+chroot $rootdir rpi-update
+</pre></p>
+
+<p>Next, fetch the latest vmdebootstrap script and call it like this
+to build the image:</p>
+
+<pre>
+sudo ./vmdebootstrap \
+ --variant minbase \
+ --arch armel \
+ --distribution jessie \
+ --mirror http://http.debian.net/debian \
+ --image test.img \
+ --size 600M \
+ --bootsize 64M \
+ --boottype vfat \
+ --log-level debug \
+ --verbose \
+ --no-kernel \
+ --no-extlinux \
+ --root-password raspberry \
+ --hostname raspberrypi \
+ --foreign /usr/bin/qemu-arm-static \
+ --customize `pwd`/customize \
+ --package netbase \
+ --package git-core \
+ --package binutils \
+ --package ca-certificates \
+ --package wget \
+ --package kmod
+</pre></p>
+
+<p>The list of packages being installed are the ones needed by
+rpi-update to make the image bootable on the Raspberry Pi, with the
+exception of netbase, which is needed by debootstrap to find
+/etc/hosts with the minbase variant. I really wish there was a way to
+set up an Raspberry Pi using only packages in the Debian archive, but
+that is not possible as far as I know, because it boots from the GPU
+using a non-free binary blob.</p>
+
+<p>The build host need debootstrap, kpartx and qemu-user-static and
+probably a few others installed. I have not checked the complete
+build dependency list.</p>
+
+<p>The resulting image will not use the hardware floating point unit
+on the Raspberry PI, because the armel architecture in Debian is not
+optimized for that use. So the images created will be a bit slower
+than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p>
+</description>
+ </item>
+
projects / homepage.git / blobdiff