Frequent connections to port 123

Hi, I have noticed, that one of my openwrt boxes (running rather old OpenWrt 18.06.9, because it is 32/4 device) frequently connects to several IP:123 (twice a minute or so). I guess they are time checks.

I have been wondering, if I can set a delay how often openwrt should contact time servers for obtaining the correct time? Other boxes in the same network with this same openwrt version and nearly the same config do not (mis)behave this way. Thanks.

openwrt:~# cat /etc/config/system
config system
        option hostname 'openwrt'
        option timezone 'CET-1CEST,M3.5.0,M10.5.0/3'
        option ttylogin '0'
        option log_size '64'
        option urandom_seed '0'

config timeserver 'ntp'
        option enabled '1'
        option enable_server '0'
        list server '0.lede.pool.ntp.org'
        list server '1.lede.pool.ntp.org'
        list server '2.lede.pool.ntp.org'
        list server '3.lede.pool.ntp.org'

Hi

according to this

ntpd --help
BusyBox v1.30.1 () multi-call binary.

Usage: ntpd [-dnqNw] [-S PROG] [-p PEER]...

NTP client/server

        -d      Verbose (may be repeated)
        -n      Do not daemonize
        -q      Quit after clock is set
        -N      Run at high priority
        -w      Do not set time (only query peers), implies -n
        -S PROG Run PROG after stepping time, stratum change, and every 11 min
        -p PEER Obtain time from PEER (may be repeated)

there is no option for update frequency
maybe something else is triggering / forcing NTP update ?

Have you checked the ntp log? The client shouldn’t call IP:123 by random all over the place!?

But for start since you are using obsolete firmware, try at least changing the servers to something modern!

https://openwrt.org/docs/guide-user/advanced/ntp_configuration

1 Like

You could schedule it in cron, instead of running it as a daemon ?

-n -q options, or perhaps -q only.

Are several connections, twice a minute or so, really an issue?

1 Like