Kurt Roeckx wrote:
On Mon, Nov 27, 2006 at 11:18:15PM +0100, Olaf van der Spek wrote:
The NTP protocol uses UDP. If a client sends a packet to a server,
it expects to get a response from the same IP address back. This
creates problems for systems with multiple IP addresses. Since there
is no API to get the IP address a packet was send to, it binds to every
IP address it finds when starting (and to the wildcard address). So
depending on the socket, it knows which address it was send too.
Isn't this only an issue for NTP servers and not for clients? I know the
daemon implements both, but when you don't use it as server it shouldn't
experience this issue.
It's the client that stops working. And it's probably a regression.
So that's no longer an argument to prefer the periodic ntpdate instead
of the daemon, assuming it gets fixed?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
