> 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)
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada 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
> > c
[Please wrap your posts before 80 columns
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada 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
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada 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
> > c
> 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
On Wed, Feb 27, 2008 at 09:58:28PM +0700, Pongthep Kulkrisada wrote:
> [EMAIL PROTECTED]:~# /etc/rc.d/ntpdate start
> Setting date via ntp.
> 27 Feb 20:46:53 ntpdate[2000]: no server suitable for synchronization found
> [EMAIL PROTECTED]:~# tcpdump -l -n -s 8192 -p "port 123"
> tcpdump: verbose o
> 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
On Tue, Feb 26, 2008 at 10:09:10PM +0700, Pongthep Kulkrisada wrote:
> > Please do not define driftfile in /etc/ntp.conf. The /etc/rc.d/ntpd
> > framework will take care of that for you by using -f /var/db/ntpd.drift.
> I have tried it, still not work.
I was pointing this out not as "this will fi
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
On Mon, Feb 25, 2008 at 10:07:56PM +0700, Pongthep Kulkrisada wrote:
> Last week I upgraded from source to FreeBSD 6.3-STABLE (buildworld).
> I found that I can not get sync with any NTP servers both IPv4 and IPv6.
> The followings are my information.
>
> # cat /etc/ntp.conf
> server time.navy.mi.
Pongthep Kulkrisada wrote:
> (2)
> My next problem after buildworld is ``man pages are not updated''.
> They are still FreeBSD 6.2. What happen? How to fix it?
>
You need to delete your old catman pages.
find /usr/share/man/cat* -type f -exec rm -f {} \;
>
> Please someone point me out.
>
12 matches
Mail list logo
