Sun May 01, 2011 5:11 am
Turns out the 66.96.99.4 does not ping, and a trace route dies at 66.96.99.1. It is a public ntp server. Maybe its set to not respond to pings?? But I know its an active server, because nearly every device on my network is using it and syncing just fine. I put in a different server address as seen below. This is also a public server, is ping-able, and is syncing fine on the few devices I have it on, but is not syncing on my 1100. Do I have to specifically allow for ntp in my firewall input chain? I haven't had to on my other devices, which are a mixture of routerboards including 450g, 411, 433, 493 etc.
[removed] > sy ntp cli pr
enabled: yes
mode: unicast
primary-ntp: 128.138.140.44
secondary-ntp: 0.0.0.0
poll-interval: 16s
active-server: 128.138.140.44