On 7/2/20 7:04 PM, harry.steven...@gmail.com wrote:
Thanks. Fulfilling this by configuring ntp.conf sounds quite diable. I
followed some instructions online but failed. Here is what in BBG's
ntp.conf and Pi's ntp.conf. I use 192.168.0.102 to ssh into pi and
192.168.4.2 to ssh into BBG.
Part of ntp.conf in BBG:
# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your
server will
# pick a different set every time it starts up. Please consider
joining the
# pool: <http://www.pool.ntp.org/join.html>
server 192.168.0.102
Part of ntp.conf in Pi:
# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 192.168.4.0 mask 255.255.255.0 nomodify notrap
And here is the result for ntpq -p on BBG. I don't know how to check
if BBG is really trying to make time sync.
debian@beaglebone:~$ sudo ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
192.168.0.102 .XFAC. 16 u 58 64 0 0.000 0.000
0.000
<chopped>
reach 0 shows that your not reaching your ntp server, or it's refusing
connections or...
It will (reach field) get to 377 if all is well. This may also fail
anyway as *most* ntp clients want more than one server. Typically at
least 3, to ensure that you get a good chimer.
Mike
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/7f1ab022-17ff-dd19-01f2-ab28429001f6%40gmail.com.
