I currently got the problem that I can´t add any server with an IPv6 adress, which is part of T-Systems (German Telekom). e.g. If I try to add 2003:a:47f:abe4::1 to the pool, the monitoring/probe will not get a valid response and does not allow to add it to the pool. Same is true for e.g. 2003:a:1…

per traceroute man page: “!N means network unreachable” 2003:0:1504:e400::2 is Deutsche Telecom. You should ask your ISP for help. IPv6 routing problems are not rare.

Hi @kashra and welcome. I’ve put the first address into two different “try my NTP server” sites and they both report connectivity ok. What output does “mtr --udp -P 123 2604:1380:2:6000::15” give you? (traces route over UDP port 123 to the monitoring server)

It does output this error: mtr: mtr-packet reported invalid argument I tried using regular ICMP probes, which work just fine, but mtr does not send udp probes at all. I tried several machines with several linux flavors on them like Ubuntu server 18.04, 19.10 and 20.10 IPv6 however is configured …

Hi, I did some digging in the code for the error message you get when trying to add the server and the pool code appears to be calling this url: https://trace2.ntppool.org/ntp/2003:a:157f:b76d::2 Which returns this error: {“Op”:“read”,“Net”:“udp”,“Source”:{“IP”:“2604:1380:2:6000::15”,“Port”:59995…

Well, the problem is, the servers worked just fine in the past, up to beginning of Feb. 2020 and stopped working all at once, with no changes made to the config for over a year by now. In addition to that my other servers are syncing to them just fine + they are in active production use with my cus…

Three NTP servers in 2003:a::./32 stopped responding to the Newark montior’s NTP queries at about the same time: 2020-01-28 10:18. They are still unreachable from Newark. traceroute6 can only probe up to telia: 1 gateway (2604:1380:2:6000::14) 71.010 ms 70.963 ms 70.915 ms 2 0.xe-0-0-17.…

I’ve asked Packet if it’s possible for them to route this a different path than Telia, too. It’s sorta nice to for once have an obvious and clear cut (I hope) routing problem rather than the random packet drops. :slight_smile:

Not able to add new server: IPv6 2003🅰47f:abe4::1

Server operators

Kashra May 20, 2020, 1:06am 7

It shows:

trace6

Topic		Replies	Views
Unable to join pool: IPv4 fails, IPv6 OK, external tests pass Server operators monitoring	16	791	February 10, 2023
I want to add my NTP server. But I can't Server operators	11	1165	August 5, 2022
Can't re-add a server with its new IPv6 Server operators	9	682	May 10, 2024
Monitoring station routing problems Server operators	10	1094	July 13, 2019
Difficulties adding IPv6 server with chronyd to the pool Server operators	6	1831	August 4, 2018

Not able to add new server: IPv6 2003🅰47f:abe4::1

Related topics