Hi,
26c3 is over and we had quite some experiments going on. Not everything went good, but we learned a lot:

• babel did not survive the hack-center.
• ahcp did survive.
• measurement needs to be improved

That does not sound much, but i think it’s valuable information as we can now concentrate on some things and forget the other.

Openimp did not run good, it had a memory leak we got not fixed during 26c3, so the router kept rebooting after a few minutes.
Babel also hat real trouble, it ate up a lot of cpu and memory, it felt like olsr 3 years ago.
A few harddrives did not survive the heat of colo, so a part of the topology data are maybe lost.
Firmware building and development did work quite good, but could be better, that was mainly my verpeilung, there is room for improvement.

I will continiue the tests in my local mesh neighbourhood without babel and without ipv4 based olsr, so expect more firmware builds soon.

Recent experiments mit l2gvpn resulted in an olsr-mesh with over 1000 nodes:

Die Folien des Vortrages, den Daniel und ich am Mittwoch über IPv6 und siit gehalten haben, sind nun online: http://download.berlin.freifunk.net/pdf/vortrag/6mesh/

Ufo vom Rundfreifunk hat mich auf dem 25c3 interviewed, das mp3 gibs hier.

The 25th chaos communication congress is coming and the wireless community will be there. This time, we got a nice cosy space in the famous hackcenter, in the Wireless corner.

We will be right next to other interesting project like:

• GSM Hackers
• Console Hacking
• The Bricophone people

More on the floorplan.

We are going to build a ipv6 only mesh using siit to transport translated ipv4 traffic.

So, preparation are happening all over, even if you can see them only if you have a very close look:

Jow is fixing tickets and enhancing the openwrt luci framework to make sure we have a good start into the experiment.

Meanwhile, Daniel is working hard on our BGP routers to make sure we get a direct routing for the freifunk PI network into the 25c3. As you can see, our RIPE entry has been updated to enable routing to and from AS249, the congress network.

Felix has ported the siit kernel module to kernel 2.6 and commited.

Lehox and friends are working hard on n2n to get at least the worst bugs fixed, as we are going to use it as the backup vpn to our other BGP routers.

There is still a lot to do, but it looks like we are on a good way.

Achtung! the right way of doing is ::ffff:<ipv4>, so newer stuff will use that.

Based on the last posting, we are doing it now with an olsr mesh between the translators.

Between this two posts, jow fixed all remaining issues, making the setstuff shellscripts obsolete. He also fixed a HNA6 issue in the olsrd-luci package. Thanks, great work, jow.

Easy setup now, one internet4 gateway, one access node to give internet to the attached ipv4 clients.

I tried to draw it: ipv4-throught-ipv6-mesh.

gate:

• wan port is dhcp, lan port is 172.23.1.1/24
• siit0 gets a dummy address: 169.254.42.42
• wl0 gets an ipv6 address, in this case the fdca:ffee:babe::1:1/64
• we do a ::ffff:ffff:0/96 route into siit0, so everything from 6mesh goes into translation.
• an HNA6 of ::ffff:ffff:0:0/96 announces the mapped 0.0.0.0/0 ipv4 space.
• MTU on WAN, LAN down to 1400, ipv6 headers are slighly larger.

access1 has

• 172.23.2.1/24 on its lan, fdca:ffee:babe::1:2 on wl0 and the usual dummy address on siit0.
• we do a ::ffff:ffff:172.13.2.0/120 to siit0, because in this case, only traffic directed to clients needs to go into translation.
• same route as HNA6 announcement to catch the traffic out of the mesh.
• Also, MTU on LAN reduced to 1400.

To reproduce the setup, you need 2 broadcom based OpenWrt boxes, as the siit kernel module has not been ported to kernel 2.6.

its based on OpenWrt 8.09RC1 plus  some patches, which add siit, enable ipv6 forwarding and fix ipv6 static routes. plus a config file.

you can also use ready made firmwareimages. then, there is a config tarball and a uci-dump for gate and a tarball and dump for access1.

for building more accessnodes, you need to alter the lan ipaddress, the ipv6 route into siit0 and the HNA6.

and, as it is just a proof of concept, telnet is open, firewall is open and the wanport of access1 is configured for my local LAN, so i can access telnet and webif from my notebook.

configuration of olsr nameservice plugin to get proper DNS automagically is left as an exercise to the reader.

for questions, you can also join #freifunk on IRCNet or write to the wlanware mailinglist.

i would be happy to hear about any success.

Again, someone is building an open source mesh router: http://www.meshlium.com/

Looks like the big players in muni mesh are getting pressure from below.

Have to have a look on that, did anybody see the downloadbuttom?