On Thu, 3 May 2007, mark kraitchman wrote: > We just received an an explanation as to why some of the > Roulette testbed nodes on the 128.32.130.0/25 were making > requests to NTP servers outside Berkeley: > > "For some reason the ntpd on the embedded linux was working with a > predefined host list and was ignoring /etc/ntp.conf unless it > was explicitly included on the ntpd command line. They're now all > configured to query only the ntpd on the local router." > > mark kraitchman (for [EMAIL PROTECTED]) > _______________________________________________ > timekeepers mailing list > [email protected] > https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers >
Hello, I suggested the following several times but nobody seems to pay attention. I suggest that your outgoing router catches all outgoing requests to ntp and redirects them to itself. This way, you do not have to configure all your devices manually like you seem to have done. As a bonus, you get 100% of the requests handled by your router not just the requests from devices properly configured. If your router redirects the requests to itself, it doesn't matter anymore which hosts are configured within the devices. Anybody ? Anything wrong with what I am suggesting ?? If not, why isn't anybody else seeming to be doing or recommending this ? Could catching udp 123 outgoing request interfere with other applications ? IMHO, that's what a router is for I guess, to route requests according to rules that we specify. I take advantage of that for LAN ntp configuration and I do not worry how the devices and hosts inside LANs are configured because it doesn't matter anymore if you catch the ntp requests. I have never seen interference with other applications doing this. Cheers, Louis http://www.oc9.com _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
