SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #719435
Ticket Status: User

PoP: 

T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Thursday, 01 May 2008 17:03:29
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: - The tunnel T14096 worked for many weeks without issue but starting Today afternoon, the remote IP (2001:6f8:202:264::1) of the tunnel is not responding any more. - On the tun interface, there is no RX packet (aiccu was restarted)): sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::4f8:202:264:2/64 Scope:Link inet6 addr: 2001:6f8:202:264::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:210796 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:19621517 (18.7 MiB) - The tunnel seems to be established correctly : May 1 16:53:15 sqrte aiccu: TIC Server does not support TLS but TLS is not required, continuing May 1 16:53:15 sqrte aiccu: Succesfully retrieved tunnel information for T14096 May 1 16:53:15 sqrte aiccu: AICCU running as PID 25728 May 1 16:53:15 sqrte kernel: sixxs: Disabled Privacy Extensions May 1 16:53:15 sqrte aiccu: [AYIYA-start] : Anything in Anything (draft-02) May 1 16:53:15 sqrte aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started - I correctly receive the routing information pointing to the remote tunnel end : default via 2001:6f8:202:264::1 dev sixxs metric 1024 expires 21334271sec mtu 1280 advmss 1220 hoplimit 4294967295 - a tcpdump on sixxs shows clearly all the packet from my allocated subnet going to the tunnel but there is no packet IN (RX). - The operating system is still routing other IPv6 networks. (IPv6 stack works) - aiccu test is stopping on test 6/8 - IPv6 Remote/PoP Inner Tunnel Endpoint (as explained before). Is there a known issue for this tunnel ? Thanks for any feedback, Kind regards,
T14096 - remote tunnel not responding any more
[ch] Jeroen Massar SixXS Staff on Thursday, 01 May 2008 20:14:27
Why are you sending massive amounts of garbage like: ?
IP6 2001:6f8:370:200::11.18806 > 2001:7b8:3bf:1:219:99ff:fe04:511e.7078: UDP, length 45 0x0000: 6000 0000 0035 113f 2001 06f8 0370 0200 `....5.?.....p.. 0x0010: 0000 0000 0000 0011 2001 07b8 03bf 0001 ................ 0x0020: 0219 99ff fe04 511e 4976 1ba6 0035 9063 ......Q.Iv...5.c 0x0030: 8003 4ea1 2a7a bbe0 0519 bc3e d820 a2e1 ..N.*z.....>.... 0x0040: 5a50 0049 2492 4924 5000 4924 9249 2450 ZP.I$.I$P.I$.I$P 0x0050: 0049 2492 4924 5000 4924 9249 24 .I$.I$P.I$.I$
Repeated and repeated and repeated. Doesn't seem to be a useful way of using IPv6 connectivity provided by us to me.
T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Friday, 02 May 2008 11:43:12
Thanks for bringing back the tunnel. The 2001:6f8:370:200::11 is generating an RTP stream. But the consumer of the RTP stream is using another SixXS client but allocated to another SixXS POP. Sorry for the inconvenient but we were wondering what's the preference at SixXS team regarding the bandwidth use between SixXS client on the same POP and different POP ? Thanks a lot for your support
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 01 May 2008 20:13:41
Message is Locked
The state of this ticket has been changed to user
T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Monday, 19 May 2008 19:16:16
Dear, The tunnel T14096 has no more RX packets. The problem is similar to this tickets-719435. The recent traffic was pretty standard and the volume was quite low. Have you packet filtered the tunnel T14096 ? Thanks for your feedback, Kind regards,
T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Friday, 23 May 2008 07:24:44
Could you reopen the ticket ? The issue is similar and the tunnel T14096 seems packet filtered. Thanks for your feedback,
T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Thursday, 26 June 2008 13:45:02
Could you reopen the ticket ? Starting Today beginning afternoon similar issue happens with the same tunnel. Thanks.
T14096 - remote tunnel not responding any more
[be] Shadow Hawkins on Thursday, 26 June 2008 16:08:46
Connectivity is back to normal. Thanks.

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

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