SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #14781685
Ticket Status: User

PoP: ruled01 - EDPnet N.V. (St.Petersburg)

No IPv6 connectivity
[ru] Shadow Hawkins on Wednesday, 06 January 2016 07:02:32
Tunnels T147509, T154381, T158717. Starts without error messages: sock_getline() : "200 SixXS TIC Service on nlhaa01.sixxs.net ready (https://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/3.13.0-74-generic" .... sock_getline() : "202 Done" Successfully retrieved tunnel information for T147509 sock_printf() : "QUIT Zij die gaan, groeten u" Tunnel Information for T147509: POP Id : ruled01 IPv6 Local : 2a02:578:5002:174::2/64 IPv6 Remote : 2a02:578:5002:174::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started But then remote tunnel endpoint cannot be pinged: ping6 2a02:578:5002:174::1 PING 2a02:578:5002:174::1(2a02:578:5002:174::1) 56 data bytes ^C --- 2a02:578:5002:174::1 ping statistics --- 360 packets transmitted, 0 received, 100% packet loss, time 359186ms Problem started yesterday about 19:00MSK (partial connectivity loss) and now ipv6 connectivity lost completely.
No IPv6 connectivity
[ru] Shadow Hawkins on Wednesday, 06 January 2016 15:40:27
Roman Bazalevskiy wrote:
Starts without error messages:
I think I've met the same issue. My tunnel id is T133610. Some investigation shows me that it's something regarding time on the PoP. Roman, do you have a lot of recent "Clock off" errors in "Live tunnel status on PoP"? ( https://www.sixxs.net/home/tunnelinfo/status/?<your tunnel id> ) _My host clock is synced using NTP. And I have correct Europe/Moscow timezone from timezone-data-2015f. _ # ntpdate -u europe.pool.ntp.org 6 Jan 18:32:36 ntpdate[10484]: adjust time server 91.121.192.17 offset -0.008627 sec When IPv6 connection starts to fail I can fix it setting the clock to the past but not far away - 30-50 seconds and after restarting the aiccu IPv6 connection starts to work. After it I can sync time to correct value or not, restart aiccu or not the same - IPv6 connection works for some time (few minutes) then stops with the same symptoms. May be it's aiccu issue. I use aiccu-2007.01.15 on gentoo amd64.
No IPv6 connectivity
[ru] Shadow Hawkins on Wednesday, 06 January 2016 19:56:15
Semen Nikiforov wrote:
When IPv6 connection starts to fail I can fix it setting the clock to the past but not far away - 30-50 seconds and after restarting the aiccu IPv6 connection starts to work. After it I can sync time to correct value or not, restart aiccu or not the same - IPv6 connection works for some time (few minutes) then stops with the same symptoms.
The same, yes :( Some time ago I've got problems with out-of-sync time on PoP (TT 14227737).
No IPv6 connectivity
[ru] Shadow Hawkins on Friday, 08 January 2016 21:03:09
My problem seems to be fixed for now.
No IPv6 connectivity
[ru] Shadow Hawkins on Monday, 11 January 2016 07:31:00
Semen Nikiforov wrote:
My problem seems to be fixed for now.
My too. Looks like ntp time sync is not configured on POP :(
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 10 January 2016 21:23:08
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