Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Nov 2002 08:43:40 -0200
From:      "Daniel C. Sobral" <dcs@tcoip.com.br>
To:        "Daniel O'Connor" <doconnor@gsoft.com.au>
Cc:        current@FreeBSD.ORG
Subject:   Re: Problem with ntpdate
Message-ID:  <3DE744DC.5030201@tcoip.com.br>
In-Reply-To: <3DE667DF.9060200@tcoip.com.br>
References:  <3DE667DF.9060200@tcoip.com.br>  <3DE66E2E.7050201@tcoip.com.br> <1038523933.21586.2.camel@chowder.gsoft.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Connor wrote:

> On Fri, 2002-11-29 at 05:57, Daniel C. Sobral wrote:
>
> >ntpdate_flags="-s -b 200.220.255.229":
> >
> >Nov 28 15:15:38 dcs ntpdate[259]: no server suitable for synchronization
> >found
> >Nov 28 15:15:39 dcs ntpd[377]: ntpd 4.1.1b-a Thu Nov 28 11:09:29 BRST
> >2002 (1)
> >Nov 28 15:15:39 dcs ntpd[377]: kernel time discipline status 2040
> >Nov 28 15:15:50 dcs ntpd[377]: sendto(200.220.255.229): No route to host
> >
> >That is, the extra time taken NOT resolving clock.tcoip.com.br was,
> >apparently, enough for something in the IP stack to go up.
> >
> >This looks, after all, like a more serious bug than I first assumed.
>
>
> You could try running FreeBSD so that it thinks the CMOS clock is local
> time the same as windows does..
>
> Have you tried ntpdate debugging?
>
> ntptrace can be handy too..
> (Although if it works after boot then probably not)
>
> I see the 'no route to host message' given by ntpd - perhaps some routes
> aren't set when ntpdate runs?

Not a FreeBSD problem, after all. I checked the interfaces, checked the 
routes, and then I finally got a tcpdump running. Seems like for some 
switching reason the arp who-has packets are taking too long to be 
properly propagated.

Now, I seem to recall there were some tcp delay changes between 4.x and 
5.x, so now 5.x is much faster. Apparently, so much so it gives up 
before I get an arp is-at, whereas 4.x would wait enough for the link 
level protocolo to get it's act together.

Or maybe 4.x tried to use something before running ntpdate, so that the 
arp table was ok by the time it got to ntpdate.

Or maybe both. <shrug>

I'll try using the -g option on ntpd like someone else suggested.

-- 
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: Daniel.Capo@tco.net.br
         Daniel.Sobral@tcoip.com.br
         dcs@tcoip.com.br

Outros:
	dcs@newsguy.com
	dcs@freebsd.org
	capo@notorious.bsdconspiracy.net

Ankh if you love Isis.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DE744DC.5030201>