It would be nice if we could customize, on the admin web interface, the NTP server IP address/FQDN.
The purpose is to reduce reliance on external resources on hardened sites (with a local NTP server that relies on a local GPS receiver and a backup DCF77/ALS162 decoder).
Best regards,
Hi,
It would be nice if we could customize, on the admin web interface, the NTP server IP address/FQDN.
The purpose is to reduce reliance on external resources on hardened sites (with a local NTP server that relies on a local GPS receiver and a backup DCF77/ALS162 decoder).
Best regards,
<!-- github-sync-id:3105713272 -->
this is great idea.... but let me ask.... would this enable anyone to have his own "local ntp" with a esp32+gps board and this way generate the ntp time even without "internet" ?
this is great idea.... but let me ask.... would this enable anyone to have his own "local ntp" with a esp32+gps board and this way generate the ntp time even without "internet" ?
<!-- github-comment-id:2927157958 -->
this is great idea.... but let me ask.... would this enable anyone to have his own "local ntp" with a esp32+gps board and this way generate the ntp time even without "internet" ?
That's one possibility for non-time critical application =)
In my case, the initial feature request is motivated by the following:
A few of our sites are built with reinforced concrete or a fully metallic shelter in which a direct reliable reception of GNSS signals isn't feasible.
We're planning to experiment with a single frequency FM repeater network in the future, so we've already got local time sources that we can leverage, with a fallback channel (LF time signal), and an internal stable oscillator.
> this is great idea.... but let me ask.... would this enable anyone to have his own "local ntp" with a esp32+gps board and this way generate the ntp time even without "internet" ?
That's one possibility for non-time critical application =)
In my case, the initial feature request is motivated by the following:
- A few of our sites are built with reinforced concrete or a fully metallic shelter in which a direct reliable reception of GNSS signals isn't feasible.
- We're planning to experiment with a single frequency FM repeater network in the future, so we've already got local time sources that we can leverage, with a fallback channel (LF time signal), and an internal stable oscillator.
<!-- github-comment-id:2927300523 -->
ok, but this gets really away from "other" NTP servers
is the goal of this request to have a box to input a personal choice NTP server to start?
ok, but this gets really away from "other" NTP servers
is the goal of this request to have a box to input a personal choice NTP server to start?
<!-- github-comment-id:2927304056 -->
ok, but this gets really away from "other" NTP servers
is the goal of this request to have a box to input a personal choice NTP server to start?
Yes.
> ok, but this gets really away from "other" NTP servers
>
> is the goal of this request to have a box to input a personal choice NTP server to start?
Yes.
<!-- github-comment-id:2927329262 -->
This would be quite useful also for our sailboat use case. We have internet connectivity only every once in a while, and the rest the device could operate as a digipeater. We do have a local NTP server on board to keep all devices in sync.
This would be quite useful also for our sailboat use case. We have internet connectivity only every once in a while, and the rest the device could operate as a digipeater. We do have a local NTP server on board to keep all devices in sync.
<!-- github-comment-id:3356793673 -->
this has been added into the repository just now... for testing purposes and if it works fine for others too, it will be added to next release
this has been added into the repository just now... for testing purposes and if it works fine for others too, it will be added to next release
<!-- github-comment-id:3393591847 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi,
It would be nice if we could customize, on the admin web interface, the NTP server IP address/FQDN.
The purpose is to reduce reliance on external resources on hardened sites (with a local NTP server that relies on a local GPS receiver and a backup DCF77/ALS162 decoder).
Best regards,
Excelent idea!
so off-grid and off-internet sites can also be in-time
this is great idea.... but let me ask.... would this enable anyone to have his own "local ntp" with a esp32+gps board and this way generate the ntp time even without "internet" ?
That's one possibility for non-time critical application =)
In my case, the initial feature request is motivated by the following:
ok, but this gets really away from "other" NTP servers
is the goal of this request to have a box to input a personal choice NTP server to start?
Yes.
This would be quite useful also for our sailboat use case. We have internet connectivity only every once in a while, and the rest the device could operate as a digipeater. We do have a local NTP server on board to keep all devices in sync.
this has been added into the repository just now... for testing purposes and if it works fine for others too, it will be added to next release