_2.3 NTP IPv6 issue maybe?_
-
None of my interfaces have IPv6 setup, but NTP seems to be prioritizing IPv6 over IPv4
Unreach/Pending 2607:f128:1:3:: .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2607:f128::50 .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2607:f128:1:3:: .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2001:4860:4802: .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2001:4860:4802: .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2001:4860:4802: .INIT. 16 u - 512 0 0.000 0.000 0.000 Unreach/Pending 2001:4860:4802: .INIT. 16 u - 512 0 0.000 0.000 0.000
I do find it interesting that NTP worked for a short bit, but then gave up. The service claims it's running, it just can't connect to any of the servers because I don't have any IPv6.
I'm just using these servers, which do return a AAAA. They all worked fine prior to the upgrade. I have restarted PFSense a few times since the upgrade for other reasons.
a.time.steadfast.net
b.time.steadfast.net
c.time.steadfast.net
time1.google.com
time2.google.com
time3.google.com
time4.google.com -
well you must be getting something for ipv6 if its trying to talk to ipv6.. Why not just set pfsense to prefer ipv4 especially if your not going to set up ipv6 anyway.
-
I get to plug another hole in my knowledge every day. That seems to have fixed it.