pfSense uses ntpd, not ntpdate.
On 11/26/06, Josep Pujadas i Jubany <[EMAIL PROTECTED]> wrote:
Hello!
My pfSense 1.0.1 was wrong with the time/date.
I connected to the console by SSH and I made this:
# ntpdate time.nist.gov
26 Nov 21:42:23 ntpdate[82308]: no server suitable for synchronization found
# ping time.nist.gov
PING time.nist.gov (192.43.244.18): 56 data bytes
64 bytes from 192.43.244.18: icmp_seq=0 ttl=44 time=226.568 ms
64 bytes from 192.43.244.18: icmp_seq=1 ttl=44 time=223.220 ms
64 bytes from 192.43.244.18: icmp_seq=2 ttl=44 time=224.814 ms
64 bytes from 192.43.244.18: icmp_seq=3 ttl=44 time=223.403 ms
^C
--- time.nist.gov ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 223.220/224.501/226.568/1.343 ms
# ntpdate 192.43.244.18
26 Nov 20:59:58 ntpdate[82425]: step time server 192.43.244.18 offset -
2580.974035 sec
# ntpdate time.nist.gov
26 Nov 21:00:48 ntpdate[82565]: adjust time server 192.43.244.18 offset
0.025371 sec
DNS servers are configurated. But, ntpdate does'nt resolve the server name
before pinging it (?)
Best regards,
Josep Pujadas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
