|
Internal routing problems
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 04 September 2010 10:53:54
A tunnel has been assigned to me two days ago and I am trying to use it with my Linux computer (which uses a static IPv4 address) and aiccu but no success so far...
What I did:
I used my login and tunnel information in the aiccu.conf and configured tun0 as ipv6_interface and left the other options on default.
What happens:
With aiccu test, IPv4 works perfectly, ping6 to localhost and my tunnel address too. ping6 to the remote endpoint has 100% packet loss though.
tun0 uses the 2001-endpoint address assigned to me and has a route to the same 2001-net and a default route to the remote endpoint (further, there are fe80 and ff00 routes but I think they are not important in this case).
I used iptraf to monitor tun0 as I ping6'ed the remote tunnel IP but nothing happens on tun0 and as I monitored eth0 I saw the ping6 packets using this interface, so the internal routing is wrong.
I'd like to route all ipv4 traffic over eth0 and all ipv6 traffic over tun0 but as the routes are there, I don't know where the problem is or how to fix this. Can someone please tell me how to configure my internal routing correctly?
Internal routing problems
... configured tun0 as ipv6_interface and left the other options on default.
Why do that when you have a static tunnel? The defaults in AICCU are correct, one just needs to fill in the username and password and optionally if you have multiple tunnels the tunnel_id.
Can someone please tell me how to configure my internal routing correctly?
You could read that big orange box and follow the link and then read the "Reporting Problems Checklist" and provide the requested information.
Without the output everybody will be guessing.
Internal routing problems
Shadow Hawkins on Saturday, 04 September 2010 13:35:46
ok, with your information not to use tun I found out that aiccu needs to use sit to bring the "sixxs" device up. As it didn't work statically compiled into the kernel, I compiled it as a module and now aiccu was able to bring up the sixxs device using the default config with only my login data.
I think I will write this somewhere into the wiki, because I didn't see this important information in the gentoo howto, which I used.
Unfortunately the routing still doesn't work. Here are my device and routing configurations after starting aiccu. I don't use any netfiltering rules.
moon ~ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:04:23:c1:e1:e7 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:1f:d0:6a:57:51 brd ff:ff:ff:ff:ff:ff
inet 137.226.143.52/23 brd 137.226.143.255 scope global eth0
inet6 2002:89e2:8f3b:8:21f:d0ff:fe6a:5751/64 scope global dynamic
valid_lft 6926sec preferred_lft 1526sec
inet6 fec0::8:21f:d0ff:fe6a:5751/64 scope site dynamic
valid_lft 6926sec preferred_lft 1526sec
inet6 fe80::21f:d0ff:fe6a:5751/64 scope link
valid_lft forever preferred_lft forever
4: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN
link/ipip 0.0.0.0 brd 0.0.0.0
5: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
6: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
7: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN
link/sit 137.226.143.52 peer 78.35.24.124
inet6 2001:4dd0:ff00:2b5::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::89e2:8f34/128 scope link
valid_lft forever preferred_lft forever
moon ~ # ip route show
137.226.142.0/23 dev eth0 proto kernel scope link src 137.226.143.52
127.0.0.0/8 via 127.0.0.1 dev lo
default via 137.226.143.1 dev eth0 metric 3
moon ~ # ip -6 route show
2001:4dd0:ff00:2b5::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
2002:89e2:8f3b:8::/64 dev eth0 proto kernel metric 256 expires 6908sec mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fec0:0:0:8::/64 dev eth0 proto kernel metric 256 expires 6908sec mtu 1500 advmss 1440 hoplimit 0
default via fe80::69e2:5e09:cc3e:2172 dev eth0 proto kernel metric 1024 expires 65234sec mtu 1500 advmss 1440 hoplimit 0
default via 2001:4dd0:ff00:2b5::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
moon ~ # uname -a
Linux moon 2.6.35.4 #5 SMP PREEMPT Sat Sep 4 12:14:02 CEST 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux
Internal routing problems
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state [..]
inet6 2002:89e2:8f3b:8:21f:d0ff:fe6a:5751/64 scope global dynamic
Somebody has 6to4 enabled on your network. Most likely you should be able to get native IPv6 inside DFN though.
137.226.143.59 / stern.tvk.RWTH-Aachen.DE is providing this 6to4.
default via fe80::69e2:5e09:cc3e:2172 dev eth0 proto kernel metric 1024... default via 2001:4dd0:ff00:2b5::1 dev sixxs metric 1024 mtu 1280 ...
You have two default routes, one over the tunnel, the other over 6to4.
Get rid of one of the two, either 6to4 or the tunnel.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 04 September 2010 11:05:11
Posting is only allowed when you are