SixXS::Sunset 2017-06-06

AICCU routing problem under RHEL5
[cz] Shadow Hawkins on Thursday, 13 November 2008 23:40:16
Hi, I've got problems with setting up IPv6 over AICCU under RHEL5. AICCU correctly starts up, creates tunnel and IPv6 network device. I'm able to ping6 to the "remote end" of the tunnel but not any further (e.g. www.kame.net, ipv6.google.com - even if I resolve hostname manually and ping IPv6 address directly). It always reports
connect: Network is unreachable
My guess is that there is something rotten in routing table - but can't find out what (it seems to me that default GW is correctly setup). Here I'm attaching aiccu autotest output and also my routing table.
Tunnel Information for T17963: POP Id : dedus01 IPv6 Local : 2a01:198:200:270::2/64 IPv6 Remote : 2a01:198:200:270::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.10.10) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.10.10 (192.168.10.10) 56(84) bytes of data. 64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.061 ms 64 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=0.051 ms 64 bytes from 192.168.10.10: icmp_seq=3 ttl=64 time=0.033 ms --- 192.168.10.10 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.033/0.048/0.061/0.012 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (91.184.37.98) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 91.184.37.98 (91.184.37.98) 56(84) bytes of data. 64 bytes from 91.184.37.98: icmp_seq=1 ttl=54 time=25.4 ms 64 bytes from 91.184.37.98: icmp_seq=2 ttl=54 time=25.4 ms 64 bytes from 91.184.37.98: icmp_seq=3 ttl=54 time=25.4 ms --- 91.184.37.98 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 25.405/25.413/25.425/0.184 ms ###### ####### [3/8] Traceroute to the PoP (91.184.37.98) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 91.184.37.98 (91.184.37.98), 30 hops max, 40 byte packets 1 (192.168.10.1) 1.054 ms 1.765 ms 2.466 ms 2 195.47.64.6 (195.47.64.6) 8.916 ms 11.092 ms 13.560 ms 3 195.47.11.33.adsl.nextra.cz (195.47.11.33) 16.245 ms 18.927 ms 20.865 ms 4 phnc10-vl-62.net.nextra.cz (195.47.20.254) 28.733 ms 31.260 ms 33.621 ms 5 phnc10-vl-62.net.nextra.cz (195.47.20.254) 35.813 ms 38.271 ms 40.511 ms 6 193.86.72.53 (193.86.72.53) 43.400 ms 11.195 ms 11.665 ms 7 tr02-gwb-stm16.gts.cz (195.39.48.85) 14.097 ms 16.849 ms 19.474 ms 8 defra1-czpratr01-1-stm16.gtsce.net (195.39.208.113) 29.284 ms 32.232 ms 34.436 ms 9 decix.r1.fra3.opencarrier.eu (80.81.192.24) 38.356 ms 41.290 ms 43.771 ms 10 oc-fra.speedpartner.de (194.54.95.218) 170.655 ms 173.064 ms 173.229 ms 11 dedus01.sixxs.net (91.184.37.98) 58.276 ms 59.161 ms 61.483 ms ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=0 ttl=64 time=0.027 ms 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.028 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.011 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.011/0.022/0.028/0.007 ms, pipe 2 ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:270::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:198:200:270::2(2a01:198:200:270::2) 56 data bytes 64 bytes from 2a01:198:200:270::2: icmp_seq=0 ttl=64 time=0.033 ms 64 bytes from 2a01:198:200:270::2: icmp_seq=1 ttl=64 time=0.028 ms 64 bytes from 2a01:198:200:270::2: icmp_seq=2 ttl=64 time=0.013 ms --- 2a01:198:200:270::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.013/0.024/0.033/0.010 ms, pipe 2 ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:270::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING 2a01:198:200:270::1(2a01:198:200:270::1) 56 data bytes 64 bytes from 2a01:198:200:270::1: icmp_seq=0 ttl=64 time=27.1 ms 64 bytes from 2a01:198:200:270::1: icmp_seq=1 ttl=64 time=27.3 ms 64 bytes from 2a01:198:200:270::1: icmp_seq=2 ttl=64 time=27.3 ms --- 2a01:198:200:270::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 27.124/27.248/27.315/0.160 ms, pipe 2 ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 40 byte packets connect: Network is unreachable ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085), 30 hops max, 40 byte packets connect: Network is unreachable ###### ###### ACCU Quick Connectivity Test (done) ### Either the above all works and gives no problems ### or it shows you where what goes wrong ### Check the SixXS FAQ (http://www.sixxs.net/faq/ ### for more information and possible solutions or hints ### Don't forget to check the Forums (http://www.sixxs.net/forum/) ### for a helping hand. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea. Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface 2a01:198:200:270::/64 :: U 256 1 0 sixxs fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 sixxs ::/0 2a01:198:200:270::1 UG 1024 0 0 sixxs ::1/128 :: U 0 83 1 lo 2a01:198:200:270::2/128 :: U 0 4 1 lo fe80::98:200:270:2/128 :: U 0 0 1 lo fe80::20f:eaff:fe30:ddf6/128 :: U 0 0 1 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs
Thanks for any hints :-) Libor
AICCU routing problem under RHEL5
[de] Shadow Hawkins on Friday, 14 November 2008 00:58:19
You are most likely hit by this bug in the RHEL kernel: Bugzilla Solution would be either the test kernel or manually adding a route to 2000::/3 to the same gateway by doing
/sbin/ip -6 route add 2000::/3 dev sixxs
I'm not sure whether it is possible to automate this easily. Bernhard
AICCU routing problem under RHEL5
[cz] Shadow Hawkins on Friday, 14 November 2008 02:26:06
Yes, that helped! To automate the fix I tried to use "setupscript" option in aiccu.conf, but the script doesn't get executed :-( So I had to modify the init.d script. Just in case anybody else triggers this - put 1 second sleep before the "ip" command, otherwise it will fail.
AICCU routing problem under RHEL5
[nl] Shadow Hawkins on Saturday, 15 November 2008 13:12:21
Just put the static route in the static route tables. /etc/sysconfig/static-routes-ipv6 here contains: sixxs 2000::/3

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

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