[LEDE-DEV] busybox ntpd not syncing if any server is bad

Hans Dedecker dedeckeh at gmail.com
Thu Aug 17 05:09:32 PDT 2017


On Thu, Aug 17, 2017 at 1:25 PM, Karl Palsson <karlp at tweak.net.au> wrote:
>
> Ok, so this was broken after busybox 1.23.2 and not fixed until
> 1.27 via
>
> https://git.busybox.net/busybox/commit/networking/ntpd.c?id=b62ea34afed7d3bf60a6c8ef5a030fea52f55b10
>
> Presumably updating busybox in master isn't exactly on the
> roadmap. Would a backport of this patch be acceptable for both
> 17.01 and master?
I'm in favor to backport the patch to 17.01; for master there's a
pending patch to upstep to busybox 1.27
(https://patchwork.ozlabs.org/patch/801034/)

Hans
>
> Sincerely,
> Karl Palsson
>
> Karl Palsson <karlp at tweak.net.au> wrote:
>>
>> Hi,
>>
>> On old openwrt 15.05 builds, if I was running in a private
>> network, and only had some NTP servers available, ntpd would
>> still sync, and I could still query the local ntpd for it's
>> sync status.
>>
>> However, now in lede-17.01 and lede current master, ntpd seems
>> to just get stuck trying the first listed ntp server, and never
>> gives up and tries the other listed servers. This seems rather
>> odd, and particularly unhelpful. Does anyone know any
>> workarounds?
>>
>> # ntpd -n -d -l -S /usr/sbin/ntpd-hotplug -p bad.example.org -p somewhere.working.org
>> ntpd: bad address 'bad.example.org'
>> ntpd: bad address 'bad.example.org'
>> ntpd: bad address 'bad.example.org'
>> ... forever....
>>
>> It never gets to trying "somewhere.working.org" so simply never
>> gets sync. Same behaviour on both 17.01 and master branch,
>> though on 17.01, the :123 listen ports aren't opened up at all.
>>
>> On openwrt 15.05 (busybox 1.23.2) the behaviour is markedly
>> different
>>
>>
>> # /usr/sbin/ntpd -d -n -l -S /usr/sbin/ntpd-hotplug -p bad.example.org -p somewhere.working.org
>> ntpd: resolved peer somewhere.working.org to 192.168.255.124
>> ntpd: sending query to 192.168.255.124 ntpd: bad address
>> 'bad.example.org' ntpd: could not resolve peer bad.example.org,
>> skipping ntpd: reply from 192.168.255.124: offset:-0.004779
>> delay:0.012441 status:0x24 strat:3 refid:0xc1043a2c
>> rootdelay:0.001465 reach:0x01 ntpd: sending query to
>> 192.168.255.124 ntpd: reply from 192.168.255.124:
>> offset:+0.001084 delay:0.002000 status:0x24 strat:3
>> refid:0xc1043a2c rootdelay:0.001465 reach:0x03
>>
>>
>> Sincerely,
>> Karl Palsson
>
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
>



More information about the Lede-dev mailing list