[opensuse-support] chrony, timedeatectl, networkmanager, dhcp
Hi *, I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook. I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient? If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf. I tried different constellations, but the results didn't seem to be consistent in a way I could understand. TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Michael Hirmke wrote:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook. I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient?
That depends on your requirements, how accurate do you need laptop time to be? chrony sounds like it would be fine for you.
If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf.
The dhcp infos are written to a file, for instance: /var/lib/dhcpcd/dhcpcd-eth0.info contains lines of "variable=value". Somehow chromy grabs hold of that. Probably slightly different with NetworkManager. -- Per Jessen, Zürich (21.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Fri, Apr 24, 2020, 09:27 Per Jessen <per@computer.org> wrote:
Michael Hirmke wrote:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook. I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient?
That depends on your requirements, how accurate do you need laptop time to be? chrony sounds like it would be fine for you.
If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf.
The dhcp infos are written to a file, for instance:
/var/lib/dhcpcd/dhcpcd-eth0.info
contains lines of "variable=value". Somehow chromy grabs hold of that.
Probably slightly different with NetworkManager.
Peter
I do not understand why would you want to change ntp server depending on whichever way you connect to a network. Unless you need local ntp on lan(s) and different one elsewhere. I personally do not need better time precision than ~ 1s to keep make happy when using network storage - for that any pool.ntp.org is good enough and it works everywhere, including LTE. Am I missing something? Tomas
Hi Tomas,
On Fri, Apr 24, 2020, 09:27 Per Jessen <per@computer.org> wrote:
Michael Hirmke wrote:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook. I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient?
That depends on your requirements, how accurate do you need laptop time to be? chrony sounds like it would be fine for you.
If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf.
The dhcp infos are written to a file, for instance:
/var/lib/dhcpcd/dhcpcd-eth0.info
contains lines of "variable=value". Somehow chromy grabs hold of that.
Probably slightly different with NetworkManager.
Peter
I do not understand why would you want to change ntp server depending on whichever way you connect to a network. Unless you need local ntp on lan(s) and different one elsewhere.
Perhaps my wording was not correct - I connect to different networks with my different interfaces.
I personally do not need better time precision than ~ 1s to keep make happy when using network storage - for that any pool.ntp.org is good enough and it works everywhere, including LTE.
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Tomas
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 25/04/2020 13.42, Michael Hirmke wrote:
Hi Tomas,
On Fri, Apr 24, 2020, 09:27 Per Jessen <> wrote:
Michael Hirmke wrote:
I do not understand why would you want to change ntp server depending on whichever way you connect to a network. Unless you need local ntp on lan(s) and different one elsewhere.
Perhaps my wording was not correct - I connect to different networks with my different interfaces.
I personally do not need better time precision than ~ 1s to keep make happy when using network storage - for that any pool.ntp.org is good enough and it works everywhere, including LTE.
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Ah. You don't need a correct universal time, but the same time as the network you are connecting to. Like a Windows Domain with active directory. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
[...]
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Ah. You don't need a correct universal time, but the same time as the network you are connecting to. Like a Windows Domain with active directory.
Not like - exactly an Active Directory domain!
-- Cheers / Saludos,
Carlos E. R.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 25/04/2020 19.45, Michael Hirmke wrote:
[...]
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Ah. You don't need a correct universal time, but the same time as the network you are connecting to. Like a Windows Domain with active directory.
Not like - exactly an Active Directory domain!
Right. So it is a different problem. You absolutely need to use the time information from the server listed in the DHCP information, not an outside source. I understand the problem, but I have not played with it in years. Not since a long training course I had, ~10 years ago or so. I don't remember offhand what we did... :-? I wonder if Samba has something already for this? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hi Carlos,
On 25/04/2020 19.45, Michael Hirmke wrote:
[...]
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Ah. You don't need a correct universal time, but the same time as the network you are connecting to. Like a Windows Domain with active directory.
Not like - exactly an Active Directory domain!
Right. So it is a different problem. You absolutely need to use the time information from the server listed in the DHCP information, not an outside source.
Yep. Time and date may be completely wrong, but they must be synchronous to the AD DC in use.
I understand the problem, but I have not played with it in years. Not since a long training course I had, ~10 years ago or so. I don't remember offhand what we did... :-?
I wonder if Samba has something already for this?
No - Samba also relies on synchronous clocks between the AD DC and the local machine. In fact, Samba uses the local kerberos infrastructure for many tasks.
-- Cheers / Saludos,
Carlos E. R.
bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2020-04-25 at 20:38 +0200, Michael Hirmke wrote:
Hi Carlos,
On 25/04/2020 19.45, Michael Hirmke wrote:
...
I understand the problem, but I have not played with it in years. Not since a long training course I had, ~10 years ago or so. I don't remember offhand what we did... :-?
I wonder if Samba has something already for this?
No - Samba also relies on synchronous clocks between the AD DC and the local machine. In fact, Samba uses the local kerberos infrastructure for many tasks.
I found this: <https://wiki.samba.org/index.php/Time_Synchronisation> Contents 1 Introduction 2 Configuring Time Synchronisation on a DC 2.1 Requirements 2.2 With ntpd 2.3 With chrony 3 Configuring Time Synchronisation on a Unix Domain Member 3.1 Requirements 3.2 With ntpd 3.3 With chrony 3.4 With systemd-timesyncd 4 Configuring Time Synchronisation on a Windows Domain Member 4.1 Default Time Source 4.2 Setting User Defined Time Sources and Options - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXqSHERwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV/jIAoJFB/ue9vK76qLFd6Xpt BitaQfTQAJwK3APFHrT9Agx66AL/w2D/LmYVHg== =F2ng -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi Carlos, [...]
I found this:
yes, exactly. And furthermore you have to obey the combinations for one or all machines being virtual, i.e. host time and guest time 8-< [...]
- -- Cheers, Carlos E. R.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 25/04/2020 22.00, Michael Hirmke wrote:
Hi Carlos,
[...]
I found this:
yes, exactly. And furthermore you have to obey the combinations for one or all machines being virtual, i.e. host time and guest time 8-<
Mmm. With virtual machines my preference is to sync only the host. The virtual machine(s) get their time via guest addition of the virtualisation platform chosen. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sat, Apr 25, 2020, 04:49 Michael Hirmke <mh@mike.franken.de> wrote:
Hi Tomas,
On Fri, Apr 24, 2020, 09:27 Per Jessen <per@computer.org> wrote:
Michael Hirmke wrote:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook. I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient?
That depends on your requirements, how accurate do you need laptop time to be? chrony sounds like it would be fine for you.
If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf.
The dhcp infos are written to a file, for instance:
/var/lib/dhcpcd/dhcpcd-eth0.info
contains lines of "variable=value". Somehow chromy grabs hold of that.
Probably slightly different with NetworkManager.
Peter
I do not understand why would you want to change ntp server depending on whichever way you connect to a network. Unless you need local ntp on lan(s) and different one elsewhere.
Perhaps my wording was not correct - I connect to different networks with my different interfaces.
That makes perfect sense that you need to follow local NTP. I was under impression that this is ordinary standalone client/laptop.
I personally do not need better time precision than ~ 1s to keep make happy
when using network storage - for that any pool.ntp.org is good enough and it works everywhere, including LTE.
If you'd use kerberos, you would also need a precise time!
Am I missing something?
Tomas
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
24.04.2020 18:29, Michael Hirmke пишет:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook.
timedatectl is used to enable/disable systemd-timesyncd which implements SNTP to periodically poll time server(s). systemd-timesyncd obtains list of servers from static configuration and from systemd-networkd. Whether systemd-networkd requests list of NTP servers from DHCP v4/v6 server is per-interface configurable. See man timedatectl man timed-timesyncd man systemd.network If systemd-networkd is not used to manage network, you cannot use DHCP to fetch NTP servers for systemd-timesyncd. chrony comes with dhclient hook script that updates running chronyd with NTP server(s) received from DHCP server and stores NTP servers in well known location that is used to prime time servers list on (re-)starting chronyd.service. If dhclient is not used, it is up to you to provide suitable hook for your DHCP client implementation. This probably includes wicked, at least I do not see any extensions for dealing with chrony. dhclient is NetworkManager default (at least on Leap 15.1) so NeworkManager should use the same dhclient hook.
I regularily use a LAN connection, WiFi connections and LTE connections. In every case the network information is fetched via dhcp. Do I need chrony in this environment? Or is the systemd timedatectl service sufficient?
Timedatectl is not service. Service is systemd-timesyncd.
If I need chrony, how does chrony get the ntp server address from dhcp? I don't want to change it manually in chrony.conf.
I tried different constellations, but the results didn't seem to be consistent in a way I could understand.
TIA.
Bye. Michael.
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi Andrei, thx for your explanations!
24.04.2020 18:29, Michael Hirmke ?????:
Hi *,
I tried to understand the relation between chrony, timedatectl, dhcp and NetworkManager on my Tumbleweed notebook.
timedatectl is used to enable/disable systemd-timesyncd which implements SNTP to periodically poll time server(s). systemd-timesyncd obtains list of servers from static configuration and from systemd-networkd. Whether systemd-networkd requests list of NTP servers from DHCP v4/v6 server is per-interface configurable. See
man timedatectl man timed-timesyncd man systemd.network
If systemd-networkd is not used to manage network, you cannot use DHCP to fetch NTP servers for systemd-timesyncd.
ok, so in this case - not using systemd-networkd, but using dhcp, I have to use chrony, if I want to get ntp servers via dhcp - right? [...]
Timedatectl is not service. Service is systemd-timesyncd.
Of course, my mistake. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi again, I disabled systemd-timesyncd and reinstalled chrony. But NetworkManager doesn't seem to accept the ntp server it got from dhcp. NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1' NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers /var/run/netconfig/NetworkManager.netconfig and /var/run/netconfig/chrony.servers are empty though. If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above. What am I missing here? Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi again,
I disabled systemd-timesyncd and reinstalled chrony. But NetworkManager doesn't seem to accept the ntp server it got from dhcp.
NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1' NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers
/var/run/netconfig/NetworkManager.netconfig and
sorry, my mistake - this file of course isn't empty, but doesn't contain ntp server data.
/var/run/netconfig/chrony.servers are empty though.
This one indeed is empty.
If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above.
What am I missing here?
Bye. Michael. -- Michael Hirmke
-- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
25.04.2020 16:45, Michael Hirmke пишет:
Hi again,
I disabled systemd-timesyncd and reinstalled chrony. But NetworkManager doesn't seem to accept the ntp server it got from dhcp.
NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1'
This is internal NetworkManager DHCP client, so dhclient hook is not called.
NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers
NetworkManager calls netconfig only for DNS updates, it does not provide NTP information.
/var/run/netconfig/NetworkManager.netconfig and /var/run/netconfig/chrony.servers are empty though.
If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above.
What am I missing here?
Distribution and version you are running, NetworkManager.conf? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
25.04.2020 17:33, Andrei Borzenkov пишет:
25.04.2020 16:45, Michael Hirmke пишет:
Hi again,
I disabled systemd-timesyncd and reinstalled chrony. But NetworkManager doesn't seem to accept the ntp server it got from dhcp.
NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1'
This is internal NetworkManager DHCP client, so dhclient hook is not called.
NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers
NetworkManager calls netconfig only for DNS updates, it does not provide NTP information.
And it would not work anyway. Of course bug number that is referenced in netconfig commit that added chrony support is private. So much about SLE/openSUSE integration ...
/var/run/netconfig/NetworkManager.netconfig and /var/run/netconfig/chrony.servers are empty though.
If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above.
What am I missing here?
Distribution and version you are running, NetworkManager.conf?
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
[...]
And it would not work anyway. Of course bug number that is referenced in netconfig commit that added chrony support is private. So much about SLE/openSUSE integration ...
Sorry, I don't understand this hint. You mean, there is a bug report already, but it isn't public? [...] Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 25/04/2020 18.17, Michael Hirmke wrote:
[...]
And it would not work anyway. Of course bug number that is referenced in netconfig commit that added chrony support is private. So much about SLE/openSUSE integration ...
Sorry, I don't understand this hint.
It is not a hint...
You mean, there is a bug report already, but it isn't public?
Yes, I think so. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
[...]
NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1'
This is internal NetworkManager DHCP client, so dhclient hook is not called.
Ok. For me this looks really confusing - NM knows about the ntp server, but nevertheless it is not used 8-<
NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers
NetworkManager calls netconfig only for DNS updates, it does not provide NTP information.
But why does it state "resolved ntp-policy 'auto'"?
/var/run/netconfig/NetworkManager.netconfig and /var/run/netconfig/chrony.servers are empty though.
If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above.
What am I missing here?
Distribution and version you are running, NetworkManager.conf?
openSUSE Tumbleweed. [main] plugins=keyfile [connectivity] uri=http://conncheck.opensuse.org Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
25.04.2020 19:15, Michael Hirmke пишет:
[...]
NetworkManager[6990]: <info> [1587822149.8981] dhcp4 (p3p2): option ntp_servers => '192.168.1.1' NetworkManager[6990]: <info> [1587822149.8982] dhcp4 (p3p2): option requested_ntp_servers => '1'
This is internal NetworkManager DHCP client, so dhclient hook is not called.
Ok. For me this looks really confusing - NM knows about the ntp server, but nevertheless it is not used 8-<
NetworkManager[7119]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime NetworkManager[7119]: debug: ntp-runtime Module called NetworkManager[7119]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK * NetworkManager' NetworkManager[7119]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: get_ntp_settings: NTP_SERVER_LIST='' NetworkManager[7119]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig NetworkManager[7119]: debug: ntp servers written to /var/run/netconfig/chrony.servers
NetworkManager calls netconfig only for DNS updates, it does not provide NTP information.
But why does it state "resolved ntp-policy 'auto'"?
Because this is current value of ntp-policy. It does not mean someone provided actual values to fill in NTP servers.
/var/run/netconfig/NetworkManager.netconfig and /var/run/netconfig/chrony.servers are empty though.
If I add an ip address to NETCONFIG_NTP_STATIC_SERVERS in /etc/sysconfig/network/config, this server shows up in both files mentioned above.
What am I missing here?
Distribution and version you are running, NetworkManager.conf?
openSUSE Tumbleweed.
Oh. You are not newbie on this list to not know that distribution and version are essential to get proper support. So far you just wasted your and my time. 1. Tumbleweed changed default NetworkManager DHCP client to internal. Which matches your information. 2. Tumbleweed completely broke integration of chrony with dhclient which means even changing client to dhclient won't help. It probably works with wicked now for a change. So using wicked instead of NetworkManager may work If you need NetworkManager and feel adventurous you can a) open NetworkManager upstream bug report about calling netconfig for NTP in addition to DNS b) try NetworkManager with dhclient and if it does not work open openSUSE bug report against chrony c) write NetworkManager dispatcher script to e.g. feed NTP data to netconfig
[main] plugins=keyfile
[connectivity] uri=http://conncheck.opensuse.org
Thx and bye. Michael.
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
[...]
NetworkManager calls netconfig only for DNS updates, it does not provide NTP information.
But why does it state "resolved ntp-policy 'auto'"?
Because this is current value of ntp-policy. It does not mean someone provided actual values to fill in NTP servers.
[...]
Distribution and version you are running, NetworkManager.conf?
openSUSE Tumbleweed.
Oh. You are not newbie on this list to not know that distribution and version are essential to get proper support. So far you just wasted your and my time.
Sorry for that 8-< I just wanted to understand the general relationship between the different pieces. I was not aware of differences between openSUSE flavours, that use NetworkManager.
1. Tumbleweed changed default NetworkManager DHCP client to internal. Which matches your information.
2. Tumbleweed completely broke integration of chrony with dhclient which means even changing client to dhclient won't help. It probably works with wicked now for a change.
So in fact I can uninstall chrony, use systemd-timesyncd and won't lose antyhing?
So using wicked instead of NetworkManager may work
If you need NetworkManager and feel adventurous you can
a) open NetworkManager upstream bug report about calling netconfig for NTP in addition to DNS
b) try NetworkManager with dhclient and if it does not work open openSUSE bug report against chrony
Opening bugs against NM in the past led to discussions, why I want/need the feature in question. So I guess I will avoid that.
c) write NetworkManager dispatcher script to e.g. feed NTP data to netconfig
Presumably I will go this way. Thx for your patience. You seem a little bit upset about the implemention in Tumbleweed!?! Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
mh＠mike.franken.de -
Per Jessen -
Tomas Kuchta