> Clifton Royston wrote:
> > You're not getting responses back from __any__ of those NTP servers. If
> > you have a firewall *in front* of your BSD box (meaning a separate box,
> > not ipfw/ipfilter/pf on the same BSD box!), then this is likely the
> > cause of the problem.
I really agree with you
Firstly, thank all of you for supporting me!
But please note that I shall install FreeBSD 7.0-RELEASE this weekend.
So I can no longer give you more information regarding 6.3-STABLE.
Secondly I'm sorry for confusing you (NAT: I mean the machine ``behind NAT.'')
> > 1. FreeBSD 5.4-RELEASE(dial up)
> You're not getting responses back from __any__ of those NTP servers. If
> you have a firewall *in front* of your BSD box (meaning a separate box,
> not ipfw/ipfilter/pf on the same BSD box!), then this is likely the
> cause of the problem.
The question is that two weeks ago, with same machine, s
> This isn't enough time. Please try this instead.
>
> # /etc/rc.d/ntpd stop
> # /etc/rc.d/ntpdate start
>
> This should set your clock, even if only by a few milliseconds.
> Assuming the ntpdate part is successful, continue on:
>
> # tcpdump -l -n -s 8192 -p "port 123"
>
> Now, in another win
Thanks Proto and Chadwick
> I can't help you with the IPv6 stuff; I don't use IPv6.
Actually I don't force ntpd to use IPv6. Hostnames could be resolved to any
IPv4 addresses. I have no problem with that.
The only thing I want is ``synchronization''.
> Please do not define driftfile in /etc/ntp.c
Hi all,
I upgraded to FreeBSD 6.3-STABLE, I have 3 problems.
I think this is the right place to ask. Please someone point me out.
(1)
Previously, I ran ntpd on FreeBSD 6.2-RELEASE with dial-up, I had no problems.
Late last year I switched to ADSL and stayed behind NAT.
I found that ntpd couldn't
