Jumping the clock doesn't play well with rtsol. If it jumps too far, ipv6 timers expire, you lose your rtsol'd address/route, and it takes a little time to reacquire them.
It might work to use rdate_flags and set the clock before ntpd starts, but this is a bit racy. On 2009-06-17, Stefan Unterweger <ste...@rg-me.it> wrote: > * Paul de Weerd on Wed, Jun 17, 2009 at 11:34:38AM +0200: >> > Just em0, which is connected to the LAN and gets all of its >> > configuration via DHCP and rtsol. > >> Is (one of) your ntp server(s) v6 only ? Do you have rtsol in >> your /etc/hostname.em0 ? > > Yes and yes. > >> Do you get a lease immediately on boot or could >> there be some delay ? It sounds like you don't have proper >> connectivity yet when ntpd tries to start (either v4 or v6 (or both)). >> Verify this by putting something like 'ifconfig -a > /tmp/ifc.out' in >> /etc/rc.local. > > As far as I glanced, the rtsol "lease" should already be present > when ntpd tries to start, or at least the machine already knows > where to reach the v6 gateway. But this is from memory; I will > test it as soon as I get back to the machine in question. > > If I *don't* go with rtsol but e.g. let aiccu set up a > gif-tunnel, ntpd get's up cleanly, sees that there's no way to > reach the v6-servers (yet) (since aiccu would be invoked from > rc.local, thus way after ntpd), syncs to the v4 ones, and some > time later (successfully) starts connecting to the v6 ones. > > > s//un
