SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #7251790
Ticket Status: User

PoP: demuc02 - M-net Telekommunikations GmbH (Muenchen)

subnet not available on T71829
[de] Shadow Hawkins on Sunday, 17 June 2012 13:03:35
hello, my subnet R32741 is not available any longer on my tunnel. tunnel is upan i can ping my ipv6 pop ip remotely.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 17 June 2012 18:44:38
Message is Locked
The state of this ticket has been changed to user
subnet not available on T71829
[ch] Jeroen Massar SixXS Staff on Sunday, 17 June 2012 18:45:00
Please read and follow the "Reporting Problems" section on the Contact page and provide the requested details.
subnet not available on T71829
[de] Shadow Hawkins on Monday, 18 June 2012 09:00:21
Tunnel Information for T71829: POP Id : demuc02 IPv6 Local : 2001:a60:f000:16a::2/64 IPv6 Remote : 2001:a60:f000:16a::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled add tunnel sit0 failed: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (212.29.7.197) ### 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 212.29.7.197 (212.29.7.197) 56(84) bytes of data. 64 bytes from 212.29.7.197: icmp_req=1 ttl=64 time=0.058 ms 64 bytes from 212.29.7.197: icmp_req=2 ttl=64 time=0.072 ms 64 bytes from 212.29.7.197: icmp_req=3 ttl=64 time=0.071 ms --- 212.29.7.197 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.058/0.067/0.072/0.006 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (62.245.150.2) ### 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 62.245.150.2 (62.245.150.2) 56(84) bytes of data. 64 bytes from 62.245.150.2: icmp_req=1 ttl=60 time=0.846 ms 64 bytes from 62.245.150.2: icmp_req=2 ttl=60 time=0.932 ms 64 bytes from 62.245.150.2: icmp_req=3 ttl=60 time=0.948 ms --- 62.245.150.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.846/0.908/0.948/0.056 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (62.245.150.2) 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 62.245.150.2 (62.245.150.2), 30 hops max, 60 byte packets 1 vlan97.gw2.teamware-gmbh.de (212.29.7.222) 1.931 ms 2.531 ms 2.873 ms 2 fe-1-0.gw5.teamware-gmbh.de (212.29.0.254) 1.118 ms 1.490 ms 1.744 ms 3 teamware-gw.m-online.net (212.18.3.113) 16.079 ms 16.081 ms 16.060 ms 4 ten0-1-0-4.r4.muc2.m-online.net (212.18.6.46) 1.095 ms 1.206 ms 1.331 ms 5 demuc02.sixxs.net (62.245.150.2) 0.966 ms 0.944 ms 0.931 ms ###### Did this work? [Y/n] y ###### [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=1 ttl=64 time=0.087 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.075 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.070 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.070/0.077/0.087/0.010 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:a60:f000:16a::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:a60:f000:16a::2(2001:a60:f000:16a::2) 56 data bytes 64 bytes from 2001:a60:f000:16a::2: icmp_seq=1 ttl=64 time=0.099 ms 64 bytes from 2001:a60:f000:16a::2: icmp_seq=2 ttl=64 time=0.104 ms 64 bytes from 2001:a60:f000:16a::2: icmp_seq=3 ttl=64 time=0.101 ms --- 2001:a60:f000:16a::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.099/0.101/0.104/0.008 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:a60:f000:16a::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 2001:a60:f000:16a::1(2001:a60:f000:16a::1) 56 data bytes 64 bytes from 2001:a60:f000:16a::1: icmp_seq=1 ttl=64 time=0.974 ms 64 bytes from 2001:a60:f000:16a::1: icmp_seq=2 ttl=64 time=0.982 ms 64 bytes from 2001:a60:f000:16a::1: icmp_seq=3 ttl=64 time=1.23 ms --- 2001:a60:f000:16a::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.974/1.063/1.235/0.126 ms ###### Did this work? [Y/n] y ###### [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, 80 byte packets 1 xena.enskat.de (2001:a60:f036::10) 2172.571 ms !H 2172.526 ms !H 2172.499 ms !H ###### Did this work? [Y/n] y ###### [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:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 xena.enskat.de (2001:a60:f036::10) 4.594 ms !H 4.541 ms !H 4.515 ms !H ###### Did this work? [Y/n] y ###### ACCU Quick Connectivity Test (done)
subnet not available on T71829
[ch] Jeroen Massar SixXS Staff on Monday, 18 June 2012 16:22:46
As mentioned in the previous reply: Please read and follow the "Reporting Problems" section on the Contact page and provide the requested details. While AICCU test is great at determining something is broken it does not show what is actually broken. Please provide interface tables, routing tables etc as requested. The general internet can reach the gateway address:
traceroute to 2001:a60:f000:16a::2 (2001:a60:f000:16a::2) from 2001:838:1:1:210:dcff:fe20:7c7c, port 33434, from port 48472, 30 hops max, 60 byte packets 1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.366 ms 0.351 ms 0.352 ms 2 gi2-11.nikhef.ipv6.concepts-ict.net (2001:838:5:a::1) 2.395 ms 2.364 ms 2.472 ms 3 AMS-IX.v6.lambdanet.net (2001:7f8:1::a501:3237:1) 2.938 ms 2.899 ms 2.955 ms 4 HAN-1-eth0-159.v6.lambdanet.net (2001:7f0:0:15::1) 6.520 ms 6.408 ms 6.392 ms 5 FRA-3-eth020.v6.lambdanet.net (2001:7f0:0:a::2) 9.286 ms 9.243 ms 9.251 ms 6 NUE-2-eth100.v6.lambdanet.net (2001:7f0:0:f::1) 12.766 ms 12.777 ms 12.786 ms 7 M-net-NUE.v6.lambdanet.net (2001:7f0:1:6::2) 18.071 ms 18.159 ms 18.172 ms 8 2001:a60:0:30::2 (2001:a60:0:30::2) 22.843 ms 23.035 ms 23.479 ms 9 2001:a60:0:30::1:1 (2001:a60:0:30::1:1) 22.067 ms 22.871 ms 22.227 ms 10 gw-363.muc-02.de.sixxs.net (2001:a60:f000:16a::1) 21.641 ms 21.642 ms 21.454 ms
As such you are likely using the wrong source address or so for the above to happen.
subnet not available on T71829
[de] Shadow Hawkins on Tuesday, 19 June 2012 08:53:26
it was working before. right the gw ip is reachable but not the subnet. For example: 2001:a60:f036::2 is on the httpd: /etc/httpd/conf/httpd.conf:Listen [2001:a60:f036::2]:80 /etc/httpd/conf/httpd.conf:Listen [2001:a60:f036::2]:443 /etc/httpd/conf/vhosts_v6.conf:NameVirtualHost [2001:a60:f036::2]:80 /etc/httpd/conf/vhosts_v6.conf:NameVirtualHost [2001:a60:f036::2]:443 /etc/httpd/conf/vhosts_v6.conf:<VirtualHost [2001:a60:f036::2]:80> /etc/httpd/conf/vhosts_v6.conf:<VirtualHost [2001:a60:f036::2]:443> Linux xena.enskat.de 3.4.2-4.fc17.i686.PAE #1 SMP Thu Jun 14 22:11:26 UTC 2012 i686 i686 i386 GNU/Linux aiccu: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1280 inet6 fe80::d41d:7c6 prefixlen 64 scopeid 0x20<link> inet6 fe80::d41d:7c5 prefixlen 64 scopeid 0x20<link> inet6 2001:a60:f000:16a::2 prefixlen 64 scopeid 0x0<global> sit txqueuelen 0 (IPv6-nach-IPv4) RX packets 4214 bytes 1449169 (1.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2052 bytes 357552 (349.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 212.29.7.197 netmask 255.255.255.224 broadcast 212.29.7.223 inet6 2001:a60:f036::3 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::10 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::7 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::5 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::4 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::8 prefixlen 48 scopeid 0x0<global> inet6 fe80::2e0:18ff:fe95:31c2 prefixlen 64 scopeid 0x20<link> inet6 2001:a60:f036::6 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::9 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::2 prefixlen 48 scopeid 0x0<global> inet6 2001:a60:f036::1 prefixlen 48 scopeid 0x0<global> ether 00:e0:18:95:31:c2 txqueuelen 1000 (Ethernet) RX packets 233177 bytes 39356187 (37.5 MiB) RX errors 0 dropped 34240 overruns 0 frame 0 TX packets 263397 bytes 196214346 (187.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Lokale Schleife) RX packets 129420 bytes 186595718 (177.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 129420 bytes 186595718 (177.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 netstat -rn Kernel IP Routentabelle Ziel Router Genmask Flags MSS Fenster irtt Iface 0.0.0.0 212.29.7.222 0.0.0.0 UG 0 0 0 eth0 212.29.7.192 0.0.0.0 255.255.255.224 U 0 0 0 eth0 Hope thats all infos you need.
subnet not available on T71829
[de] Shadow Hawkins on Tuesday, 19 June 2012 10:11:54
cat ../network NETWORKING=yes HOSTNAME=xena.enskat.de NETWORKING_IPV6=yes IPV6FORWARDING=yes ifcfg-System_eth0 TYPE=Ethernet BOOTPROTO=none IPADDR0=212.29.7.197 PREFIX0=27 GATEWAY0=212.29.7.222 IPADDR1=212.29.7.198 PREFIX1=27 GATEWAY1=212.29.7.222 DNS1=212.29.7.197 DNS2=212.29.0.1 DOMAIN=enskat.de DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=yes IPV6_AUTOCONF=no IPV6_DEFAULTGW=2001:a60:f000:16a::1 IPV6ADDR=2001:a60:f036::1/48 IPV6ADDR_SECONDARIES="2001:a60:f036::2/48 2001:a60:f036::3/48 2001:a60:f036::4/48 2001:a60:f036::5/48 2001:a60:f036::6/48 2001:a60:f036::7/48 2001:a60:f036::8/48 2001:a60:f036::9/48 2001:a60:f036::10/48" IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME="System eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 ONBOOT=yes DNS3=2001:a60::53:1
subnet not available on T71829
[de] Shadow Hawkins on Tuesday, 19 June 2012 10:24:04
[root@xena /]# ip -6 route unreachable ::/96 dev lo metric 1024 error -101 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 2001:a60:f000:16a::1 dev eth0 proto static metric 1024 2001:a60:f000:16a::/64 via :: dev aiccu proto kernel metric 256 2001:a60:f036::/48 dev eth0 proto kernel metric 256 unreachable 2002:a00::/24 dev lo metric 1024 error -101 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 unreachable 2002:e000::/19 dev lo metric 1024 error -101 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 unreachable fe80::/64 dev lo proto kernel metric 256 error -101 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 via :: dev aiccu proto kernel metric 256 default via 2001:a60:f000:16a::1 dev eth0 proto static metric 1 default via 2001:a60:f000:16a::1 dev aiccu metric 1024 [root@xena /]# ip route default via 212.29.7.222 dev eth0 proto static 212.29.7.192/27 dev eth0 proto kernel scope link src 212.29.7.197
subnet not available on T71829
[de] Shadow Hawkins on Tuesday, 19 June 2012 10:28:15
ok find it. it seems kernelupdate messed up IPV6_DEFAULTGW= when i remove the line: IPV6_DEFAULTGW=2001:a60:f000:16a::1 the defaultgw is aiccu and all is working with the subnet. strange

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

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