My two home servers are down for the moment. This also means that our two IPv6 SixXS tunnels are down which costs us 100 ISK per week. Argh! I need to get these up and running as soon as possible. Fortunately we have another VPS on Linux that can save us. So we just have to enable the two tunnels there and make sure that we can ping to/from both interfaces.
Setting up the two tunnels is easy. Use one configuration file per tunnel. Ensure that you change the parameters “tunnel_id” to the tunnel associated to this configuration file, one “pidfile” and “ipv6_interface” for each tunnel and “defaultroute” to false because we already have a default IPv6 route. Now you can start/stop each tunnel with:
aiccu start /etc/aiccu/tunnel0.conf aiccu start /etc/aiccu/tunnel1.conf aiccu stop /etc/aiccu/tunnel0.conf aiccu stop /etc/aiccu/tunnel1.conf
Don’t forget to hack /etc/init.d/aiccu to start/stop both tunnel on each reboot. OK! So now ifconfig list the two interfaces, up and running sixxs0 and sixxs1. This is great but wait… Nobody outside can ping these interfaces. The tunnel must ping to be considered active by SixXS so we better get this running.
For now we have these three interfaces and IPs (not the actual names/IPs):
- net0 (2001::1) default
- sixxs0 (2a02::1)
- sixxs1 (2a02::2)
By default, all our IPv6 traffic goes through net0. However and unsurprisingly our ISP filters the traffic at the output of net0. So we cannot use this interface to answer the echo-requests. Actually, what we want is that traffic originating 2a02::1 goes through sixxs0 and from 2a02::2 goes through sixxs1. That is, one default route based on the source address.
Linux has long had support for multiple routing tables (CONFIG_IP_MULTIPLE_TABLES). Basically what we will do here:
- Create two routing tables for each tunnel interface (sixxs0, sixxs1).
- Each table will have a default route through its interface.
- Lookup into one of the two tables according to the source IP.
You can find some relevant documentation in Linux Advanced Routing & Traffic Control, Chapter 4.
We first list the actual rules:
# ip rule list 0: from all lookup local 32766: from all lookup main 32767: from all lookup default
We can see that we have three routing tables. One for the local addresses, the normal routing table (what you get with
ip -6 route) and the fallback default table.
Let’s first check the local routing table (we are just curious):
# ip -6 route list table local local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 0 local 2a02::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 0 local 2001::1 via :: dev lo proto none metric 0 mtu 16436 rtt 6ms rttvar 7ms cwnd 10 advmss 16376 hoplimit 0 local 2a02::2 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 0 local fe80::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 0 local fe80::2 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 0 ff00::/8 dev net0 metric 256 mtu 1500 advmss 1440 hoplimit 0 ff00::/8 dev sixxs1 metric 256 mtu 1280 advmss 1220 hoplimit 0 ff00::/8 dev sixxs0 metric 256 mtu 1280 advmss 1220 hoplimit 0
So now you know what’s going on when you ping one of your local interfaces. But back to our point. We name our two new routing tables in /etc/iproute2/rt_tables:
# SixXS tables 200 sixxs0 201 sixxs1
Now we add the default route in each of these two tables:
ip -6 route add default dev sixxs0 table sixxs0 ip -6 route add default dev sixxs1 table sixxs1
And finally we use two rules to map the source address to the correct routing table:
# ip -6 rule add from 2a02::1 table sixxs0 # ip -6 rule add from 2a02::2 table sixxs1 # ip -6 rule list 0: from all lookup local 16383: from 2a02::1 lookup sixxs0 16383: from 2a02::2 lookup sixxs1 32766: from all lookup main 32767: from all lookup default
It should be OK but let’s check that. We can ping from the sixxs interfaces:
ping6 -c1 -I 2a02::1 www.kame.net ping6 -c1 -I 2a02::2 www.kame.net
We also check that we can ping our interfaces from another host:
ping6 -c1 2a02::1 ping6 -c1 2a02::2
Everything works, that’s great! Finally we just hack /etc/init.d/aiccu to configure the routing tables on each reboot. Note that you need to sleep a bit when you issue the aiccu start because the daemon needs a bit of time to enable the tunnels. Also note that you must be careful when you test your script (quoting the SixXS FAQ):
“If a client connects more than 4 times in 60 seconds (1 minute) the client will not be allowed to connect again for the next 5 minutes. In case this threshold is exceeded more than once in 24 hours a client will be automatically blocked for a week.”
As you can guess, I have been blocked. Oops!