06-14-2023, 12:40 AM
Actually, I see a smattering of seemingly related posts on the InterWeb™ regarding eero (especially with eero Secure) but I'm not in a position to comment. For a time in the past, I was on an ISP-provided eero mesh network and had no problem with moOde and time synchronization. That was then and this is now. Lots of changes have occurred in all of the components involved.
In any case, this is an issue between eero and Raspberry Pi OS; moOde is just going along on the ride. I suppose the moOde build could override the default /etc/systemd/timesyncd.conf file, but I'm not certain what the best settings would be. AFAIK the default settings allow each installation to find the closest available NTP server and this change would override that behavior. For the vast majority of us, the default settings work fine.
I'm not able to experiment with this for now. My partner and I fly to California in 10 hours to spend a couple of weeks with her new grandchild. That is a more exciting prospect than futzing with code
Regards,
Kent
In any case, this is an issue between eero and Raspberry Pi OS; moOde is just going along on the ride. I suppose the moOde build could override the default /etc/systemd/timesyncd.conf file, but I'm not certain what the best settings would be. AFAIK the default settings allow each installation to find the closest available NTP server and this change would override that behavior. For the vast majority of us, the default settings work fine.
I'm not able to experiment with this for now. My partner and I fly to California in 10 hours to spend a couple of weeks with her new grandchild. That is a more exciting prospect than futzing with code
Regards,
Kent
