SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3945785
Ticket Status: Resolved

PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)

dedus01 pop doesnt react to ping6 2a01:198:200:828::1
[de] Shadow Hawkins on Monday, 21 March 2011 14:10:19
Does happen quite often with this pop: 1) aiccu start works ok, giving: Tunnel Information for T26397: POP Id : dedus01 IPv6 Local : 2a01:198:200:828::2/64 IPv6 Remote : 2a01:198:200:828::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started 2) my local ipv6 pings ok 3) remote ipv6 does not answer, routing etc does not work: # ping6 2a01:198:200:828::1 PING 2a01:198:200:828::1(2a01:198:200:828::1) 56 data bytes --- 2a01:198:200:828::1 ping statistics --- 17 packets transmitted, 0 received, 100% packet loss, time 16007ms 4) A traceroute via another ipv6 tunnel to the remote ipv6: # traceroute6 2a01:198:200:828::1 traceroute to 2a01:198:200:828::1 (2a01:198:200:828::1) from 2001:6f8:1c9c::a01:101, 30 hops max, 16 byte packets 1 gw-330.ham-02.de.sixxs.net (2001:6f8:1c00:149::1) 45.319 ms 41.159 ms 37.865 ms 2 2001:6f8:800:1003::209:55 (2001:6f8:800:1003::209:55) 40.019 ms 38.616 ms 37.875 ms 3 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 39.939 ms 40.762 ms 39.855 ms 4 2001:6f8:1:0:87:86:77:67 (2001:6f8:1:0:87:86:77:67) 39.936 ms 37.693 ms 39.872 ms 5 2001:6f8:1:0:86:87:77:81 (2001:6f8:1:0:86:87:77:81) 39.929 ms 39.601 ms 39.865 ms 6 2001:6f8:1:0:87:86:77:83 (2001:6f8:1:0:87:86:77:83) 40.924 ms 40.742 ms 41.868 ms 7 2001:6f8:1:0:86:87:77:95 (2001:6f8:1:0:86:87:77:95) 55.936 ms 52.726 ms 53.863 ms 8 2001:6f8:1:0:87:86:77:71 (2001:6f8:1:0:87:86:77:71) 189.947 ms 54.789 ms 55.841 ms 9 2001:6f8:1:0:87:86:77:249 (2001:6f8:1:0:87:86:77:249) 53.901 ms 55.85 ms 55.813 ms 10 decix.r1.fra3.opencarrier.eu (2001:7f8::a2dc:0:1) 57.825 ms 54.19 ms 67.878 ms 11 oc-fra.dus.speedpartner.de (2001:7f8:3a:e102::2) 51.9 ms 52.271 ms 51.849 ms 12 dedus01.sixxs.net (2a01:198:200::2) 53.898 ms !N 58.404 ms !N 59.906 ms !N Hu??? 2a01:198:200::2 is supposed to be MY ipv6 address? :S Basically, every tracepath6 to 2a01:198:200::???? is answered from 2a01:198:200::2 ... And quite often, without any changes on my side, after a while it works again for some time, mostly some days (not sure about week or longer). Hope you can use this report, if problem is on my side, please give me a hint to solve it. Thank you, regards, Lutz Stohlmann
dedus01 pop doesnt react to ping6 2a01:198:200:828::1
[de] Shadow Hawkins on Monday, 21 March 2011 14:13:40
4) ... Sorry for 4) ... my mistake, did not read correctly. Regards!
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 21 March 2011 16:41:41
Message is Locked
The state of this ticket has been changed to user
dedus01 pop doesnt react to ping6 2a01:198:200:828::1
[ch] Jeroen Massar SixXS Staff on Monday, 21 March 2011 16:43:43
When the PoP does not respond to the pop-side address of the tunnel (in your case 2a01:198:200:828::1) then it means the tunnel is not up.
Hu??? 2a01:198:200::2 is supposed to be MY ipv6 address? :S
That is because your tunnel is not up, then the PoP replies with !N which means "no route".
Basically, every tracepath6 to 2a01:198:200::???? is answered
from 2a01:198:200::2 .
What exactly are you trying to do?

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

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