[ntp:questions] offline machines' time synchronization

Ali Nikzad nikzad.a at gmail.com
Thu May 24 03:22:47 UTC 2012


thanks for your answers.

I am using Ubuntu operating system and the IP addresses are assigned
manually and they are fixed. I also disabled the firewalls of both systems.

I changed the Files as follows:

#ntp.conf
#ip: 192.168.17.11
driftfile /etc/ntp.drift
tos cohort 1 orphan 11
restrict source nomodify
restrict default kod notrap nomodify nopeer noquery
restrict 127.0.0.1

#ntp.conf
#ip: 192.168.17.22

driftfile /etc/ntp.drift
server 192.168.17.11
tos cohort 1 orphan 11
restrict source nomodify
restrict default kod notrap nomodify nopeer noquery
restrict 127.0.0.1

But they are still not synchronized.
I should use the orphan mode since they are not connected to any external
servers but there should be a problem that they can't be synced.

Thanks,
Ali


On Wed, May 23, 2012 at 5:55 PM, E-Mail Sent to this address will be added
to the BlackLists <Null at blacklist.anitech-systems.invalid> wrote:

> David Woolley wrote:
> > BlackList wrote:
> >>
> >> Add to both?:
> >>  tos cohort 1 orphan 11
> >>  restrict source nomodify
> >>
> > If he's offline to the ubuntu server, won't that, effectively,
> >  make both server lines redundant,
> >  or does orphan require a token server.
>
> If (#ip: 192.168.17.11) can't reach ntp.ubuntu.com ever,
>  having "server ntp.ubuntu.com" in the conf is obviously useless.
>
>
> > One problem I see is that there is no guarantee which machine will
> >  be the master in the relationship.
>
> <http://www.eecis.udel.edu/~mills/ntp/html/orphan.html>
>
>
> {He didn't mention using any automatic server discovery
>  pool / manycast / multicast / broadcast / anycast / ... in his conf.}
>
> If he is not using any Automatic Server Discovery,
>  the (#ip: 192.168.17.22) client conf,
>  would need the "server 192.168.17.11" line ?
>
>
> (#ip: 192.168.17.11) doesn't know about (#ip: 192.168.17.22),
>  if it ever gets to talk to "server ntp.ubuntu.com",
>  so much the better; if not, it should chug along on its own.
>
> (#ip: 192.168.17.22) has "server 192.168.17.11" in the conf
>  it should follow (#ip: 192.168.17.11) {"the master"}
>
>
> >> and start ntpd with?: -g
>
> So, if when ntp is started,
>  if the offset between the client (#ip: 192.168.17.22)
>  and server (#ip: 192.168.17.11) exceeds the panic threshold,
>   ntp will step the client #ip: 192.168.17.22)
>    to match the server (#ip: 192.168.17.11),
>   instead of exiting.
>
>
> --
> E-Mail Sent to this address <BlackList at Anitech-Systems.com>
>  will be added to the BlackLists.
>
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions
>


More information about the questions mailing list