OPNsense Forum

English Forums => General Discussion => Topic started by: meschmesch on August 17, 2023, 11:31:38 PM

Title: NTP Unreach/Pending
Post by: meschmesch on August 17, 2023, 11:31:38 PM
Hello,
NTP is not working, status unreach/pending. The log states

unable to bind to wildcard address :: - another process may be running - EXITING


Any idea to solve the problem?
Thx!!!!
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 18, 2023, 12:45:31 AM
issues with IPv6?

take a look at your routing and make sure you are able to ping the NTP servers.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 18, 2023, 11:30:21 PM
Ping is possible. Only v4. I currently have a problem with v6. I request a 61 prefix and assign ID0 ID1 etc, but for whatever reason various interfaces get assigned the same v6 subnet?

Could that be the problem?

How to solve?
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 19, 2023, 01:31:30 AM
61 is no valid. 64 or 56 should be seleted.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 19, 2023, 10:45:28 AM
The 61 prefix is pre programmed by my internet provider and until some time ago everything worked fine. Was there any change regarding that on Opnsense?
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 19, 2023, 02:35:23 PM
it's not opnsense.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 28, 2023, 08:19:23 PM
Hello, the ipv6 issue is solved. IPv6 works flawlessly now. BUT: NTP does not work yet. The protocol says:
2023-08-28T17:36:58 Notice ntpd Command line: /usr/local/sbin/ntpd -q -g -c /var/etc/ntpd.conf
2023-08-28T17:36:58 Notice ntpd ntpd 4.2.8p17@1.4004-o Tue Aug 8 02:15:10 UTC 2023 (1): Starting
2023-08-28T17:36:58 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-08-28T17:36:58 Informational ntpd initial drift restored to 0.000000
2023-08-28T17:36:58 Informational ntpd gps base set to 2023-07-30 (week 2273)
2023-08-28T17:36:58 Informational ntpd basedate set to 2023-07-27
2023-08-28T17:36:58 Informational ntpd proto: precision = 0.104 usec (-23)


My settings:

[x]  Quit NTP server immediately after time synchronisation
Interfaces: ALL
Orphan Mode 12
Maxclock 10
[x] Enable Kiss-o'-death packets
[x] Enable Rate limiting
[ ] Deny state modifications (i.e. run time configuration) by ntpq and ntpdc
[ ] Disable ntpq and ntpdc queries
[x] Disable all except ntpq and ntpdc queries
[x] Deny packets that attempt a peer association
[x] Deny mode 6 control message trap service
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 28, 2023, 08:29:12 PM
try using Chrony package and see if you see the same issue.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 28, 2023, 09:47:24 PM
Chrony works without problems. So? Use Chrony instead??!
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 29, 2023, 03:59:26 AM
Sure. I do!
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 29, 2023, 04:58:31 PM
Can I disable the NTP tool?

Nevertheless it would be interesting to know why it does not work on my machine.
Title: Re: NTP Unreach/Pending
Post by: lilsense on August 30, 2023, 09:24:58 PM
If you remove all the pools, it will stop ntp service.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on August 31, 2023, 09:47:22 AM
Works, thank you!
Title: Re: NTP Unreach/Pending
Post by: Patrick M. Hausen on August 31, 2023, 10:38:54 AM
[x] Deny packets that attempt a peer association

If you use a "pool" directive and "nopeer" at the same time ntpd cannot work.
Title: Re: NTP Unreach/Pending
Post by: meschmesch on September 01, 2023, 11:59:26 AM
Makes no difference.

Unreach/Pending 1.de.pool.ntp.org .POOL.         16 p - 64 0 0.000 +0.000 0.000
Unreach/Pending 192.168.1.1         213.239.234.28 3 u 48m 512 0 1.293 +0.043 0.000
Title: Re: NTP Unreach/Pending
Post by: meschmesch on September 04, 2023, 02:23:03 PM
Update: under access restrictions is deselected "Disable all except ntpq and ntpdc queries". Now the result is still unreach/pending for the pool, but it seems to work for "content" of the pool, even though I have no idea what ".PZFs." means (and I don't have GPS).

Unreach/Pending 0.de.pool.ntp.org               .POOL. 16 p - 64 0 0.000 +0.000 0.000
Unreach/Pending 1.de.pool.ntp.org               .POOL. 16 p - 64 0 0.000 +0.000 0.000
Candidate 213.209.109.45                 10.129.9.96 2 u 28 64 377 18.335 -0.258 3.273
Active Peer 131.188.3.223                  .PZFs. 1 u 29 64 377 17.491 +0.860 2.054
Candidate 49.12.125.53               131.188.3.222 2 u 27 64 377 18.710 +1.093 2.421
Candidate 85.214.127.75               208.90.67.116 3 u 26 64 377 24.587 +0.649 3.101
Candidate 193.203.3.170                             .GPS. 1 u 33 64 377 25.712 -1.734 3.365
Candidate 85.215.93.134               192.53.103.108 2 u 22 64 377 25.651 -0.275 0.987
Candidate 91.107.199.28               36.224.68.195 2 u 32 64 377 19.211 +0.997 1.131
Candidate 81.169.199.94               161.143.24.141 2 u 22 64 377 25.849 +2.366 2.736


All very strange.
Title: Re: NTP Unreach/Pending
Post by: CJ on September 05, 2023, 02:58:50 PM
IIRC, the third column is telling you where that particular time server is getting it's time from.  Not familiar with PZFs though.