Re: [chrony-users] FreeBSD: bindaddress broken in chrony 3.4

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


On Sat, Dec 01, 2018 at 02:58:58PM -0800, Danny wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233644
> >
> > 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:
> >
> > bindaddress 10.0.1.1
> >
> > 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.
> 
> Reverting "ntp: add support for IP_RECVDSTADDR and IP_SENDSRCADDR"
> fixes it for me.

It seems FreeBSD doesn't like the source address to be set on a bound
socket. It should be now fixed in git. Please let me know if it
doesn't work for you. I don't have a real multi-homed FreeBSD system
for testing.

Thanks for the report.

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/