On 2015-Apr-11, at 12:51 AM, Fabian Wenk wrote:
> I had a similar problem, but already when switching from 2.1.x to 2.2. I got
> it working again with not selecting any interface(s) in the NTP Server
> Configuration.
I've created a bug report (https://redmine.pfsense.org/issues/4604) with an
Hello Adam
On 09.04.15 02:37, Adam Thompson 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 usi
On 2015-Apr-08, at 5:37 PM, Adam Thompson 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
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
