<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I stopped using ntpdate, ntp does a far better job.<div>I don't see a relation to olsd.<br><div>Teco</div><div><br><div><div>Op 3 mrt. 2012, om 08:57 heeft Ben West het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Bruce,<div><br></div><div>Thanks for the response. I do have the full ntpdate client installed on these nodes. The problem seems to be that ntpdate only (by default) syncs on power-up, so any nodes that don't quickly get a default route set by OLSRd have ntpdate time out.</div>
<div><br></div><div>A simple solution seems like it would be to run ntpdate periodically, though I'm not sure if running as often as hourly may interfere with the timestamps on the HNAs (e.g. introduce excessive jitter). The onboard clocks on the UBNT radios are not that precise; I've seen a 1 minute or so drift develop over a day.<br>
<br><div class="gmail_quote">On Sat, Mar 3, 2012 at 1:50 AM, Bruce Ford <span dir="ltr"><<a href="mailto:fordbr@gmail.com">fordbr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Perhaps use the ntp client included in the OpenWRT BusyBox rather than ntpdate or install the full NTP client. See <a href="http://wiki.openwrt.org/doc/howto/ntp.client" target="_blank">http://wiki.openwrt.org/doc/howto/ntp.client</a><br>
<br>Bruce Ford<br><br><div class="gmail_quote"><div><div class="h5">On Sat, Mar 3, 2012 at 10:11 AM, Ben West <span dir="ltr"><<a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="h5">
I'm running OLSR v0.6.1 packaged with OpenWRT 10.03.1 on a collection of Ubiquiti M5 access points (Rocket, Bullet, Nanostation, Nano Loco).<div><br></div><div>All radios have /etc/init.d/ntpdate service enabled on boot to sync local time to a remote NTP server, although this only succeeds on non-gateway nodes if OLSRd (also enabled on boot) finds and sets a default route before ntpdate times out.</div>
<div><br></div><div>In the case where ntpdate does time out before setting a node's local time, I've noticed letting that node operate as-is in the mesh can cause other nodes to lose their default route. Presumably from the non-sync'ed node sending out HNA's with bad timestamps? Is this expected OLSR behavior?</div>
<div><br></div><div>Besides simply letting ntpdate run on all nodes as an hourly or daily cron job, would anyone have other recommendations on keeping all nodes' local time synced?<span><font color="#888888"><br clear="all">
<div><br></div>-- <br>
<div>Ben West</div><div><a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a></div><br>
</font></span></div>
<br></div></div><span class="HOEnZb"><font color="#888888">--<br>
Olsr-users mailing list<br>
<a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
<a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br></font></span></blockquote></div><br>
<br>--<br>
Olsr-users mailing list<br>
<a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>
<a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Ben West</div><div>
<a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a></div><br>
</div>
-- <br>Olsr-users mailing list<br><a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>https://lists.olsr.org/mailman/listinfo/olsr-users</blockquote></div><br></div></div></body></html>