SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1247695
Ticket Status: Resolved

PoP: 

chzrh01 PoP IPv4 not routed properly
[ch] Shadow Hawkins on Monday, 28 December 2009 10:29:08
admin edits: * change subject from "chzrh01 PoP apparently unreachable from BlueWin DSL (Swisscom)" to "chzrh01 PoP IPv4 not routed properly" * When a PoP is reachable over IPv6 and/or IPv4 it is marked as online this as routing issues can be very local. * removed "me too" posts. When a ticket is there, the problem is listed, one does not have to add "me too" then. We will be looking at it in due time and resolving it in due time. Please also read the PoP notice which states:
Peering with IP-MAN (AS20932) recommended, PoP might not be reachable from around the globe, thus request from your ISP to peer with IP-MAN to properly use this PoP if you experience connectivity problems.
-- I am reporting an issue with tunnel T15932, my RIPE ID is AT6085-RIPE (arrigo@sevenseas.org).
Tunnel Name semola PoP Name chzrh01 PoP Location Zurich, Switzerland PoP IPv4 194.1.163.40 TIC Server tic.sixxs.net (default in AICCU) Your Location Geneva, Switzerland Your IPv4 AYIYA, currently 83.77.169.82 IPv6 Prefix 2001:41e0:ff00:6d::1/64 PoP IPv6 2001:41e0:ff00:6d::1 Your IPv6 2001:41e0:ff00:6d::2 Created 2008-06-24 13:45:52 CET Last Alive 2009-11-04 10:52:45 CET State AYIYA (automatically enabled on the fly)
Since Monday evening it appears that the PoP is unreachable from Bluewin DSL (Swisscom), at least from the addresses I am being given by Swisscom's DHCP (Swisscom forces a DHCP address change every 20 hours). The output from aiccu autotest is (traceroute stars and comments chopped): # aiccu autotest add net default: gateway 2001:41e0:ff00:6d::1 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.4.4.2) PING 10.4.4.2 (10.4.4.2): 56 data bytes 64 bytes from 10.4.4.2: icmp_seq=0 ttl=255 time=0.454 ms 64 bytes from 10.4.4.2: icmp_seq=1 ttl=255 time=0.098 ms 64 bytes from 10.4.4.2: icmp_seq=2 ttl=255 time=0.093 ms --- 10.4.4.2 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.093/0.215/0.454/0.169 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (194.1.163.40) PING 194.1.163.40 (194.1.163.40): 56 data bytes --- 194.1.163.40 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ###### ####### [3/8] Traceroute to the PoP (194.1.163.40) over IPv4 traceroute to 194.1.163.40 (194.1.163.40), 64 hops max, 40 byte packets 1 outer-gw.alchemistowl.org (10.4.4.1) 5.199 ms 4.177 ms 4.359 ms 2 1-128.77-83.cust.bluewin.ch (83.77.128.1) 14.705 ms 14.355 ms 14.495 ms 3 193-255-3-213.bluewin.ch (213.3.255.193) 15.366 ms 13.506 ms 13.433 ms 4 189-247-3-213.bluewin.ch (213.3.247.189) 14.273 ms 13.469 ms 16.143 ms 5 if234.ip-plus.bluewin.ch (195.186.0.234) 13.277 ms 13.261 ms 15.938 ms 6 i79tix-015-ten1-1.bb.ip-plus.net (138.187.129.74) 13.702 ms 14.357 ms 16.216 ms 7 ge-6-15.car2.Zurich1.Level3.net (213.242.67.129) 13.841 ms 13.738 ms 13.568 ms 8 * * * 9 * * * 10 * * * ^C ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1%4 time=0.143 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1%4 time=0.257 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1%4 time=0.244 ms --- ::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.143/0.215/0.257/0.051 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:41e0:ff00:6d::2) PING6(56=40+8+8 bytes) 2001:41e0:ff00:6d::2 --> 2001:41e0:ff00:6d::2 16 bytes from 2001:41e0:ff00:6d::2: Echo Request 16 bytes from 2001:41e0:ff00:6d::2, icmp_seq=0 hlim=64 dst=2001:41e0:ff00:6d::2%4 time=0.118 ms 16 bytes from 2001:41e0:ff00:6d::2: Echo Request 16 bytes from 2001:41e0:ff00:6d::2, icmp_seq=1 hlim=64 dst=2001:41e0:ff00:6d::2%4 time=0.264 ms 16 bytes from 2001:41e0:ff00:6d::2: Echo Request 16 bytes from 2001:41e0:ff00:6d::2, icmp_seq=2 hlim=64 dst=2001:41e0:ff00:6d::2%4 time=0.245 ms --- 2001:41e0:ff00:6d::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.118/0.209/0.264/0.065 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:41e0:ff00:6d::1) PING6(56=40+8+8 bytes) 2001:41e0:ff00:6d::2 --> 2001:41e0:ff00:6d::1 --- 2001:41e0:ff00:6d::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:41e0:ff00:6d::2, 64 hops max, 12 byte packets 1 * * * 2 * * * 3 * * * 11 *^C ###### ###### [8/8] Traceroute6 to (www.kame.net) traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:41e0:ff00:6d::2, 64 hops max, 12 byte packets ^C ###### ###### ACCU Quick Connectivity Test (done) I have tried ringing Swisscom's support line but as you can imagine they are clueless like all good DSL providers. Best regards, Arrigo
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 05 November 2009 10:43:39
Message is Locked
The state of this ticket has been changed to confirmed
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 November 2009 23:01:28
Message is Locked
The state of this ticket has been changed to resolved
chzrh01 PoP IPv4 not routed properly
[ch] Shadow Hawkins on Monday, 04 January 2010 16:03:36
Summary ping 194.1.163.40 (chzrh01.sixxs.net.) fail Long info I didn't use my tunnel (T14904) for quite some time now, however I didn't change the configuration. The TCP login works correctly, and an attempt to create a tunnel to 194.1.163.40 is attempted. No answer comes to any of the datagrams sent out and the tunnel doesn't appear up in the sixxs GUI. I have started a aiccu and a ping6 2001:41e0:ff00:30::1 (which is supposedly the sixxs side of this tunnel), IPv4 datagrams get send out, but no reply: 20:01:26.341219 IP 80.83.54.2.58183 > 194.1.163.40.5072: UDP, length 148 Debugging using the aiccu test I can't seem to ping 194.1.163.40. Various tests around the globe have shown that only from Romania this seems reachable (not from US, not from three different Swiss ISPs: Cablecom, Sunrise, IP Worldcom). Thank you for any help.
chzrh01 PoP IPv4 not routed properly
[ch] Jeroen Massar SixXS Staff on Monday, 04 January 2010 16:07:29
Debugging using the aiccu test I can't seem to ping 194.1.163.40.
Various tests around the globe have shown that only from Romania
this seems reachable (not from US, not from three different Swiss ISPs:
Cablecom, Sunrise, IP Worldcom).
We are working with Cablecom to resolve this issue. For the rest, please actually read the first post which has details on this problem.

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

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