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

[Danny]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233644

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.

[Miroslav Lichvar]

Post by Danny
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233644

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.

[Bernhard Fröhlich]

Post by Miroslav Lichvar

Post by Danny
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233644

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.

I've applied commit 6af39d63aa9323b4b8c39efe24ae0c88c949a901 on our FreeBSD
port for chrony 3.4 and it works fine again. Thanks a lot!
--
Bernhard Fröhlich
http://www.bluelife.at/