On Aug 3, 2017, at 7:27 AM, Leandro Martelli wrote:
> I just came across a non-intuitive ntpdate case caused by my firewall
> configuration.
>
> My firewall outbound rules include something like:
>
> - allow from udp 123 to udp 123
> - allow from udp 1-2 to any
Try: all from udp any to
This is a classic problem that arises when the system is booting from DHCP.
This is a link I had saved that describes the problem and points to a
solution:
https://serverfault.com/questions/329596/how-to-override-the-ntp-information
-sent-by-dhcp-in-debian
Please let me know if this worked and if
Hi,
I just came across a non-intuitive ntpdate case caused by my firewall
configuration.
My firewall outbound rules include something like:
- allow from udp 123 to udp 123
- allow from udp 1-2 to any
The first line ensures NTPd will work, which is fine.
The second line was spotted afte
Check the process running with something like "ps -Aef | grep ntpd" to be sure
things are running how you think they are. "/etc/ntp.conf" is the default but
there may be something passing an alternate config file to the daemon with the
-c flag on startup.
Also, see if you have something like ti
Kevin Chan wrote:
> I'm on an imx233 arm processor using Debian 7.0 with kernel version 3.12
>
> I'm having issues configuring ntpd to read from a gps source. I have tried
> adding server entries in /etc/ntp.conf, but those changes have no effect on
> the sources listed in ntpq -p
>
> The only th
I'm on an imx233 arm processor using Debian 7.0 with kernel version 3.12
I'm having issues configuring ntpd to read from a gps source. I have tried
adding server entries in /etc/ntp.conf, but those changes have no effect on
the sources listed in ntpq -p
The only thing I see is:
root@arm:~# ntpq
