I suggest that routed be specified as being BEFORE ntpd. In the absence
of a route to the specified servers, ntpd has the annoying behavior of
chosing the address of lo0 as the source address for ntp requests,
resulting in all sorts of problems.
This wouldn't happen in configurations with defaultrouter, but for those
depending on dynamic routing...
Of course, most dynamic routing protocols require a certain time before
it goes to a stable state and install the externally received routes,
but _that_ I solved with a sleep in the zebractl script (zebra being the
router I use).
I do see one contraindication to this behavior. Most routing protocols
also react badly to time changes. Egg and chicken problem, but,
personally, and running OSPF, which is one of those protocols that react
badly to time changes, I find it preferably to run the router first.
After all, having ntpd using 127.0.0.1 as source is useless to me.
--
Daniel C. Sobral (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
TCO
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Outros:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Q: How did you get into artificial intelligence?
A: Seemed logical -- I didn't have any real intelligence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- Re: RC NG, ntp and routed Daniel C. Sobral
- Re: RC NG, ntp and routed Brad Knowles
- Re: RC NG, ntp and routed Mike Makonnen
- Re: RC NG, ntp and routed Gordon Tetlow
- Re: RC NG, ntp and routed Daniel C. Sobral
- Re: RC NG, ntp and routed Mike Makonnen
- Re: RC NG, ntp and routed Gordon Tetlow
- Re: RC NG, ntp and routed Mike Makonnen
- Re: RC NG, ntp and routed Gordon Tetlow
- Re: RC NG, ntp and routed Doug Barton
- Re: RC NG, ntp and routed Brad Knowles