SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1099138
Ticket Status: User

PoP: sesto01 - Availo (Stockholm)

No IPv6 connectivity to sesto01
[ua] Shadow Hawkins on Wednesday, 27 May 2009 11:56:08
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: My ID is NT664-RIPE, using tunnel T10096 to sesto01. After about 18:00 2009-05-25, IPv6 connectivity through the tunnel stopped. Running aiccu test stops working here: ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ff00:12d::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:16d8:ff00:12d::1(2001:16d8:ff00:12d::1) 56 data bytes --- 2001:16d8:ff00:12d::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2012ms No firewall rules enabled for this tunnel. Listening with tcpdump on the tunnel interface I see only traffic going out, nothing coming back from sesto01.
No IPv6 connectivity to sesto01
[ua] Shadow Hawkins on Wednesday, 27 May 2009 11:58:35
Please disregard, after looping aiccu stop/start for a while, the tunnel works again.
No IPv6 connectivity to sesto01
[ch] Jeroen Massar SixXS Staff on Wednesday, 27 May 2009 11:58:49
That you can't ping is one thing, but there could be a lot of reasons for that. Please actually supply the requested data.
No IPv6 connectivity to sesto01
[ua] Shadow Hawkins on Tuesday, 02 June 2009 15:21:43
Hi again, After a while, tunnel became inoperable again, although it is brought up without problems. I'm talking about ICMP echo just as about indicator. By the fact, no IPv6 packets are returning to me. nick@fallout:~$ sudo aiccu start Tunnel Information for T10096: POP Id : sesto01 IPv6 Local : 2001:16d8:ff00:12d::2/64 IPv6 Remote : 2001:16d8:ff00:12d::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled nick@fallout:~$ curl -v http://noc.sixxs.net * About to connect() to noc.sixxs.net port 80 (#0) * Trying 2001:838:1:1:210:dcff:fe20:7c7c... Timeout * Trying 213.197.29.32... connected At the same time dumping traffic to my PoP: nick@fallout:~$ sudo tcpdump -n -p host 82.96.56.14 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 16:14:56.251040 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:14:59.247750 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:15:05.247765 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:15:16.168910 IP 192.168.1.7.38050 > 82.96.56.14.3740: UDP, length 89 16:15:17.247785 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:15:41.247764 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:16:16.169875 IP 192.168.1.7.35974 > 82.96.56.14.3740: UDP, length 89 16:16:29.247761 IP 192.168.1.7 > 82.96.56.14: IP6 2001:16d8:ff00:12d::2.36577 > 2001:838:1:1:210:dcff:fe20:7c7c.80: Flags [S], seq 225992937, win 4880 , options [[|tcp] 16:17:16.171020 IP 192.168.1.7.34371 > 82.96.56.14.3740: UDP, length 89 Please tell me if I can do anything more.
No IPv6 connectivity to sesto01
[ch] Jeroen Massar SixXS Staff on Wednesday, 03 June 2009 17:20:36
The only thing the TCPdump output tells is that you are behind a NAT; if that NAT drops packets for whatever reason (either inbound or outbound) then you indeed don't have any connectivity anymore. But that seems to be a local issue, nothing we can do about.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 27 May 2009 11:58:53
Message is Locked
The state of this ticket has been changed to user

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

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