NTP server issues

4o4rh

@johnpoz I have the pro version, you have the plus. You don't seem to have many of the features that i have.
Time is under System, Management, Time. But like i say, you are missing a whole bunch of stuff like switching, routing, qos, etc

johnpoz

@JKnott said in NTP server issues:

it should have got an address on my LAN

How do you know it didn't query asia.pool.ntp.org or 0.pool.ntp.org, 1.pool.ntp.org, do you have a wildcard setup?

Again any sntp client could query the ntp service that pfsense is running... It is the the ntp server that owns the internet to be honest.. Sniff the traffic.. What do you see.

4o4rh

@JKnott i removed all timeservers except for the pfsense box and i am getting TCP 66 to 52.211.208.165

JKnott

@johnpoz

While you were posting that, I checked again and it is indeed querying asia.pool.ntp.org. I don't know how I missed that before.

This is one example of where using Wireshark is better than Packet Capture. With Wireshark I can filter on both DNS and NTP at the same time, along with the MAC address, whereas Packet Capture can only filter on 1 protocol at a time, along with MAC or IP address.

Still, given that the tablets are used around the world, it would be better if they just used pool.ntp.org, instead of asia.pool.ntp.org. Using pool.ntp.org will provide a regional address.

Guess it's time for another host override.

johnpoz

yup same sort of nonsense with my smart plugs using uk.pool ;) hehehe

you can download the pcap.. Your pfsense box sure and the F is not 52.211.x.x is it??

That is a aws IP, and is not in the pool.

And I don't show it answering ntp.. And TCP is not what sntp or ntp uses.. anyway. Are you trying to say port tcp 66 to that IP? That sure and the hell has nothing to do with time. Or is the packet size... sniff on port 123 UDP.. And then open it in wireshark - attach a copy..

4o4rh

@johnpoz how can i export just the 4 ntp lines from wireshark
ntp client
ntp server
ntp client
ntp server

johnpoz

Attache the pcap.. If you sniffed on 123 and the IP of your switch all that would be in there is its query for ntp and answers.

JKnott

@johnpoz

I often filter on the MAC, to capture both IPv4 and IPv6.

johnpoz

Thats fine - is is switch running IPv6.. He made no mention of that.. Here is query from my pc to my ntp server.. That captured with pfsense

Since its routed from my lan to my segment my pi ntp server sites in.

ntp.pcap

You can download that and open in wireshark as example of ntp query and answer.

4o4rh

@johnpoz ntp_dump.pcap i notice in the two server entries, the first one is giving the address 127.0.0.1 and the second says unidentified reference source 'rate'

johnpoz

That shows that your ntp on pfsense is not in sync... Show us the status of ntp on pfsense.

Here is what typical should look like

Says right there that your clock is unsynced

So no - no clients at all should sync with that..

4o4rh

@johnpoz

johnpoz

So pfsense can not talk to any ntp servers, so no shit nobody is going to be able to sync time with it.

your reach needs to be 377... And looks like you hae those set as pool placeholders... But they prob never resolved.

example

4o4rh

@johnpoz i had the interface set to all the LAN/VLAN addresses. Now i changed it to the WAN/VPN and chugging.

johnpoz

Ok once you see it in sync.. Then your switch should sync with it... But when it is unsync like that, no ntp client would sync.

You changed it to what? Your ntp services doesn't need to listen on your wan/vpn... You mean your dns was not using your wan/vpn to resolve with?

4o4rh

@johnpoz I originally had the Listen Interface selecting only the LAN/VLANS, but not the WAN/VPNs, now i reversed it.

should i listen on both wan and vpn, or just wan?
is europe pool ntp org enough, or should i add individual country pools?
How do i know when it is in sync

stephenw10

Wait until you have entries showing reach 377 and an active peer. Check the logs.
But that looks good now.

4o4rh

@gwaitsi hmm... interesting.

if i select no interface items, it works.
if i select all the vlan/lan interfaces only, it does not work
if i select the wan/vpn interfaces only , it works
if i select the vlan interfaces only, works
if i select the lan interfaces (3) only, it does not work
if i select any one of the lan interfaces, it does not work.

So the issue seems to be with having ntp listen on a lan interface
*** So i confirmed it, if i enter the pfsense vlan address as the time server, netgear successfully updates ***

so, what can be breaking the NTP if i select the lan interfaces to listen on

4o4rh

@johnpoz @stephenw10 You can see what happens igb1.50 (vlan) is working.
Then i add a LAN interface to listen on and you see it falls over. why is the lan interface adding 0.0.0.0 instead of the lan address? this is a bug right?

4o4rh

@stephenw10 where can i find the ntp configuration files to see what is being written