| [chrony-users] FreeBSD: bindaddress broken in chrony 3.4 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] FreeBSD: bindaddress broken in chrony 3.4
- From: Danny <anonymous.bug.report@xxxxxxxxx>
- Date: Sat, 1 Dec 2018 14:58:58 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=2oN1mIheOGYcAIzBblfZj8PzoxRhFRZ29LXN4QPAbVM=; b=a7HW823LElpigwZUWG5s56KDDYXQ5HUhT8l3DMjqXq7cv0z6jp7ccbXth9IXP15ipR 5LD/22XQZRnyABr3l5H9wWGH84zpCFmN2s8afTfuYS3i9Qb5F//NdBH/GheHRAUklHiU PGRpH/erbRKuQiVggX/YlspOCMrCzO+JpeGKK2fYWEjhOYY2cMOP1gFs0nreQ0XyXtE3 LXu3OMon6ei4OWp32TITQnFGOJSlUzsNA9SP4gk2JRq9HZtLCWY18bA+XPe9LhB1k0sd l3TD2aQUZVAAGACfxLsP9m/h73FhymsKqsvYFeExM8Od22B4lkDmd44fp8rpw4MWSIRi hnBg==
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.
--
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.