blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html">Lets make a wireless community network in Oslo!</a></div>
  24       <div class="date">13th November 2013</div>
  25       <div class="body"><p>Today NUUG and Hackeriet announced
  26 <a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
  27 plans to join forces and create a wireless community network in
  28 Oslo</a>.  The workshop to help people get started will take place
  29 Thursday 2013-11-28, but we already are collecting the geolocation of
  30 people joining forces to make this happen.  We have
  31 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
  32 locations plotted on the map</a>, but we will need more before we have
  33 a connected mesh spread across Oslo.  If this sound interesting to
  34 you, please join us at the workshop.  If you are too impatient to wait
  35 15 days, please join us on the IRC channel
  36 <a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
  37 right away. :)</p>
  38 </div>
  39       <div class="tags">
  40
  41
  42         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
  43
  44
  45       </div>
  46     </div>
  47     <div class="padding"></div>
  48
  49     <div class="entry">
  50       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html">Running TP-Link MR3040 as a batman-adv mesh node using openwrt</a></div>
  51       <div class="date">10th November 2013</div>
  52       <div class="body"><p>Continuing my research into mesh networking, I was recommended to
  53 use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
  54 bought arrived on Friday.  Here are my notes on how to set up the
  55 MR3040 as a mesh node using
  56 <a href="http://www.openwrt.org/">OpenWrt</a>.</p>
  57
  58 <p>I started by following the instructions on the OpenWRT wiki for
  59 <a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
  60 and downloaded
  61 <a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
  62 recommended firmware image</a>
  63 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
  64 uploaded it into the original web interface.  The flashing went fine,
  65 and the machine was available via telnet on the ethernet port.  After
  66 logging in and setting the root password, ssh was available and I
  67 could start to set it up as a batman-adv mesh node.</p>
  68
  69 <p>I started off by reading the instructions from
  70 <a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
  71 Africa</a>, which had quite a lot of useful information, but
  72 eventually I followed the recipe from the Open Mesh wiki for
  73 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
  74 batman-adv on OpenWrt</a>.  A small snag was the fact that the
  75 <tt>opkg install kmod-batman-adv</tt> command did not work as it
  76 should.  The batman-adv kernel module would fail to load because its
  77 dependency crc16 was not already loaded.  I
  78 <a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> to
  79 the openwrt project and hope it will be fixed soon.  But the problem
  80 only seem to affect initial testing of batman-adv, as configuration
  81 seem to work when booting from scratch.</p>
  82
  83 <p>The setup is done using files in /etc/config/.  I did not bridge
  84 the Ethernet and mesh interfaces this time, to be able to hook up the
  85 box on my local network and log into it for configuration updates.
  86 The following files were changed and look like this after modifying
  87 them:</p>
  88
  89 <p><tt>/etc/config/network</tt></p>
  90
  91 <pre>
  92
  93 config interface 'loopback'
  94         option ifname 'lo'
  95         option proto 'static'
  96         option ipaddr '127.0.0.1'
  97         option netmask '255.0.0.0'
  98
  99 config globals 'globals'
 100         option ula_prefix 'fdbf:4c12:3fed::/48'
 101
 102 config interface 'lan'
 103         option ifname 'eth0'
 104         option type 'bridge'
 105         option proto 'dhcp'
 106         option ipaddr '192.168.1.1'
 107         option netmask '255.255.255.0'
 108         option hostname 'tl-mr3040'
 109         option ip6assign '60'
 110
 111 config interface 'mesh'
 112         option ifname 'adhoc0'
 113         option mtu '1528'
 114         option proto 'batadv'
 115         option mesh 'bat0'
 116 </pre>
 117
 118 <p><tt>/etc/config/wireless</tt></p>
 119 <pre>
 120
 121 config wifi-device 'radio0'
 122         option type 'mac80211'
 123         option channel '11'
 124         option hwmode '11ng'
 125         option path 'platform/ar933x_wmac'
 126         option htmode 'HT20'
 127         list ht_capab 'SHORT-GI-20'
 128         list ht_capab 'SHORT-GI-40'
 129         list ht_capab 'RX-STBC1'
 130         list ht_capab 'DSSS_CCK-40'
 131         option disabled '0'
 132
 133 config wifi-iface 'wmesh'
 134         option device 'radio0'
 135         option ifname 'adhoc0'
 136         option network 'mesh'
 137         option encryption 'none'
 138         option mode 'adhoc'
 139         option bssid '02:BA:00:00:00:01'
 140         option ssid 'meshfx@hackeriet'
 141 </pre>
 142 <p><tt>/etc/config/batman-adv</tt></p>
 143 <pre>
 144
 145 config 'mesh' 'bat0'
 146         option interfaces 'adhoc0'
 147         option 'aggregated_ogms'
 148         option 'ap_isolation'
 149         option 'bonding'
 150         option 'fragmentation'
 151         option 'gw_bandwidth'
 152         option 'gw_mode'
 153         option 'gw_sel_class'
 154         option 'log_level'
 155         option 'orig_interval'
 156         option 'vis_mode'
 157         option 'bridge_loop_avoidance'
 158         option 'distributed_arp_table'
 159         option 'network_coding'
 160         option 'hop_penalty'
 161
 162 # yet another batX instance
 163 # config 'mesh' 'bat5'
 164 #       option 'interfaces' 'second_mesh'
 165 </pre>
 166
 167 <p>The mesh node is now operational.  I have yet to test its range,
 168 but I hope it is good.  I have not yet tested the TP-Link 3600 box
 169 still wrapped up in plastic.</p>
 170 </div>
 171       <div class="tags">
 172
 173
 174         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 175
 176
 177       </div>
 178     </div>
 179     <div class="padding"></div>
 180
 181     <div class="entry">
 182       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html">Debian init.d boot script example for rsyslog</a></div>
 183       <div class="date"> 2nd November 2013</div>
 184       <div class="body"><p>If one of the points of switching to a new init system in Debian is
 185 <a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
 186 init.d scripts</a>, I doubt we need to switch away from sysvinit and
 187 init.d scripts at all.  Here is an example init.d script, ie a rewrite
 188 of /etc/init.d/rsyslog:</p>
 189
 190 <p><pre>
 191 #!/lib/init/init-d-script
 192 ### BEGIN INIT INFO
 193 # Provides:          rsyslog
 194 # Required-Start:    $remote_fs $time
 195 # Required-Stop:     umountnfs $time
 196 # X-Stop-After:      sendsigs
 197 # Default-Start:     2 3 4 5
 198 # Default-Stop:      0 1 6
 199 # Short-Description: enhanced syslogd
 200 # Description:       Rsyslog is an enhanced multi-threaded syslogd.
 201 #                    It is quite compatible to stock sysklogd and can be
 202 #                    used as a drop-in replacement.
 203 ### END INIT INFO
 204 DESC="enhanced syslogd"
 205 DAEMON=/usr/sbin/rsyslogd
 206 </pre></p>
 207
 208 <p>Pretty minimalistic to me... For the record, the original sysv-rc
 209 script was 137 lines, and the above is just 15 lines, most of it meta
 210 info/comments.</p>
 211
 212 <p>How to do this, you ask?  Well, one create a new script
 213 /lib/init/init-d-script looking something like this:
 214
 215 <p><pre>
 216 #!/bin/sh
 217
 218 # Define LSB log_* functions.
 219 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
 220 # and status_of_proc is working.
 221 . /lib/lsb/init-functions
 222
 223 #
 224 # Function that starts the daemon/service
 225
 226 #
 227 do_start()
 228 {
 229         # Return
 230         #   0 if daemon has been started
 231         #   1 if daemon was already running
 232         #   2 if daemon could not be started
 233         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
 234                 || return 1
 235         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
 236                 $DAEMON_ARGS \
 237                 || return 2
 238         # Add code here, if necessary, that waits for the process to be ready
 239         # to handle requests from services started subsequently which depend
 240         # on this one.  As a last resort, sleep for some time.
 241 }
 242
 243 #
 244 # Function that stops the daemon/service
 245 #
 246 do_stop()
 247 {
 248         # Return
 249         #   0 if daemon has been stopped
 250         #   1 if daemon was already stopped
 251         #   2 if daemon could not be stopped
 252         #   other if a failure occurred
 253         start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
 254         RETVAL="$?"
 255         [ "$RETVAL" = 2 ] && return 2
 256         # Wait for children to finish too if this is a daemon that forks
 257         # and if the daemon is only ever run from this initscript.
 258         # If the above conditions are not satisfied then add some other code
 259         # that waits for the process to drop all resources that could be
 260         # needed by services started subsequently.  A last resort is to
 261         # sleep for some time.
 262         start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
 263         [ "$?" = 2 ] && return 2
 264         # Many daemons don't delete their pidfiles when they exit.
 265         rm -f $PIDFILE
 266         return "$RETVAL"
 267 }
 268
 269 #
 270 # Function that sends a SIGHUP to the daemon/service
 271 #
 272 do_reload() {
 273         #
 274         # If the daemon can reload its configuration without
 275         # restarting (for example, when it is sent a SIGHUP),
 276         # then implement that here.
 277         #
 278         start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
 279         return 0
 280 }
 281
 282 SCRIPTNAME=$1
 283 scriptbasename="$(basename $1)"
 284 echo "SN: $scriptbasename"
 285 if [ "$scriptbasename" != "init-d-library" ] ; then
 286     script="$1"
 287     shift
 288     . $script
 289 else
 290     exit 0
 291 fi
 292
 293 NAME=$(basename $DAEMON)
 294 PIDFILE=/var/run/$NAME.pid
 295
 296 # Exit if the package is not installed
 297 #[ -x "$DAEMON" ] || exit 0
 298
 299 # Read configuration variable file if it is present
 300 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
 301
 302 # Load the VERBOSE setting and other rcS variables
 303 . /lib/init/vars.sh
 304
 305 case "$1" in
 306   start)
 307         [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
 308         do_start
 309         case "$?" in
 310                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 311                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 312         esac
 313         ;;
 314   stop)
 315         [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
 316         do_stop
 317         case "$?" in
 318                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 319                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 320         esac
 321         ;;
 322   status)
 323         status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
 324         ;;
 325   #reload|force-reload)
 326         #
 327         # If do_reload() is not implemented then leave this commented out
 328         # and leave 'force-reload' as an alias for 'restart'.
 329         #
 330         #log_daemon_msg "Reloading $DESC" "$NAME"
 331         #do_reload
 332         #log_end_msg $?
 333         #;;
 334   restart|force-reload)
 335         #
 336         # If the "reload" option is implemented then remove the
 337         # 'force-reload' alias
 338         #
 339         log_daemon_msg "Restarting $DESC" "$NAME"
 340         do_stop
 341         case "$?" in
 342           0|1)
 343                 do_start
 344                 case "$?" in
 345                         0) log_end_msg 0 ;;
 346                         1) log_end_msg 1 ;; # Old process is still running
 347                         *) log_end_msg 1 ;; # Failed to start
 348                 esac
 349                 ;;
 350           *)
 351                 # Failed to stop
 352                 log_end_msg 1
 353                 ;;
 354         esac
 355         ;;
 356   *)
 357         echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
 358         exit 3
 359         ;;
 360 esac
 361
 362 :
 363 </pre></p>
 364
 365 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
 366 lot.  I did not really polish the approach, so it might not always
 367 work out of the box, but you get the idea.  I did not try very hard to
 368 optimize it nor make it more robust either.</p>
 369
 370 <p>A better argument for switching init system in Debian than reducing
 371 the size of init scripts (which is a good thing to do anyway), is to
 372 get boot system that is able to handle the kernel events sensibly and
 373 robustly, and do not depend on the boot to run sequentially.  The boot
 374 and the kernel have not behaved sequentially in years.</p>
 375 </div>
 376       <div class="tags">
 377
 378
 379         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 380
 381
 382       </div>
 383     </div>
 384     <div class="padding"></div>
 385
 386     <div class="entry">
 387       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html">Browser plugin for SPICE (spice-xpi) uploaded to Debian</a></div>
 388       <div class="date"> 1st November 2013</div>
 389       <div class="body"><p><a href="http://www.spice-space.org/">The SPICE protocol</a> for
 390 remote display access is the preferred solution with oVirt and RedHat
 391 Enterprise Virtualization, and I was sad to discover the other day
 392 that the browser plugin needed to use these systems seamlessly was
 393 missing in Debian.  The <a href="http://bugs.debian.org/668284">request
 394 for a package</a> was from 2012-04-10 with no progress since
 395 2013-04-01, so I decided to wrap up a package based on the great work
 396 from Cajus Pollmeier and put it in a collab-maint maintained git
 397 repository to get a package I could use.  I would very much like
 398 others to help me maintain the package (or just take over, I do not
 399 mind), but as no-one had volunteered so far, I just uploaded it to
 400 NEW.  I hope it will be available in Debian in a few days.</p>
 401
 402 <p>The source is now available from
 403 <a href="http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary</a>.</p>
 404 </div>
 405       <div class="tags">
 406
 407
 408         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 409
 410
 411       </div>
 412     </div>
 413     <div class="padding"></div>
 414
 415     <div class="entry">
 416       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html">Teaching vmdebootstrap to create Raspberry Pi SD card images</a></div>
 417       <div class="date">27th October 2013</div>
 418       <div class="body"><p>The
 419 <a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a>
 420 program is a a very nice system to create virtual machine images.  It
 421 create a image file, add a partition table, mount it and run
 422 debootstrap in the mounted directory to create a Debian system on a
 423 stick.  Yesterday, I decided to try to teach it how to make images for
 424 <a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part
 425 of a plan to simplify the build system for
 426 <a href="https://wiki.debian.org/FreedomBox">the FreedomBox
 427 project</a>.  The FreedomBox project already uses vmdebootstrap for
 428 the virtualbox images, but its current build system made multistrap
 429 based system for Dreamplug images, and it is lacking support for
 430 Raspberry Pi.</p>
 431
 432 <p>Armed with the knowledge on how to build "foreign" (aka non-native
 433 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
 434 code and adjusted it to be able to build armel images on my amd64
 435 Debian laptop.  I ended up giving vmdebootstrap five new options,
 436 allowing me to replicate the image creation process I use to make
 437 <a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
 438 Jessie based mesh node images for the Raspberry Pi</a>.  First, the
 439 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
 440 call debootstrap with --foreign and to copy the handler into the
 441 generated chroot before running the second stage.  This allow
 442 vmdebootstrap to create armel images on an amd64 host.  Next I added
 443 two new options <tt>--bootsize size</tt> and <tt>--boottype
 444 fstype</tt> to teach it to create a separate /boot/ partition with the
 445 given file system type, allowing me to create an image with a vfat
 446 partition for the /boot/ stuff.  I also added a <tt>--variant
 447 variant</tt> option to allow me to create smaller images without the
 448 Debian base system packages installed.  Finally, I added an option
 449 <tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux
 450 as a boot loader.  It is not needed on the Raspberry Pi and probably
 451 most other non-x86 architectures.  The changes were accepted by the
 452 upstream author of vmdebootstrap yesterday and today, and is now
 453 available from
 454 <a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
 455 upstream project page</a>.</p>
 456
 457 <p>To use it to build a Raspberry Pi image using Debian Jessie, first
 458 create a small script (the customize script) to add the non-free
 459 binary blob needed to boot the Raspberry Pi and the APT source
 460 list:</p>
 461
 462 <p><pre>
 463 #!/bin/sh
 464 set -e # Exit on first error
 465 rootdir="$1"
 466 cd "$rootdir"
 467 cat &lt;&lt;EOF > etc/apt/sources.list
 468 deb http://http.debian.net/debian/ jessie main contrib non-free
 469 EOF
 470 # Install non-free binary blob needed to boot Raspberry Pi.  This
 471 # install a kernel somewhere too.
 472 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
 473     -O $rootdir/usr/bin/rpi-update
 474 chmod a+x $rootdir/usr/bin/rpi-update
 475 mkdir -p $rootdir/lib/modules
 476 touch $rootdir/boot/start.elf
 477 chroot $rootdir rpi-update
 478 </pre></p>
 479
 480 <p>Next, fetch the latest vmdebootstrap script and call it like this
 481 to build the image:</p>
 482
 483 <pre>
 484 sudo ./vmdebootstrap \
 485     --variant minbase \
 486     --arch armel \
 487     --distribution jessie \
 488     --mirror http://http.debian.net/debian \
 489     --image test.img \
 490     --size 600M \
 491     --bootsize 64M \
 492     --boottype vfat \
 493     --log-level debug \
 494     --verbose \
 495     --no-kernel \
 496     --no-extlinux \
 497     --root-password raspberry \
 498     --hostname raspberrypi \
 499     --foreign /usr/bin/qemu-arm-static \
 500     --customize `pwd`/customize \
 501     --package netbase \
 502     --package git-core \
 503     --package binutils \
 504     --package ca-certificates \
 505     --package wget \
 506     --package kmod
 507 </pre></p>
 508
 509 <p>The list of packages being installed are the ones needed by
 510 rpi-update to make the image bootable on the Raspberry Pi, with the
 511 exception of netbase, which is needed by debootstrap to find
 512 /etc/hosts with the minbase variant.  I really wish there was a way to
 513 set up an Raspberry Pi using only packages in the Debian archive, but
 514 that is not possible as far as I know, because it boots from the GPU
 515 using a non-free binary blob.</p>
 516
 517 <p>The build host need debootstrap, kpartx and qemu-user-static and
 518 probably a few others installed.  I have not checked the complete
 519 build dependency list.</p>
 520
 521 <p>The resulting image will not use the hardware floating point unit
 522 on the Raspberry PI, because the armel architecture in Debian is not
 523 optimized for that use.  So the images created will be a bit slower
 524 than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p>
 525 </div>
 526       <div class="tags">
 527
 528
 529         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>.
 530
 531
 532       </div>
 533     </div>
 534     <div class="padding"></div>
 535
 536     <div class="entry">
 537       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html">Det er jo makta som er mest sårbar ved massiv overvåkning av Internett</a></div>
 538       <div class="date">26th October 2013</div>
 539       <div class="body"><p>De siste måneders eksponering av
 540 <a href="http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den
 541 totale overvåkningen som foregår i den vestlige verden dokumenterer
 542 hvor sårbare vi er</a>.  Men det slår meg at de som er mest sårbare
 543 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
 544 selv er de mest interessante personene å lage profiler på, for å kunne
 545 påvirke dem.</p>
 546
 547 <p>For å ta et lite eksempel: Stortingets nettsted,
 548 <a href="http://www.stortinget.no/">www.stortinget.no</a> (og
 549 forsåvidt også
 550 <a href="http://data.stortinget.no/">data.stortinget.no</a>),
 551 inneholder informasjon om det som foregår på Stortinget, og jeg antar
 552 de største brukerne av informasjonen der er representanter og
 553 rådgivere på Stortinget.  Intet overraskende med det.  Det som derimot
 554 er mer skjult er at Stortingets nettsted bruker
 555 <a href="http://en.wikipedia.org/wiki/Google_Analytics">Google
 556 Analytics</a>, hvilket gjør at enhver som besøker nettsidene der også
 557 rapporterer om besøket via Internett-linjer som passerer Sverige,
 558 England og videre til USA.  Det betyr at informasjon om ethvert besøk
 559 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
 560 etterretningsvesen.  De kan dermed holde et øye med hvilke
 561 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
 562 ut, og hvilke sider rådgivere og andre på stortinget synes er
 563 interessant å besøke, når de gjør det og hvilke andre representanter
 564 som sjekker de samme sidene omtrent samtidig.  Stortingets bruk av
 565 Google Analytics gjør det dermed enkelt for utenlands etteretning å
 566 spore representantenes aktivitet og interesse.  Hvis noen av
 567 representantene bruker Google Mail eller noen andre tjenestene som
 568 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
 569 hvilke personer som bruker hvilke nettlesere og dermed knytte
 570 informasjonen opp til enkeltpersoner på Stortinget.</p>
 571
 572 <p>Og jo flere nettsteder som bruker Google Analytics, jo bedre
 573 oversikt over stortingsrepresentantenes lesevaner og interesse blir
 574 tilgjengelig for svensk, britisk og USAs etterretning.  Hva de kan
 575 bruke den informasjonen til overlater jeg til leseren å undres
 576 over.</p>
 577 </div>
 578       <div class="tags">
 579
 580
 581         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 582
 583
 584       </div>
 585     </div>
 586     <div class="padding"></div>
 587
 588     <div class="entry">
 589       <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">A Raspberry Pi based batman-adv Mesh network node</a></div>
 590       <div class="date">21st October 2013</div>
 591       <div class="body"><p>The last few days I have been experimenting with
 592 <a href="http://www.open-mesh.org/projects/batman-adv/wiki">the
 593 batman-adv mesh technology</a>.  I want to gain some experience to see
 594 if it will fit <a href="https://wiki.debian.org/FreedomBox">the
 595 Freedombox project</a>, and together with my neighbors try to build a
 596 mesh network around the park where I live.  Batman-adv is a layer 2
 597 mesh system ("ethernet" in other words), where the mesh network appear
 598 as if all the mesh clients are connected to the same switch.</p>
 599
 600 <p>My hardware of choice was the Linksys WRT54GL routers I had lying
 601 around, but I've been unable to get them working with batman-adv.  So
 602 instead, I started playing with a
 603 <a href="http://www.raspberrypi.org/">Raspberry Pi</a>, and tried to
 604 get it working as a mesh node.  My idea is to use it to create a mesh
 605 node which function as a switch port, where everything connected to
 606 the Raspberry Pi ethernet plug is connected (bridged) to the mesh
 607 network.  This allow me to hook a wifi base station like the Linksys
 608 WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow
 609 non-mesh clients to hook up to the mesh.  This in turn is useful for
 610 Android phones using <a href="http://servalproject.org/">the Serval
 611 Project</a> voip client, allowing every one around the playground to
 612 phone and message each other for free.  The reason is that Android
 613 phones do not see ad-hoc wifi networks (they are filtered away from
 614 the GUI view), and can not join the mesh without being rooted.  But if
 615 they are connected using a normal wifi base station, they can talk to
 616 every client on the local network.</p>
 617
 618 <p>To get this working, I've created a debian package
 619 <a href="https://github.com/petterreinholdtsen/meshfx-node">meshfx-node</a>
 620 and a script
 621 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node">build-rpi-mesh-node</a>
 622 to create the Raspberry Pi boot image.  I'm using Debian Jessie (and
 623 not Raspbian), to get more control over the packages available.
 624 Unfortunately a huge binary blob need to be inserted into the boot
 625 image to get it booting, but I'll ignore that for now.  Also, as
 626 Debian lack support for the CPU features available in the Raspberry
 627 Pi, the system do not use the hardware floating point unit.  I hope
 628 the routing performance isn't affected by the lack of hardware FPU
 629 support.</p>
 630
 631 <p>To create an image, run the following with a sudo enabled user
 632 after inserting the target SD card into the build machine:</p>
 633
 634 <p><pre>
 635 % wget -O build-rpi-mesh-node \
 636     https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node
 637 % sudo bash -x ./build-rpi-mesh-node > build.log 2>&1
 638 % dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=1M
 639 %
 640 </pre></p>
 641
 642 <p>Booting with the resulting SD card on a Raspberry PI with a USB
 643 wifi card inserted should give you a mesh node.  At least it does for
 644 me with a the wifi card I am using. The default mesh settings are the
 645 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
 646 <a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
 647 earlier blog post about this mesh testing</a>.</p>
 648
 649 <p>The mesh node was not horribly expensive either.  I bought
 650 everything over the counter in shops nearby.  If I had ordered online
 651 from the lowest bidder, the price should be significantly lower:</p>
 652
 653 <p><table>
 654
 655 <tr><th>Supplier</th><th>Model</th><th>NOK</th></tr>
 656 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi model B</td><td>349.90</td></tr>
 657 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi type B case</td><td>99.90</td></tr>
 658 <tr><td>Lefdal</td><td>Jensen Air:Link 25150</td><td>295.-</td></tr>
 659 <tr><td>Clas Ohlson</td><td>Kingston 16 GB SD card</td><td>199.-</td></tr>
 660 <tr><td>Total cost</td><td></td><td>943.80</td></tr>
 661
 662 </table></p>
 663
 664 <p>Now my mesh network at home consist of one laptop in the basement
 665 connected to my production network, one Raspberry Pi node on the 1th
 666 floor that can be seen by my neighbor across the park, and one
 667 play-node I use to develop the image building script.  And some times
 668 I hook up my work horse laptop to the mesh to test it.  I look forward
 669 to figuring out what kind of latency the batman-adv setup will give,
 670 and how much packet loss we will experience around the park. :)</p>
 671 </div>
 672       <div class="tags">
 673
 674
 675         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 676
 677
 678       </div>
 679     </div>
 680     <div class="padding"></div>
 681
 682     <div class="entry">
 683       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html">Perl library to control the Spykee robot moved to github</a></div>
 684       <div class="date">19th October 2013</div>
 685       <div class="body"><p>Back in 2010, I created a Perl library to talk to
 686 <a href="http://en.wikipedia.org/wiki/Spykee">the Spykee robot</a>
 687 (with two belts, wifi, USB and Linux) and made it available from my
 688 web page.  Today I concluded that it should move to a site that is
 689 easier to use to cooperate with others, and moved it to github.  If
 690 you got a Spykee robot, you might want to check out
 691 <a href="https://github.com/petterreinholdtsen/libspykee-perl">the
 692 libspykee-perl github repository</a>.</p>
 693 </div>
 694       <div class="tags">
 695
 696
 697         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>.
 698
 699
 700       </div>
 701     </div>
 702     <div class="padding"></div>
 703
 704     <div class="entry">
 705       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html">Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</a></div>
 706       <div class="date">15th October 2013</div>
 707       <div class="body"><p>The last few days I came across a few good causes that should get
 708 wider attention.  I recommend signing and donating to each one of
 709 these. :)</p>
 710
 711 <p>Via <a href="http://www.debian.org/News/weekly/2013/18/">Debian
 712 Project News for 2013-10-14</a> I came across the Outreach Program for
 713 Women program which is a Google Summer of Code like initiative to get
 714 more women involved in free software.  One debian sponsor has offered
 715 to match <a href="http://debian.ch/opw2013">any donation done to Debian
 716 earmarked</a> for this initiative.  I donated a few minutes ago, and
 717 hope you will to. :)</p>
 718
 719 <p>And the Electronic Frontier Foundation just announced plans to
 720 create <a href="https://supporters.eff.org/donate/nsa-videos">video
 721 documentaries about the excessive spying</a> on every Internet user that
 722 take place these days, and their need to fund the work.  I've already
 723 donated.  Are you next?</p>
 724
 725 <p>For my Norwegian audience, the organisation Studentenes og
 726 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
 727 statement under the heading
 728 <a href="http://saih.no/Bloggers_United/">Bloggers United for Open
 729 Access</a> for those of us asking for more focus on open access in the
 730 Norwegian government.  So far 499 signatures.  I hope you will sign it
 731 too.</p>
 732 </div>
 733       <div class="tags">
 734
 735
 736         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 737
 738
 739       </div>
 740     </div>
 741     <div class="padding"></div>
 742
 743     <div class="entry">
 744       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">Oslo community mesh network - with NUUG and Hackeriet at Hausmania</a></div>
 745       <div class="date">11th October 2013</div>
 746       <div class="body"><p>Wireless mesh networks are self organising and self healing
 747 networks that can be used to connect computers across small and large
 748 areas, depending on the radio technology used.  Normal wifi equipment
 749 can be used to create home made radio networks, and there are several
 750 successful examples like
 751 <a href="http://www.freifunk.net/">Freifunk</a> and
 752 <a href="http://www.awmn.net/">Athens Wireless Metropolitan Network</a>
 753 (see
 754 <a href="http://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region#Greece">wikipedia
 755 for a large list</a>) around the globe.  To give you an idea how it
 756 work, check out the nice overview of the Kiel Freifunk community which
 757 can be seen from their
 758 <a href="http://freifunk.in-kiel.de/ffmap/nodes.html">dynamically
 759 updated node graph and map</a>, where one can see how the mesh nodes
 760 automatically handle routing and recover from nodes disappearing.
 761 There is also a small community mesh network group in Oslo, Norway,
 762 and that is the main topic of this blog post.</p>
 763
 764 <p>I've wanted to check out mesh networks for a while now, and hoped
 765 to do it as part of my involvement with the <a
 766 href="http://www.nuug.no/">NUUG member organisation</a> community, and
 767 my recent involvement in
 768 <a href="https://wiki.debian.org/FreedomBox">the Freedombox project</a>
 769 finally lead me to give mesh networks some priority, as I suspect a
 770 Freedombox should use mesh networks to connect neighbours and family
 771 when possible, given that most communication between people are
 772 between those nearby (as shown for example by research on Facebook
 773 communication patterns).  It also allow people to communicate without
 774 any central hub to tap into for those that want to listen in on the
 775 private communication of citizens, which have become more and more
 776 important over the years.</p>
 777
 778 <p>So far I have only been able to find one group of people in Oslo
 779 working on community mesh networks, over at the hack space
 780 <a href="http://hackeriet.no/">Hackeriet</a> at Husmania.  They seem to
 781 have started with some Freifunk based effort using OLSR, called
 782 <a href="http://oslo.freifunk.net/index.php?title=Main_Page">the Oslo
 783 Freifunk project</a>, but that effort is now dead and the people
 784 behind it have moved on to a batman-adv based system called
 785 <a href="http://meshfx.org/trac">meshfx</a>.  Unfortunately the wiki
 786 site for the Oslo Freifunk project is no longer possible to update to
 787 reflect this fact, so the old project page can't be updated to point to
 788 the new project.  A while back, the people at Hackeriet invited people
 789 from the Freifunk community to Oslo to talk about mesh networks.  I
 790 came across this video where Hans Jørgen Lysglimt interview the
 791 speakers about this talk (from
 792 <a href="https://www.youtube.com/watch?v=N2Kd7CLkhSY">youtube</a>):</p>
 793
 794 <p><iframe width="420" height="315" src="https://www.youtube.com/embed/N2Kd7CLkhSY" frameborder="0" allowfullscreen></iframe></p>
 795
 796 <p>I mentioned OLSR and batman-adv, which are mesh routing protocols.
 797 There are heaps of different protocols, and I am still struggling to
 798 figure out which one would be "best" for some definitions of best, but
 799 given that the community mesh group in Oslo is so small, I believe it
 800 is best to hook up with the existing one instead of trying to create a
 801 completely different setup, and thus I have decided to focus on
 802 batman-adv for now.  It sure help me to  know that the very cool
 803 <a href="http://www.servalproject.org/">Serval project in Australia</a>
 804 is using batman-adv as their meshing technology when it create a self
 805 organizing and self healing telephony system for disaster areas and
 806 less industrialized communities.  Check out this cool video presenting
 807 that project (from
 808 <a href="https://www.youtube.com/watch?v=30qNfzJCQOA">youtube</a>):</p>
 809
 810 <p><iframe width="560" height="315" src="https://www.youtube.com/embed/30qNfzJCQOA" frameborder="0" allowfullscreen></iframe></p>
 811
 812 <p>According to the wikipedia page on
 813 <a href="http://en.wikipedia.org/wiki/Wireless_mesh_network">Wireless
 814 mesh network</a> there are around 70 competing schemes for routing
 815 packets across mesh networks, and OLSR, B.A.T.M.A.N. and
 816 B.A.T.M.A.N. advanced are protocols used by several free software
 817 based community mesh networks.</p>
 818
 819 <p>The batman-adv protocol is a bit special, as it provide layer 2
 820 (as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
 821 network.  One way to think about it is that it provide a mesh based
 822 vlan you can bridge to or handle like any other vlan connected to your
 823 computer.  The required drivers are already in the Linux kernel at
 824 least since Debian Wheezy, and it is fairly easy to set up.  A
 825 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide">good
 826 introduction</a> is available from the Open Mesh project.  These are
 827 the key settings needed to join the Oslo meshfx network:</p>
 828
 829 <p><table>
 830 <tr><th>Setting</th><th>Value</th></tr>
 831 <tr><td>Protocol / kernel module</td><td>batman-adv</td></tr>
 832 <tr><td>ESSID</td><td>meshfx@hackeriet</td></tr>
 833 <td>Channel / Frequency</td><td>11 / 2462</td></tr>
 834 <td>Cell ID</td><td>02:BA:00:00:00:01</td>
 835 </table></p>
 836
 837 <p>The reason for setting ad-hoc wifi Cell ID is to work around bugs
 838 in firmware used in wifi card and wifi drivers.  (See a nice post from
 839 VillageTelco about
 840 "<a href="http://tiebing.blogspot.no/2009/12/ad-hoc-cell-splitting-re-post-original.html">Information
 841 about cell-id splitting, stuck beacons, and failed IBSS merges!</a>
 842 for details.)  When these settings are activated and you have some
 843 other mesh node nearby, your computer will be connected to the mesh
 844 network and can communicate with any mesh node that is connected to
 845 any of the nodes in your network of nodes. :)</p>
 846
 847 <p>My initial plan was to reuse my old Linksys WRT54GL as a mesh node,
 848 but that seem to be very hard, as I have not been able to locate a
 849 firmware supporting batman-adv.  If anyone know how to use that old
 850 wifi access point with batman-adv these days, please let me know.</p>
 851
 852 <p>If you find this project interesting and want to join, please join
 853 us on IRC, either channel
 854 <a href="irc://irc.freenode.net/#oslohackerspace">#oslohackerspace</a>
 855 or <a href="irc://irc.freenode.net/#nuug">#nuug</a> on
 856 irc.freenode.net.</p>
 857
 858 <p>While investigating mesh networks in Oslo, I came across an old
 859 research paper from the university of Stavanger and Telenor Research
 860 and Innovation called
 861 <a href="http://folk.uio.no/paalee/publications/netrel-egeland-iswcs-2008.pdf">The
 862 reliability of wireless backhaul mesh networks</a> and elsewhere
 863 learned that Telenor have been experimenting with mesh networks at
 864 Grünerløkka in Oslo.  So mesh networks are also interesting for
 865 commercial companies, even though Telenor discovered that it was hard
 866 to figure out a good business plan for mesh networking and as far as I
 867 know have closed down the experiment.  Perhaps Telenor or others would
 868 be interested in a cooperation?</p>
 869
 870 <p><strong>Update 2013-10-12</strong>: I was just
 871 <a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2013-October/005900.html">told
 872 by the Serval project developers</a> that they no longer use
 873 batman-adv (but are compatible with it), but their own crypto based
 874 mesh system.</p>
 875 </div>
 876       <div class="tags">
 877
 878
 879         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 880
 881
 882       </div>
 883     </div>
 884     <div class="padding"></div>
 885
 886     <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
 887     <div id="sidebar">
 888
 889
 890
 891 <h2>Archive</h2>
 892 <ul>
 893
 894 <li>2013
 895 <ul>
 896
 897 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 898
 899 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (4)</a></li>
 918
 919 </ul></li>
 920
 921 <li>2012
 922 <ul>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 927
 928 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 947
 948 </ul></li>
 949
 950 <li>2011
 951 <ul>
 952
 953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 954
 955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 956
 957 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 958
 959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 960
 961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 962
 963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 964
 965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 976
 977 </ul></li>
 978
 979 <li>2010
 980 <ul>
 981
 982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 983
 984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 985
 986 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 987
 988 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 989
 990 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 991
 992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 993
 994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1001
1002 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1003
1004 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1005
1006 </ul></li>
1007
1008 <li>2009
1009 <ul>
1010
1011 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1012
1013 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1014
1015 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1016
1017 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1018
1019 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1020
1021 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1022
1023 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1026
1027 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1028
1029 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1030
1031 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1032
1033 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1034
1035 </ul></li>
1036
1037 <li>2008
1038 <ul>
1039
1040 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1041
1042 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1043
1044 </ul></li>
1045
1046 </ul>
1047
1048
1049
1050 <h2>Tags</h2>
1051 <ul>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (90)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (142)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (227)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (37)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (5)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (236)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (158)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (8)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
1116
1117  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1118
1119  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1120
1121  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1122
1123  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (8)</a></li>
1124
1125  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1126
1127  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1128
1129  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1130
1131  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (32)</a></li>
1132
1133  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1134
1135  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1136
1137  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (43)</a></li>
1138
1139  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1140
1141  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1142
1143  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (20)</a></li>
1144
1145  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1146
1147  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1148
1149  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1150
1151  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1152
1153  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
1154
1155 </ul>
1156
1157
1158     </div>
1159     <p style="text-align: right">
1160  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1161 </p>
1162
1163   </body>
1164 </html>