SMP is connecting to several remote time-servers multiple times per minute 24/7

WD Legacy Products WD TV Live Streaming
1

Why is the device trying to get the time from different servers multiple times per second even if it successfully got the time after booting?

FW 2.01.86

This is a bug which hasn’t gotten any attention for four years now!

Jan 18 10:00:03 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=54536 DPT=123 LEN=56 
Jan 18 10:00:04 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=54536 DPT=123 LEN=56 
Jan 18 10:00:04 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=54536 DPT=123 LEN=56 
Jan 18 10:00:04 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=54536 DPT=123 LEN=56 
Jan 18 10:00:05 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=45013 DPT=123 LEN=56 
Jan 18 10:00:06 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=45013 DPT=123 LEN=56 
Jan 18 10:00:07 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=45013 DPT=123 LEN=56 
Jan 18 10:00:08 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=45013 DPT=123 LEN=56 
Jan 18 10:00:14 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58497 DPT=123 LEN=56 
Jan 18 10:00:14 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58497 DPT=123 LEN=56 
Jan 18 10:00:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58497 DPT=123 LEN=56 
Jan 18 10:00:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58497 DPT=123 LEN=56 
Jan 18 10:00:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=46953 DPT=123 LEN=56 
Jan 18 10:00:16 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=46953 DPT=123 LEN=56 
Jan 18 10:00:17 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=46953 DPT=123 LEN=56 
Jan 18 10:00:18 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=46953 DPT=123 LEN=56 
Jan 18 10:00:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35430 DPT=123 LEN=56 
Jan 18 10:00:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35430 DPT=123 LEN=56 
Jan 18 10:00:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35430 DPT=123 LEN=56 
Jan 18 10:00:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35430 DPT=123 LEN=56 
Jan 18 10:00:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=33160 DPT=123 LEN=56 
Jan 18 10:00:26 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=33160 DPT=123 LEN=56 
Jan 18 10:00:27 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=33160 DPT=123 LEN=56 
Jan 18 10:00:28 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=33160 DPT=123 LEN=56 
Jan 18 10:00:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=37601 DPT=123 LEN=56 
Jan 18 10:00:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=37601 DPT=123 LEN=56 
Jan 18 10:00:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=37601 DPT=123 LEN=56 
Jan 18 10:00:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=37601 DPT=123 LEN=56 
Jan 18 10:00:36 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50305 DPT=123 LEN=56 
Jan 18 10:00:37 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50305 DPT=123 LEN=56 
Jan 18 10:00:38 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50305 DPT=123 LEN=56 
Jan 18 10:00:39 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50305 DPT=123 LEN=56 
Jan 18 10:00:45 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=85.125.61.2 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=40028 DPT=123 LEN=56 
Jan 18 10:00:45 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=40028 DPT=123 LEN=56 
Jan 18 10:00:45 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=40028 DPT=123 LEN=56 
Jan 18 10:00:45 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=40028 DPT=123 LEN=56 
Jan 18 10:00:46 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39188 DPT=123 LEN=56 
Jan 18 10:00:47 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39188 DPT=123 LEN=56 
Jan 18 10:00:48 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39188 DPT=123 LEN=56 
Jan 18 10:00:49 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39188 DPT=123 LEN=56 
Jan 18 10:00:55 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=146.255.58.33 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36005 DPT=123 LEN=56 
Jan 18 10:00:55 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36005 DPT=123 LEN=56 
Jan 18 10:00:55 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36005 DPT=123 LEN=56 
Jan 18 10:00:55 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=37.235.63.106 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36005 DPT=123 LEN=56 
Jan 18 10:00:56 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=41036 DPT=123 LEN=56 
Jan 18 10:00:57 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=41036 DPT=123 LEN=56 
Jan 18 10:00:58 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=41036 DPT=123 LEN=56 
Jan 18 10:00:59 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=41036 DPT=123 LEN=56 
Jan 18 10:01:05 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=146.255.58.33 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=44828 DPT=123 LEN=56 
Jan 18 10:01:05 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=44828 DPT=123 LEN=56 
Jan 18 10:01:05 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=44828 DPT=123 LEN=56 
Jan 18 10:01:05 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=44828 DPT=123 LEN=56 
Jan 18 10:01:06 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58935 DPT=123 LEN=56 
Jan 18 10:01:07 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58935 DPT=123 LEN=56 
Jan 18 10:01:08 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58935 DPT=123 LEN=56 
Jan 18 10:01:09 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=58935 DPT=123 LEN=56 
Jan 18 10:01:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39930 DPT=123 LEN=56 
Jan 18 10:01:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39930 DPT=123 LEN=56 
Jan 18 10:01:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39930 DPT=123 LEN=56 
Jan 18 10:01:15 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=146.255.58.33 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=39930 DPT=123 LEN=56 
Jan 18 10:01:16 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50937 DPT=123 LEN=56 
Jan 18 10:01:17 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50937 DPT=123 LEN=56 
Jan 18 10:01:18 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50937 DPT=123 LEN=56 
Jan 18 10:01:19 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=50937 DPT=123 LEN=56 
Jan 18 10:01:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=146.255.58.33 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35848 DPT=123 LEN=56 
Jan 18 10:01:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35848 DPT=123 LEN=56 
Jan 18 10:01:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35848 DPT=123 LEN=56 
Jan 18 10:01:25 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=35848 DPT=123 LEN=56 
Jan 18 10:01:26 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36282 DPT=123 LEN=56 
Jan 18 10:01:27 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36282 DPT=123 LEN=56 
Jan 18 10:01:28 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36282 DPT=123 LEN=56 
Jan 18 10:01:29 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=36282 DPT=123 LEN=56 
Jan 18 10:01:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=91.206.8.70 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47038 DPT=123 LEN=56 
Jan 18 10:01:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=146.255.58.33 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47038 DPT=123 LEN=56 
Jan 18 10:01:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=193.170.62.252 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47038 DPT=123 LEN=56 
Jan 18 10:01:35 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=194.112.182.172 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47038 DPT=123 LEN=56 
Jan 18 10:01:36 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47888 DPT=123 LEN=56 
Jan 18 10:01:37 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47888 DPT=123 LEN=56 
Jan 18 10:01:38 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47888 DPT=123 LEN=56 
Jan 18 10:01:39 router user.warn kernel: ACCEPT IN=br0 OUT=vlan2 src=192.168.1.8 DST=172.19.10.99 LEN=76 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=UDP SPT=47888 DPT=123 LEN=56

 192.168.1.8 is the IP-address of the SMP, and DPT=123 is the assigned destination port for accessing NTP-servers (network time protocol).

The bug has been reported for the SMP 19 months ago:  http://community.wd.com/t5/WD-TV-Live-Streaming-Issues/Remove-Developer-Code-Pt-II-NTP-Server-spam/idi-p/423630

Please stop this! I cannot allow the device to access the LAN when it’s behaving like a little DDoS-device.

EDIT: I know that 172.19.10.99 is a private non-routable IP, which doesn’t make things any better. Debug-routines shouldn’t be active in shipped firmware-releases…

2

/bin/ntpd.sh:

#!/bin/sh

while true; do
	/usr/sbin/rtc -s -w -g pool.ntp.org; 
	if [$? -eq 0]; then
		touch /tmp/ntp_success
		break
	else
		/usr/sbin/rtc -s -w -g 172.19.10.99;
		if [$? -eq 0]; then
			break
		fi
	fi
	sleep 5;
done

 rtc:

Usage: rtc {[-r] [-R]} {[-w] [-W]} {[-g ntp_server] [-G ntp_server]}        -r: Read time from RTC and set to system        -w: Set the current system time to RTC        -g: Get time from NTP server only. (Not set to system or written to RTC).            Used with [-w] [-s]        -s: Set time got from NTP to system

What’s the point of retrying every five seconds?

A mediaplayer doesn’t really need the time to be synchronous down to the millisecond. I’m sure the device can go on for hours or days without successfully synching the time without any breakage.

If a SMP is used offline or restricted from accessing the internet, this routine just ends up spamming the router’s error-log with dropped connections.

And apparently there’s something wrong with either the program or the parameters in general as the loop just goes on even if the SMP is online and has a working connection to online-services, i.e. the location-detection routine etc.

3

schwurbel wrote:

Why is the device trying to get the time from different servers multiple times per second even if it successfully got the time after booting?

schwurbel wrote:

And apparently there’s something wrong with either the program or the parameters in general as the loop just goes on even if the SMP is online and has a working connection to online-services, i.e. the location-detection routine etc.

It doesn’t.  The script quits as soon as the time is sync’d:

/bin # uname -a
Linux WDTVLive3 2.6.35.9-22-sigma #11 PREEMPT Thu Dec 5 16:02:07 CST 2013 mips unknown
/bin # ./ntpd.sh
offset: -0.001800
Try to sync NTP time to system time
/bin #
4

The logic of the script says:

Beginning:

Try pool.ntp.org.  If it works, quit.

If that doesn’t work, try the private address. If that works, quit.

If nothing works, go back to beginning and retry.

I verified the correct behavior of the script by blocking pool.ntp.org and allowing (via a pseudo-interface for that other IP address on my Linux box) that the script works correctly… once it gets an NTP response, it stops.

5

I was wondering, nothing in the NTP protocol tells the client to use 24 hours when a “German timezone” is selected or a server like de.pool.ntp.org is used?

6

TonyPh12345 wrote:

 

It doesn’t.  The script quits as soon as the time is sync’d:

 

/bin # uname -a
Linux WDTVLive3 2.6.35.9-22-sigma #11 PREEMPT Thu Dec 5 16:02:07 CST 2013 mips unknown
/bin # ./ntpd.sh
offset: -0.001800
Try to sync NTP time to system time
/bin #

 

 Could you tell me how you got access to the shell?

7

Nevermind.

/bin # ./ntpd.sh
offset: -78.542389
offset is wrong (-78.542389), we won't set to system
offset: -78.541496
offset is wrong (-78.541496), we won't set to system
^C/bin # /usr/sbin/rtc -s -w -g pool.ntp.orgoffset: -78.523941offset is wrong (-78.523941), we won't set to system/bin # /usr/sbin/rtc -rTry to set time from RTC to systemrtc time : Sun Jan 19 09:39:46 2014/bin # /usr/sbin/rtc -s -w -g pool.ntp.orgoffset: 0.826098Try to sync NTP time to system time/bin #

Now it’s fixed.

How could that excessive offset happen in the first place?

And why would the program deny setting the time when the offset is so wrong? Isn’t correcting the time the point of this program? Weird.

Maybe WD could add the “rtc -r” command to the script as another fallback and set the sleep to a few hours or something.

8

Techflaws wrote:

I was wondering, nothing in the NTP protocol tells the client to use 24 hours when a “German timezone” is selected or a server like de.pool.ntp.org is used?

Nope…  The NTP protocol only gets UTC time.  Doesn’t care about timezone, GMT offset, or format.

9

schwurbel wrote:

How could that excessive offset happen in the first place?

And why would the program deny setting the time when the offset is so wrong? Isn’t correcting the time the point of this program? Weird.

The hardware clock in the box has a battery backup.  So I have a few theories:

  1.  The battery has failed and the RTC is drifting wildly.

  2.  The clock came from the factory way out of sync.

  3.  The box has been off network for a LONG time and the RTC has drifted.

The reason it won’t sync is because that’s the standard.   If the hardware clock is more than a certain amount of time off from the NTP clock, the software assumes it’s the NTP clock that’s wrong.  NTP clocks *can* (and often are) wrong…  so that prevents an excessive shift in time.

I can’t imagine only 1 minute 18 seconds being enough to do that, though…