SixXS::Sunset 2017-06-06

Routing trouble on OpenWRT
[de] Shadow Hawkins on Monday, 22 July 2013 17:36:45
Hi, I've finally got a tunnel working on my openWrt box (Backfire (10.03.1, r29592)) but I have some trouble with the setup of the routes and such. Would anyone please be kind enough and take my hand and walk me through this? I've done this tutorial : https://www.sixxs.net/wiki/Aiccu/Installing_on_OpenWRT and got the tunnel up and can ping into the v6 world from my router. But looking at my routing table I find it hard to believe that that's what it is supposed to look like:
root@Link:~# route -A inet6 Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 0 0 lo 2a01:1e8:e100:482::1/128 2a01:1e8:e100:482::1 UC 0 1 1 sixxs0 2a01:1e8:e100:482::2/128 :: U 0 4 0 lo 2a01:1e8:e100:482::/64 :: U 256 2 0 sixxs0 fe80::e8:e100:482:2/128 :: U 0 0 0 lo fe80::214:bfff:fec4:eed1/128 :: U 0 36 0 lo fe80::214:bfff:fec4:eed3/128 :: U 0 0 0 lo fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 eth0.0 fe80::/64 :: U 256 0 0 eth0.1 fe80::/64 :: U 256 0 0 br-lan fe80::/64 :: U 256 0 0 wl0 fe80::/64 :: U 256 0 0 sixxs0 ff02::1/128 ff02::1 UC 0 1 1 br-lan ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 eth0.0 ff00::/8 :: U 256 0 0 eth0.1 ff00::/8 :: U 256 0 0 br-lan ff00::/8 :: U 256 0 0 wl0 ff00::/8 :: U 256 0 0 sixxs0 ::/0 2a01:1e8:e100:482::1 UG 1 207 0 sixxs0 ::/0 2a01:1e8:e100:482::1 UG 1024 0 0 sixxs0
Routing trouble on OpenWRT
[ch] Jeroen Massar SixXS Staff on Tuesday, 23 July 2013 07:21:12
::/0 2a01:1e8:e100:482::1 UG 1 207 0 sixxs0
::/0 2a01:1e8:e100:482::1 UG 1024 0 0 sixxs0
How come you have two default routes? As they are almost identical it should not hurt, but something, next to AICCU, is apparently setting one up. The 'duplicate' fe80::/64 are normal, these are link-locals, thus every link has one. ff02::1 is there as you are a router for that interface as that is the multicast all-routers address. The ff00:/8 (the whole multicast range is meant with that maybe) are a bit odd, none of my boxes does that and there would not be any reason to do so either. What kernel version is this? For your other interfaces you should use a 'subnet' (see your User Home) and route a /64 per interface. Adding an address out of the /64 and enabling radvd should do the trick.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker