Subject: Re: bin/6897: xntpd interfaces alias bug
To: None <email@example.com>
From: Wolfgang Rupprecht <firstname.lastname@example.org>
Date: 01/28/1999 11:55:08
email@example.com (Manuel Bouyer) writes:
> On Jan 28, Geoff Wing wrote
> > Weird, has worked OK for me for a couple of years, two network cards,
> > multiple aliases on each.
> I think it doesn't work only in broadcast mode (at last I can't
> start xntpd -b on my www server).
> I'll try this and see if it solves my problem.
I'm also seeing the problem in unicast mode if broadcast is also
enabled (in a belt-and-suspenders fashion).
I don't yet understand the code well enough to know what important
data is getting stepped on by the duplicate interface initialization.
More is happening than just the exit() call after the failed bind().
That exit() is easy enough to comment out, and is in fact what ntp-4.x
does right out of the box.
In my unicast+broadcast case, tcpdump shows absolutely no packets
being emitted for the local network (neither unicast nor broadcast).
Tcpdump does show all the packets addressed to external hosts though.
Wolfgang Rupprecht <firstname.lastname@example.org>
Get DGPS signals over IP. http://www.wsrcc.com/wolfgang/gps/dgps-ip.html