On 2015-Apr-08, at 5:37 PM, Adam Thompson <[email protected]> wrote:
> I'm running 2.2.1-RELEASE (i386) in a new install, and everything's working > great so far (or as great as the FUBAR layer 2 lets it work...) except for > NTP. > > No matter what NTP server I pick, it sits in .INIT. state forever. > Stopping ntpd and using ntpdate on the command-line produces - surprise - a > timeout. > Yet NTP from *behind* the firewall works fine. > > Anyone else seeing this problem? Any ideas? > > -Adam Thompson > [email protected] Sounds like the same issue I experienced. We've always used time.apple.com as the time server for our pfSense boxes and the LAN-resident systems use pfSense. Pointing at time.apple.com works on only 2 of our 3 pfsense boxes. On the stubborn pfSense, I could ping the FQDN from the NTP-no-work pfSense box and even tried just the IP address but all attempts resulted in it reporting .INIT. state, forever. Restarts and reboots didn't help. I didn't have more time to waste so I simply pointed the stubborn pfSense box's NTP at one of the other pfSense boxes via the always-on site-to-site VPN and it's been OK with that. Of course, it reports that the NTP service's "Ref ID" is the IP of time.apple.com (from the other pfSense box), LOL. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
