Bug 233644 - net/chrony: After 3.4 update, chronyd server listener broken when bindaddress set in chrony.conf
Summary: net/chrony: After 3.4 update, chronyd server listener broken when bindaddress...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs mailing list
Keywords: needs-qa, regression
Depends on:
Reported: 2018-11-29 18:30 UTC by ddrinnon
Modified: 2018-12-05 22:19 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (yonas)

upstream patch (2.83 KB, patch)
2018-12-04 00:38 UTC, Colin T.
koobs: maintainer-approval? (yonas)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description ddrinnon 2018-11-29 18:30:53 UTC
It seems the latest update to net/chrony 3.4 has broken the chronyd server if the chrony.conf option bindaddress is set, such as:


If the bindaddress is commented out, then time clients can get time from the chronyd server, but then that opens up the port on all interfaces on a multi-homed server.
Comment 1 Morgan Vandagriff 2018-11-30 18:20:22 UTC
I can confirm. Seeing the same thing. It's a real problem on a host with multiple jails, as chrony on the host is now listening on all jail IPs.
Comment 2 Colin T. 2018-12-04 00:38:26 UTC
Created attachment 199807 [details]
upstream patch

Does this patch fix it for you guys?
Comment 3 ddrinnon 2018-12-04 14:25:59 UTC
The patch fixes it for me.  Thank you!

[root@gateway01 /usr/local/etc]# sockstat -4|more
chronyd  chronyd    20582 5  udp4          *:*

[root@aux01 ~]# ntpdate
 4 Dec 07:25:07 ntpdate[19211]: adjust time server offset 0.002788 sec

[root@aux01 ~]# chronyc sources
210 Number of sources = 4
MS Name/IP address         Stratum Poll Reach LastRx Last sample
^* gateway01.cdor.net            2   9   377   349   +310us[ +310us] +/-   30ms
Comment 4 Morgan Vandagriff 2018-12-05 22:19:36 UTC
(In reply to Colin T. from comment #2)

The patch works great! Thanks so much.