search

WAGO / pfc-firmware

This repository contains official Wago firmware releases for 750-8xxx(PFC) series.
Mozilla Public License 2.0
46 stars 6 forks source link

Feature Request: Allow domain-names in NTP config #5

Closed kohlerdominik closed 2 years ago

kohlerdominik commented 2 years ago

Hi there

I hope i'm in the right place here to drop a feature request. If not, feel free to move this issue whereever it belongs.

All NTP-clients that I know support domain names as ntp server address. However, for some reasons, wbm-config does only allow IPs. I think, domain names are much more reliable in the long shot, as it allows to use a server pool like ntppool.org. Are there any chances, that future version will allow this?

Helmut-Saal commented 2 years ago

Hi, yes we have this request open. In the Moment it is not clear if we like to do that because if you use a name instead of a ip address you also have to use an DNS Server. BG

Ekristoffe commented 2 years ago

Hello helmut, Any cloud request (as if it is not fulfilled you are stuck) an up to date time and date. Please remind me how cloud connectivity work ? An ip or a name ? Thanks to send this to the devs.

kohlerdominik commented 2 years ago

Hi @Helmut-Saal

Just ran into an issue, the public NTP server defined in one of our installations is no longer available. Can you please provide public IPs of 4 stable NTP-Servers? Or maybe fill by default?

Helmut-Saal commented 2 years ago

Hi, just let me say sorry....but the thing i would do is to google IP adresses of public ntp servers. I think you can also search via google to servers. To preset ntp server in wbm may get problems in different countrys. Wy did you not use your one server?? That would be the best way.

Ekristoffe commented 2 years ago

@kohlerdominik could you try those IP address: 133.243.238.163 : NICT Public NTP (ntp.nict.jp) 133.243.238.164 : NICT Public NTP (ntp.nict.jp) 133.243.238.243 : NICT Public NTP (ntp.nict.jp) 133.243.238.244 : NICT Public NTP (ntp.nict.jp) 216.239.35.0 : Google Public NTP (time1.google.com) 216.239.35.4 : Google Public NTP (time2.google.com) 216.239.35.8 : Google Public NTP (time3.google.com) 216.239.35.12 : Google Public NTP (time4.google.com)

@Helmut-Saal not every company / building have a NTP server available on their network.

Helmut-Saal commented 2 years ago

Hi all, thats right but if we preset an public server in our firmware what about if this server would not work in the future. This would create a lot of support tickets and what then, we have to recreate an provide a new firmware because the ntp server is dead. I think you could follow me that we cant do that....... Also an pfc could be an ntp server.......

Ekristoffe commented 2 years ago

Hi all, thats right but if we preset an public server in our firmware what about if this server would not work in the future. This would create a lot of support tickets and what then, we have to recreate an provide a new firmware because the ntp server is dead. I think you could follow me that we cant do that....... Also an pfc could be an ntp server.......

Indeed and this is why the URL NTP would be the best option. I really hope this will be allowed in the next future.

kohlerdominik commented 2 years ago

Hi

Just to provide feedback on this: we install the device at customers site. They usually do not have a NTP server, therefore we are forced to use a public NTP server. And I did not find a single NTP server provider which states the IP addresses of its servers. And this is because domains are so much easier to redirect than IP-addresses. Because of this, domains pointed server are reachable forever, while IP(v4) addresses might change and break the NTP functionality.

See this list of public time servers, which are provided by all big companies and are exclusively documented to use by domain https://gist.github.com/mutin-sa/eea1c396b1e610a2da1e5550d94b0453