Bug #916
closedOpenNTPd Does Not Operate
0%
Description
The OpenNTPd server does not operate. There is no option to install further NTP services in System > Packages. There is no configuration under Services > (e.g. NTP or OpenNTPd)
2.0-BETA4 Wed Sep 8 05:47:43 UTC 201
Status > Services:
ntpd "Running"
Firewall > Rules > LAN:
Proto: TCP/UPD
Source: LAN net
Source Port: *
Destination: LAN Address
Port: 123 (NTP)
Gateway: *
Queue: none
- ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:90:1C:26:D2
inet addr:172.20.13.249 Bcast:172.20.13.255 Mask:255.255.254.0
inet6 addr: fe80::21e:90ff:fe1c:26d2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530145 errors:0 dropped:0 overruns:0 frame:0
TX packets:537932 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:114939470 (109.6 Mb) TX bytes:120519047 (114.9 Mb)
Interrupt:27 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:68 errors:0 dropped:0 overruns:0 frame:0
TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26066 (25.4 Kb) TX bytes:26066 (25.4 Kb)
w1g1 Link encap:Point-to-Point Protocol
UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1
RX packets:9654514 errors:0 dropped:0 overruns:0 frame:0
TX packets:9654514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Memory:f7eb0000-f7eb1fff
- sntp -P no -r 172.20.13.254
sntp: not enough valid responses received in time
- nmap 172.20.13.254
Starting Nmap 5.00 ( http://nmap.org ) at 2010-09-21 15:05 EDT
Interesting ports on pfsense.fhu.local (172.20.13.254):
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
MAC Address: 00:26:B9:43:AC:E9 (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 5.24 seconds
Updated by Chris Buechler about 14 years ago
- Status changed from New to Rejected
It works fine. It will not provide responses immediately, you have to wait an hour or two after it launches until it's satisfied it's synced. It's not going to show up in a nmap scan as it's UDP. I'm sure if you capture traffic you'll see it's sending replies that it's not providing time sync yet.
Updated by Andreas van dem Helge about 14 years ago
That is correct. This is not documented: http://69.64.6.24/index.php/NTP_Server_(OpenNTPD)
How can I get access to update the documentation?