Re: [LEDE-DEV] busybox ntpd not syncing if any server is bad (update, if _first_ server is bad)

2017-11-07 Thread Karl Palsson
Final note here, busybox has fixed this upstream, and ntpd now syncs faster and _vastly_ more reliably with bad servers in the list. Depending on their release schedule some people may like the patches backported, but I'm just carrying them myself for the time being. Cheers, Karl P Karl

Re: [LEDE-DEV] busybox ntpd not syncing if any server is bad (update, if _first_ server is bad)

2017-10-27 Thread Karl Palsson
Magnus Kroken wrote: > On 21.08.2017 16:34, Karl Palsson wrote: > > on master, even with the ntpd patch for busybox applied. > > # ntpdate -q localhost > > server ::1, stratum 0, offset 0.00, delay 0.0 > > server 127.0.0.1, stratum 0, offset 0.00, delay 0.0 21 >

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

2017-08-23 Thread Magnus Kroken
On 21.08.2017 16:34, Karl Palsson wrote: on master, even with the ntpd patch for busybox applied. # ntpdate -q localhost server ::1, stratum 0, offset 0.00, delay 0.0 server 127.0.0.1, stratum 0, offset 0.00, delay 0.0 21 Aug 14:26:24 ntpdate[1392]: no server suitable for

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

2017-08-21 Thread Karl Palsson
Magnus Kroken wrote: > Hi Karl > > On 17.08.2017 15:13, Karl Palsson wrote: > > It certainly _looks_ better, but isn't actually syncing... > > > > Sincerely, > > Karl Palsson > > > > > > # /usr/sbin/ntpd -d -n -N -l -S /usr/sbin/ntpd-hotplug -p > > 0.lede.pool.ntp.org -p

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

2017-08-17 Thread Hans Dedecker
On Thu, Aug 17, 2017 at 1:25 PM, Karl Palsson 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