SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #455965
Ticket Status: Invalid

PoP: nlams05 - SURFnet (Amsterdam)

No data over IPv6 tunnel as of 2006-12-07 18:47:26
[nl] Shadow Hawkins on Thursday, 07 December 2006 22:11:45
I am afraid I have to spoil the fun as I have no traffic over the tunnel to nlams05 as of 2006-12-07 18:47:26 according to Nagios. It seems to be similar to the report on #455937 If I run tcpdump on the tunnel interface I only have outgoing traffic: 22:10:52.029805 2001:610:600:2cf::2.59247 > 2001:888:10fa::12.smtp: S 801244903:801244903(0) win 4880 <mss 1220,sackOK,timestamp 2543882364 0,nop,wscale 2> 22:10:55.003964 2001:610:600:2cf::2.41598 > 2001:888:10fa::12.domain: 261 SOA? compusitter.net. (33) 22:10:55.028697 2001:610:600:2cf::2.59247 > 2001:888:10fa::12.smtp: S 801244903:801244903(0) win 4880 <mss 1220,sackOK,timestamp 2543885364 0,nop,wscale 2> 22:11:01.027785 2001:610:600:2cf::2.59247 > 2001:888:10fa::12.smtp: S 801244903:801244903(0) win 4880 <mss 1220,sackOK,timestamp 2543891364 0,nop,wscale 2> 22:11:05.194636 2001:610:600:2cf::2.59249 > 2001:888:10fa::11.ssh: S 824324160:824324160(0) win 4880 <mss 1220,sackOK,timestamp 2543895531 0,nop,wscale 2> 22:11:08.193682 2001:610:600:2cf::2.59249 > 2001:888:10fa::11.ssh: S 824324160:824324160(0) win 4880 <mss 1220,sackOK,timestamp 2543898531 0,nop,wscale 2> 22:11:14.192766 2001:610:600:2cf::2.59249 > 2001:888:10fa::11.ssh: S 824324160:824324160(0) win 4880 <mss 1220,sackOK,timestamp 2543904531 0,nop,wscale 2> 22:11:16.047923 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 0 22:11:17.047344 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 1 22:11:18.047191 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 2 22:11:19.047037 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 3 22:11:20.046884 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 4 22:11:21.046731 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 5 22:11:22.046575 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 6 22:11:23.046424 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 7 22:11:24.046272 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 8 22:11:25.046118 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 9 22:11:26.045964 2001:610:600:2cf::2 > 2001:888:10fa::12: icmp6: echo request seq 10
State change: invalid Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 07 December 2006 21:57:32
Message is Locked
The state of this ticket has been changed to invalid
No data over IPv6 tunnel as of 2006-12-07 18:47:26
[ch] Jeroen Massar SixXS Staff on Thursday, 07 December 2006 22:02:29
Read the contact page "Reporting Problems" and use the other ticket.
No data over IPv6 tunnel as of 2006-12-07 18:47:26
[nl] Shadow Hawkins on Thursday, 07 December 2006 22:09:57
Which ticket would that be? I refered to a closed ticket. And I am not used to getting any followup on closed tickets. I also could not find any reference that one should add information to closed tickets instead of opening a new ticket. And using ticket systems myself as part of my job I have found that it is in fact rather uncommon to do so. Either with our own system or any of the manufacturers I deal with. So if you have specific guidelines for this I would appreciate it they are posted so we do not have this misunderstanding. After reading the 'contact page' in full a couple of times I could not find the guidelines referring to this policy.
No data over IPv6 tunnel as of 2006-12-07 18:47:26
[ch] Jeroen Massar SixXS Staff on Thursday, 07 December 2006 22:24:38
As mentioned above the Ticket page: -------------- . When a previous ticket already exists for the same problem, post your problem in that ticket so that we can re-open the existing ticket. -------------- Which also clearly states that you need to read (and use of course) the "Reporting Problems" section on the contact page

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

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