starred/OpenEPaperLink
1
0
Fork 0
mirror of https://github.com/OpenEPaperLink/OpenEPaperLink.git synced 2026-03-21 00:04:28 +01:00
Code Issues 472 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #547] Feature request: make NTP server configurable #3113

New Issue
Closed
opened 2026-03-20 22:07:31 +01:00 by sascha_hemi · 2 comments
sascha_hemi commented 2026-03-20 22:07:31 +01:00
Owner
Copy Link

Originally created by @joluxer on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/547

Well maintained IoT equipment is not allowed to access the public internet. The amount of security reviews would be a night mare.

Currently the NTP servers are hardcoded, thus the OEPL-AP need internet access. Without, it seems not to run stable.

In the first turn it would be enough, to replace the static NTP servers strings by values from the configuration database. If those are empty, simple preset them to the current static string. The web interface could present this setting as a space separated list.

It would be great, if in the DHCP case the system pulls the time server from DHCP too. If no available by DHCP, fall back to the static strings.

Originally created by @joluxer on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/547 Well maintained IoT equipment is not allowed to access the public internet. The amount of security reviews would be a night mare. Currently the NTP servers are hardcoded, thus the OEPL-AP need internet access. Without, it seems not to run stable. In the first turn it would be enough, to replace the static NTP servers strings by values from the configuration database. If those are empty, simple preset them to the current static string. The web interface could present this setting as a space separated list. It would be great, if in the DHCP case the system pulls the time server from DHCP too. If no available by DHCP, fall back to the static strings.
sascha_hemi added the enhancement label 2026-03-20 22:07:31 +01:00
sascha_hemi commented 2026-03-20 22:07:31 +01:00
Author
Owner
Copy Link

@svenove commented on GitHub (Jan 25, 2026):

See #167

<!-- gh-comment-id:3796416643 --> @svenove commented on GitHub (Jan 25, 2026): See #167
sascha_hemi commented 2026-03-20 22:07:32 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Mar 18, 2026):

clusing this one as a duplicate of the (reopened) https://github.com/OpenEPaperLink/OpenEPaperLink/issues/167

<!-- gh-comment-id:4081693155 --> @nlimper commented on GitHub (Mar 18, 2026): clusing this one as a duplicate of the (reopened) https://github.com/OpenEPaperLink/OpenEPaperLink/issues/167
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
88MZ100 FW
ARM Tag FW
ap fw
bug
documentation
enhancement
good first issue
nRF FW
pull-request
Mirrored from GitHub Pull Request
 question
tag fw
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sascha_hemi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3113
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?