SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #9834122
Ticket Status: User

PoP: czprg01 - Ignum, s.r.o. (Prague)

PoP endpoint unreachable few minutes after connect (T128030)
[cz] Shadow Hawkins on Tuesday, 30 July 2013 00:06:37
Hello, my PoP endpoint is unreachable few minutes after connecting the tunnel. Just after establishing the tunnel, I can successfully ping ipv6.google.com and for example see live video from the http://www.terena.org/webcam/ But after ~1 minute (looks like after passing some amount of traffic), PoP endpoint starts being unreachable. It repeats, when I reconnect the tunnel (restart aiccu) Tunnel Id: T128030 (AYIYA tunnel, I'm behind NAT) OS: Windows 8 Using: aiccu-2012-02-02-windows-console.exe C:\>ping -6 2a01:8c00:ff00:23e::1 -t ... Reply from 2a01:8c00:ff00:23e::1: time=2ms Reply from 2a01:8c00:ff00:23e::1: time=2ms Reply from 2a01:8c00:ff00:23e::1: time=3ms Reply from 2a01:8c00:ff00:23e::1: time=3ms Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 2a01:8c00:ff00:23e::1: Packets: Sent = 94, Received = 90, Lost = 4 (4% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 9ms, Average = 2ms C:\>ping -6 2a01:8c00:ff00:23e::2 Pinging 2a01:8c00:ff00:23e::2 with 32 bytes of data: Reply from 2a01:8c00:ff00:23e::2: time<1ms Reply from 2a01:8c00:ff00:23e::2: time<1ms Reply from 2a01:8c00:ff00:23e::2: time<1ms I tested it with firewall disabled. C:\>netsh i ipv6 sh r Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ Yes Manual 256 ::/0 31 2a01:8c00:ff00:23e::1 No System 256 ::1/128 1 Loopback Pseudo-Interface 1 No System 256 2a01:8c00:ff00:23e::/64 31 sixxs No System 256 2a01:8c00:ff00:23e::2/128 31 sixxs No System 256 fe80::/64 13 Ethernet 2 No System 256 fe80::/64 15 Local Area Connection No System 256 fe80::/64 31 sixxs No System 256 fe80::8171:acd5:7308:5658/128 13 Ethernet 2 No System 256 fe80::b125:1e00:4e0f:9c40/128 31 sixxs No System 256 fe80::f83d:9a5c:af37:4004/128 15 Local Area Connection No System 256 ff00::/8 1 Loopback Pseudo-Interface 1 No System 256 ff00::/8 13 Ethernet 2 No System 256 ff00::/8 15 Local Area Connection No System 256 ff00::/8 31 sixxs IPv4 traceroute to the PoP endpoint: C:\>tracert 217.31.57.16 Tracing route to czprg01.sixxs.net [217.31.57.16] 1 <1 ms <1 ms <1 ms 192.168.200.1 2 <1 ms <1 ms <1 ms 10.200.236.1 3 1 ms 1 ms 1 ms 10.32.19.57 4 3 ms 2 ms 2 ms 10.200.254.25 5 2 ms 1 ms 1 ms 10.32.0.1 6 2 ms 2 ms 2 ms gw.cznet.cz [82.208.57.181] 7 10 ms 3 ms 2 ms R3N.vl94.cas.ip-anywhere.net [81.0.192.61] 8 7 ms 3 ms 3 ms nix-h.backbone.ignum.cz [91.210.16.4] 9 173 ms 2 ms 203 ms 217.31.48.90 10 3 ms 2 ms 2 ms ned.backbone.ignum.cz [217.31.48.7] 11 2 ms 3 ms 2 ms czprg01.sixxs.net [217.31.57.16] Best regards, Jakub Rimek
PoP endpoint unreachable few minutes after connect (T128030)
[ch] Jeroen Massar SixXS Staff on Tuesday, 30 July 2013 05:29:30
Tunnel Id: T128030 (AYIYA tunnel, I'm behind NAT)
What is your time setting, is it properly NTP synced?
Tracing route to czprg01.sixxs.net [217.31.57.16]
1 <1 ms <1 ms <1 ms 192.168.200.1
2 <1 ms <1 ms <1 ms 10.200.236.1
3 1 ms 1 ms 1 ms 10.32.19.57
4 3 ms 2 ms 2 ms 10.200.254.25
5 2 ms 1 ms 1 ms 10.32.0.1
Seems you are behind 2 layers of NAT, do you control both of them and are your sure they are not configured to block long standing UDP flows for instance?
PoP endpoint unreachable few minutes after connect (T128030)
[cz] Shadow Hawkins on Tuesday, 30 July 2013 17:30:55
NTP is properly synced against cz.pool.ntp.org (CET timezone) Unfortunately I don't control the NAT's. My ISP control them. I don't know about any blocking, but I'll ask the provider. What protocols and ports the AYIYA tunnel use please? Are there other users using similar tunnel on same PoP without problems? So it's probably issue on my side?
PoP endpoint unreachable few minutes after connect (T128030)
[ch] Jeroen Massar SixXS Staff on Tuesday, 30 July 2013 17:32:52
Unfortunately I don't control the NAT's. My ISP control them.
And does your "ISP" allow tunneling through those NATs?
What protocols and ports the AYIYA tunnel use please?
The AYIYA protocol on the AYIYA port. See the FAQ (firewall) for the details.
Are there other users using similar tunnel on same PoP without problems? So it's probably issue on my side?
Not that has been reported, thus yes, a problem on your side is likely.

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

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