OPNsense Forum

Archive => 23.1 Legacy Series => Topic started by: Kornelius777 on March 15, 2023, 01:18:15 PM

Title: [SOLVED] Issue with Network Time
Post by: Kornelius777 on March 15, 2023, 01:18:15 PM
Dear all,

on my LAN, I run two Stratum-1-clocks which I wish to use as the Time Source for my OPNSense Firewall.
Having added them to "Services --> Network Time --> General" results in "Unreach/Pending" on the Status Page.

Will I need to add anything on the Firewall to enable this setting?
I'm confused.

Would anyone be so kind as to share their thoughts with me?
Title: Re: Issue with Network Time
Post by: bartjsmit on March 15, 2023, 01:22:02 PM
Are you using the internal IP addresses of your time anchors? Do both respond to ping?

Bart...
Title: Re: Issue with Network Time
Post by: CJ on March 15, 2023, 01:22:14 PM
How long since you added them?  It can take a little while for the status to update.
Title: Re: Issue with Network Time
Post by: Kornelius777 on March 15, 2023, 01:41:03 PM
root@OPNsense:~ # ping 192.168.150.72
PING 192.168.150.72 (192.168.150.72): 56 data bytes
64 bytes from 192.168.150.72: icmp_seq=0 ttl=64 time=0.344 ms
64 bytes from 192.168.150.72: icmp_seq=1 ttl=64 time=0.243 ms
^C
--- 192.168.150.72 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.243/0.293/0.344/0.051 ms


I probably added them some 30 minutes ago. However, the Time Source doesn't report OPNsense as a client ("chronyc clients") and the status is still "Unreach/Pending".

For testing, I even set chrony.conf to "allow 0.0.0.0/0"
No success, so far....
Title: Re: Issue with Network Time
Post by: Kornelius777 on March 15, 2023, 01:49:18 PM
As usual, the mistake was 40 cm in front of the screen...

Of course, I had to check "LAN" on the interfaces drop down list.

Sorry for bothering you...