Upon boot, the BBB in the flying aircraft will be required to contact the server to get the current time/date.
When connected to the internet through eth0, the stock BBB uses NTP to retrieve time from the internet. When connected through USB, the BBB uses a date of 1-Mar-2015 (very annoying).
The mechanism I anticipate to solve this problem will require running NTPD on the server, using static IP's and having the (multiple) BBB all contact the server to retrieve time on boot. This will also require that we bring up (boot) the server sufficiently in advance of booting the BBB.
How exactly to get NTPD running on the server and have the BBB contact the server NTPD upon boot for time is an open issue.
Upon boot, the BBB in the flying aircraft will be required to contact the server to get the current time/date.
When connected to the internet through eth0, the stock BBB uses NTP to retrieve time from the internet. When connected through USB, the BBB uses a date of 1-Mar-2015 (very annoying).
The mechanism I anticipate to solve this problem will require running NTPD on the server, using static IP's and having the (multiple) BBB all contact the server to retrieve time on boot. This will also require that we bring up (boot) the server sufficiently in advance of booting the BBB.
How exactly to get NTPD running on the server and have the BBB contact the server NTPD upon boot for time is an open issue.