Time is not syncing

NogBadTheBad

Try using:-

0.pool.ntp.org to 3.pool.ntp.org

Does it then sync ?

"NTP will only sync if a majority of the servers agree on the time. For best results you should configure between 3 and 5 servers (NTP support pages recommend at least 4 or 5), or a pool. If only one server is configured, it will be believed, and if 2 servers are configured and they disagree, neither will be believed. Options:
Prefer - NTP should favor the use of this server more than all others.
No Select - NTP should not use this server for time, but stats for this server will be collected and displayed.
Is a Pool - this entry is a pool of NTP servers and not a single address. This is assumed for *.pool.ntp.org."

johnpoz

Well that is not working since its not even resolving any hosts in the pool. So it doesn't even know to ask any ntp server for time.

See how I have a placeholder, and then IPs listed under that.

I would validate that pfsense is able to resolve.. You can use the dns lookup tool under diag to check if pfsense can resolve that FQDN.. See example below

brunovic

@NogBadTheBad I've already done that too with the same results.

johnpoz

Ok so your resolving, but ntp not able to reach or is not resolving? Place a specific IP in there vs FQDN.

What do you have listed for interface that ntp is listening on? There was a recent there were a user was seeing a problem that ntp could not query unless they selected the wan interface. Even though that should not be required, unless you had maybe messed with your outbound nat.

Are you trying to force all traffic through a vpn? your doing something odd with pfsense dns for sure since the only IP listed in pfsense for using the unbound resolver is the loopback, like you see in my output. But your also listing opendns.

brunovic

@johnpoz I am not sure why 0.north-america.pool.ntp.org was cut off in the Status/NTP section but it was configured correctly in the NTP config and it resolves perfectly fine.

NogBadTheBad

@brunovic

[2.4.3-RELEASE][admin@pfsense]/root: ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.pool.ntp.org  .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.pool.ntp.org  .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.pool.ntp.org  .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.pool.ntp.org  .POOL.          16 p    -   64    0    0.000    0.000   0.000
-2a01:7e00::f03c 85.199.214.98    2 u  334  512  377   10.483   -0.018   0.166
+185.182.62.7    85.199.214.102   2 u   92  512  377    9.679   -0.223   0.409
*87.242.168.84   .UPPS.           1 u  133  512  377   20.003    0.220   0.106
-2001:1b40:5000: 188.39.213.7     2 u  324  512  377   10.234    2.004   0.296
-83.137.225.103  193.190.230.66   2 u  199  512  377   10.425    0.849   0.296
+188.39.213.7    .GPS.            1 u  432  512  377   16.887    0.036   4.039
[2.4.3-RELEASE][admin@pfsense]/

Works fine here, I know thats not of any help.

brunovic

These are the results when I put the IP addresses directly in. Where do I find out what interface NTP is listening on?

beremonavabi

Here's a link to my thread (that johnpoz mentioned) on the same problem:

https://forum.netgate.com/topic/131506/ntp-not-working-solved-mostly

For me, I have to have WAN selected under Services > NTP in the Interfaces section. I've been utterly unable to find any reason for this since it shouldn't be necessary.

brunovic

@beremonavabi said in Time is not syncing:

Here's a link to my thread (that johnpoz mentioned) on the same problem:

https://forum.netgate.com/topic/131506/ntp-not-working-solved-mostly

For me, I have to have WAN selected under Services > NTP in the Interfaces section. I've been utterly unable to find any reason for this since it shouldn't be necessary.

This solution worked for me. Thank you.

beremonavabi

@brunovic
I don't like having my WAN selected for NTP to listen to. But, since that's the only way I've found to be able to get NTP to run, I guess I have to live with it.

NogBadTheBad

@beremonavabi

Does it now work ?

You both shouldn't need to have it listening on the WAN interface.

brunovic

@johnpoz so it looks like my outbound NAT is manually configured. How will this prevent NTP from syncing?

beremonavabi

@nogbadthebad said in Time is not syncing:

@beremonavabi

Does it now work ?

You both shouldn't need to have it listening on the WAN interface.

NTP will ONLY run on my SG-4860 if WAN is selected to listen to (the gory details of everything I've tried are in the thread I referenced, above). I agree that the WAN shouldn't be necessary. But, for no reason I can come up with, it turns out to be necessary in my case.

Looking over some of brunovic's other posts, it looks like he's using a VPN. I am, too. It's possible that's a relationship, but I just don't see why using a VPN might interfere with NTP.

brunovic

@beremonavabi I use a VPN for remote access into my network but not for outbound traffic. Is that how you are using it?

NogBadTheBad

@beremonavabi said in Time is not syncing:

@nogbadthebad said in Time is not syncing:

@beremonavabi

Does it now work ?

You both shouldn't need to have it listening on the WAN interface.

NTP will ONLY run on my SG-4860 if WAN is selected to listen to (the gory details of everything I've tried are in the thread I referenced, above). I agree that the WAN shouldn't be necessary. But, for no reason I can come up with, it turns out to be necessary in my case.

Looking over some of brunovic's other posts, it looks like he's using a VPN. I am, too. It's possible that's a relationship, but I just don't see why using a VPN might interfere with NTP.

I run a IKEv2 IPsec VPN ( inbound ) too I've got Automatic outbound NAT rule generation set.

beremonavabi

@brunovic I've got OpenVPN clients running on my pfSense box to my VPN provider (AirVPN). I've also got a server running on it so our phones can use the VPN.

brunovic

@beremonavabi ah no I am not using the client on my pfsense just the server.

beremonavabi

@brunovic said in Time is not syncing:

@beremonavabi ah no I am not using the client on my pfsense just the server.

Well, an OpenVPN server commonality might be a start. Mine is listening on port 443. My firewall rules on the WAN look like:

0_1528994663634_20180604 -- Firewall Rules WAN.PNG

Like you, my NAT rules are Manual. Outside of your specific ports, mine look similar:

0_1528994721603_20180610 -- pfSense Firewall NAT Outbound.PNG

For DNS, I’m using DNS Resolver in NON-Forwarding mode. It’s active for all my local LAN-type interfaces (not WAN). Though, since I've checked with NTP using actual IP addresses instead of pool names (as you did), I can't see how this could be DNS related.

johnpoz

@beremonavabi said in Time is not syncing:

NTP will ONLY run on my SG-4860 if WAN is selected to listen

I have sg4860, I run both vpn servers on multiple instances 443 tcp, 1194 udp and also a vpn client connection to a vps out on the net running openvpn-as..

But I am NOT pulling routes from that connection and only policy route out to that vpn if need a client to take that path.. And I am NOT listening on the wan port and have zero issues with ntp talking to outbound ntp per previous screen shots.

So you clearly have something messed up in your configuration causing this problem there is zero reason that ntp should have to listen on wan to talk to ntp servers on the internet.