Hi, Look at this output on a newly installed Leap 15.2 system: arlos@Rescate:~> grep chrony /var/log/messages 2020-09-04T01:55:00.304034+02:00 install chronyd[1465]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-04T01:55:12.502311+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T01:56:16.829596+02:00 install chronyd[1465]: Selected source 178.255.228.77 2020-09-04T01:59:30.696451+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T02:25:17.504984+02:00 install chronyd[1465]: Source 2606:4700:f1::123 replaced with 2001:720:424:1::1:15 2020-09-04T02:55:08.658645+02:00 install chronyd[1465]: Source 2606:4700:f1::1 replaced with 2001:720:1014:a202::2 2020-09-04T03:25:01.548423+02:00 install chronyd[1465]: Source 2001:720:424:1::1:15 replaced with 178.32.88.247 2020-09-04T03:54:53.688796+02:00 install chronyd[1465]: Source 2001:720:1014:a201::2 replaced with 2606:4700:f1::1 2020-09-04T04:24:45.734513+02:00 install chronyd[1465]: Source 2001:720:1014:a202::2 replaced with 2001:720:424:1::1:15 carlos@Rescate:~> Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router. carlos@Rescate:~> ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::b24b:5404:16c2:b3f6 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 91343 bytes 111136210 (105.9 MiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 32678 bytes 2686720 (2.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 What should I look at? The system is with default configurations, installed hours ago. -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-09-03 22:00:54 Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
arlos@Rescate:~> grep chrony /var/log/messages 2020-09-04T01:55:00.304034+02:00 install chronyd[1465]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-04T01:55:12.502311+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T01:56:16.829596+02:00 install chronyd[1465]: Selected source 178.255.228.77 2020-09-04T01:59:30.696451+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T02:25:17.504984+02:00 install chronyd[1465]: Source 2606:4700:f1::123 replaced with 2001:720:424:1::1:15 2020-09-04T02:55:08.658645+02:00 install chronyd[1465]: Source 2606:4700:f1::1 replaced with 2001:720:1014:a202::2 2020-09-04T03:25:01.548423+02:00 install chronyd[1465]: Source 2001:720:424:1::1:15 replaced with 178.32.88.247 2020-09-04T03:54:53.688796+02:00 install chronyd[1465]: Source 2001:720:1014:a201::2 replaced with 2606:4700:f1::1 2020-09-04T04:24:45.734513+02:00 install chronyd[1465]: Source 2001:720:1014:a202::2 replaced with 2001:720:424:1::1:15 carlos@Rescate:~>
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
carlos@Rescate:~> ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::b24b:5404:16c2:b3f6 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 91343 bytes 111136210 (105.9 MiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 32678 bytes 2686720 (2.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
What should I look at? The system is with default configurations, installed hours ago.
-- Cheers
Carlos E. R. (from 15.1 x86_64 at Telcontar)
You have, of course, disabled IPv6 in YaST => Network Settings? Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 05.13, J Leslie Turriff wrote:
On 2020-09-03 22:00:54 Carlos E. R. wrote:
What should I look at? The system is with default configurations, installed hours ago.
You have, of course, disabled IPv6 in YaST => Network Settings?
Certainly not. Then I would not be at "default settings" as I said. The system should be clever enough to deduce that there is no IPv6 connectivity to internet >;-) Other programs switch immediately to the IPv4 variant. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-09-03 22:46:02 Carlos E. R. wrote:
On 04/09/2020 05.13, J Leslie Turriff wrote:
On 2020-09-03 22:00:54 Carlos E. R. wrote:
What should I look at? The system is with default configurations, installed hours ago.
You have, of course, disabled IPv6 in YaST => Network Settings?
Certainly not.
Then I would not be at "default settings" as I said. Oops; my bad.
The system should be clever enough to deduce that there is no IPv6 connectivity to internet >;-)
Other programs switch immediately to the IPv4 variant.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-09-03 22:00:54 Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
arlos@Rescate:~> grep chrony /var/log/messages 2020-09-04T01:55:00.304034+02:00 install chronyd[1465]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-04T01:55:12.502311+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T01:56:16.829596+02:00 install chronyd[1465]: Selected source 178.255.228.77 2020-09-04T01:59:30.696451+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T02:25:17.504984+02:00 install chronyd[1465]: Source 2606:4700:f1::123 replaced with 2001:720:424:1::1:15 2020-09-04T02:55:08.658645+02:00 install chronyd[1465]: Source 2606:4700:f1::1 replaced with 2001:720:1014:a202::2 2020-09-04T03:25:01.548423+02:00 install chronyd[1465]: Source 2001:720:424:1::1:15 replaced with 178.32.88.247 2020-09-04T03:54:53.688796+02:00 install chronyd[1465]: Source 2001:720:1014:a201::2 replaced with 2606:4700:f1::1 2020-09-04T04:24:45.734513+02:00 install chronyd[1465]: Source 2001:720:1014:a202::2 replaced with 2001:720:424:1::1:15 carlos@Rescate:~>
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
carlos@Rescate:~> ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::b24b:5404:16c2:b3f6 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 91343 bytes 111136210 (105.9 MiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 32678 bytes 2686720 (2.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
What should I look at? The system is with default configurations, installed hours ago.
-- Cheers
Carlos E. R. (from 15.1 x86_64 at Telcontar)
Looking at info, I see -4 and -6 options, but no description of which is the default; perhaps someone has changed it to -6? There is no relevant entry in the /etc/chrony.conf on my (15.1) machine; if there's none in yours, it must be using the internal default? Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 06.08, J Leslie Turriff wrote:
On 2020-09-03 22:00:54 Carlos E. R. wrote:
Looking at info, I see -4 and -6 options, but no description of which is the default; perhaps someone has changed it to -6? There is no relevant entry in the /etc/chrony.conf on my (15.1) machine; if there's none in yours, it must be using the internal default?
No, that would be here: Rescate:~ # systemctl cat chronyd # /usr/lib/systemd/system/chronyd.service [Unit] Description=NTP client/server Documentation=man:chronyd(8) man:chrony.conf(5) After=nss-lookup.target Wants=network.target After=network.target Wants=time-sync.target Before=time-sync.target Conflicts=ntpd.service systemd-timesyncd.service ConditionCapability=CAP_SYS_TIME [Service] Type=forking PIDFile=/var/run/chronyd.pid EnvironmentFile=-/etc/sysconfig/chronyd ExecStart=/usr/sbin/chronyd $OPTIONS <==== ExecStartPost=/usr/lib/chrony/helper update-daemon PrivateTmp=yes ProtectHome=yes ProtectSystem=full [Install] WantedBy=multi-user.target Rescate:~ # and: Rescate:~ # cat /etc/sysconfig/chronyd ## Path: Network/Chrony ## Description: Chrony time synchronization settings ## Type: yesno ## Default: "yes" ## ServiceRestart: chronyd # # Resolve hostnames with IPv4 # CHRONY_IPV4="yes" ## Type: yesno ## Default: "yes" ## ServiceRestart: chronyd # # Resolve hostnames with IPv6 # CHRONY_IPV6="yes" <================== ## Type: yesno ## Default: "yes" ## ServiceRestart: chronyd # # Lock the chrony daemon process into RAM, preventing it from swapping out # CHRONY_LOCK_IN_RAM="no" Rescate:~ # So I can switch it off in config. Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc. I'm waiting for James Knot to chime in. Per Jessen has already answered ;-) The thing is, now I can configure IPv6 off in chronyd, but as the next time the machine may be used on a different network (it is not my machine, after all), we will never know if IPv6 will work there. IMHO, programs should autodetect external IPv6 automatically, different from the LAN being IPv6 capable. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc.
I think people who believe disabling IPv6 will help their systems should just do so. -- Per Jessen, Zürich (20.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 11.51, Per Jessen wrote:
Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc.
I think people who believe disabling IPv6 will help their systems should just do so.
Well, it is just that the default configuration doesn't work. Programs think that IPv6 to internet think they can use it, when they can not. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-09-04 04:39:14 Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc.
That would depend on one's location. Some countries use IPv6 in preference to IPv4 others, vice versa. I suspect that's why they are both enabled by default. Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/2020 10.56, J Leslie Turriff wrote:
On 2020-09-04 04:39:14 Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc.
That would depend on one's location. Some countries use IPv6 in preference to IPv4 others, vice versa. I suspect that's why they are both enabled by default.
My router is supplied by the ISP and is prepared or configured by the ISP to provide IPv6 if available. But at the same time, the ISP does not provide IPv6, at least not to home users. They did a test run at some point, but they did not deploy it. I believe that now they supply a different router. And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available: thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 33373876 bytes 49000013687 (45.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14198888 bytes 1510736559 (1.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-09-08 04:08:53 Carlos E. R. wrote:
On 08/09/2020 10.56, J Leslie Turriff wrote:
On 2020-09-04 04:39:14 Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years - ;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc.
That would depend on one's location. Some countries use IPv6 in preference to IPv4 others, vice versa. I suspect that's why they are both enabled by default.
My router is supplied by the ISP and is prepared or configured by the ISP to provide IPv6 if available. But at the same time, the ISP does not provide IPv6, at least not to home users. They did a test run at some point, but they did not deploy it.
I believe that now they supply a different router.
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 33373876 bytes 49000013687 (45.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14198888 bytes 1510736559 (1.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
How strange; on my machine, I just checked YaST => System => Network Settings [Global Options], where I see that Enable IPv6 is checked; but ifconfig shows |eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 | ether 2c:4d:54:cf:fb:72 txqueuelen 1000 (Ethernet) | RX packets 2806936 bytes 3379103019 (3.1 GiB) | RX errors 0 dropped 0 overruns 0 frame 0 | TX packets 1799006 bytes 173870409 (165.8 MiB) | TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 | device interrupt 16 memory 0xf7500000-f7520000 (no inet addresses at all). Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 04:37 -0500, J Leslie Turriff escribió:
On 2020-09-08 04:08:53 Carlos E. R. wrote:
On 08/09/2020 10.56, J Leslie Turriff wrote:
On 2020-09-04 04:39:14 Carlos E.R. wrote:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid 0x20<link> ether f8:75:a4:e2:4b:48 txqueuelen 1000 (Ethernet) RX packets 33373876 bytes 49000013687 (45.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14198888 bytes 1510736559 (1.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
How strange; on my machine, I just checked YaST => System => Network Settings [Global Options], where I see that Enable IPv6 is checked; but ifconfig shows
|eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 | ether 2c:4d:54:cf:fb:72 txqueuelen 1000 (Ethernet) | RX packets 2806936 bytes 3379103019 (3.1 GiB) | RX errors 0 dropped 0 overruns 0 frame 0 | TX packets 1799006 bytes 173870409 (165.8 MiB) | TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 | device interrupt 16 memory 0xf7500000-f7520000
(no inet addresses at all).
Then you should have it on another interface. But eth0 has sent and received data. How strange. Another command - if you are sure you use eth0 Andor:~ # ifstatus addr eth0 eth0 up link: #2, state up, mtu 1500 type: ethernet, hwaddr 00:d8:61:a1:5a:bd config: compat:suse:/etc/sysconfig/network/ifcfg-eth0 leases: ipv4 dhcp granted leases: ipv6 dhcp requesting addr: ipv4 192.168.1.136/24 [dhcp] route: ipv4 default via 192.168.1.1 [dhcp] Andor:~ # -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available". On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that. -- Per Jessen, Zürich (17.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-) -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it. -- Per Jessen, Zürich (20.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-? I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2 -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good. -- Per Jessen, Zürich (18.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió:
Carlos E. R. wrote:
> And openSUSE machines get/create a linklocal(?) IPv6 addresses, > so it seems that programs inside think that IPv6 is available: > > thinkpadE15:~ # ifconfig > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.1.134 netmask 255.255.255.0 broadcast > 192.168.1.255 > inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid
The IPv6 link-local (LL) setup is needed for IPv6 configuration, but it does not mean "that programs inside think that IPv6 is available".
On a machine with LL only, any application that attempts to connect to a non-LL IPv6 address will receive a "network unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
Now it (chrony) knows that address could not be reached. Good.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address.
I'm stopping here, this talk is only creating superfluous noise, and we are not getting anywhere. Feel free to take it to off-topic. -- Per Jessen, Zürich (16.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 22:23 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió: > Carlos E. R. wrote:
> >> And openSUSE machines get/create a linklocal(?) IPv6 addresses, >> so it seems that programs inside think that IPv6 is available: >> >> thinkpadE15:~ # ifconfig >> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >> inet 192.168.1.134 netmask 255.255.255.0 broadcast >> 192.168.1.255 >> inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid > > The IPv6 link-local (LL) setup is needed for IPv6 configuration, > but it does not mean "that programs inside think that IPv6 is > available". > > On a machine with LL only, any application that attempts to > connect to a non-LL IPv6 address will receive a "network > unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
Now it (chrony) knows that address could not be reached. Good.
No, it keeps trying for hours with other IPv6 addresses. IMHO it is a bug.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address.
I'm stopping here, this talk is only creating superfluous noise, and we are not getting anywhere. Feel free to take it to off-topic.
Ok. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
On 9/8/20 4:42 PM, Carlos E. R. wrote:
No, it keeps trying for hours with other IPv6 addresses. IMHO it is a bug.
It's not a bug. It's a feature! ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 08 Sep 2020 22:23:13 +0200 Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
El 2020-09-08 a las 12:09 +0200, Per Jessen escribió: > Carlos E. R. wrote:
> >> And openSUSE machines get/create a linklocal(?) IPv6 >> addresses, so it seems that programs inside think that IPv6 >> is available: >> >> thinkpadE15:~ # ifconfig >> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >> inet 192.168.1.134 netmask 255.255.255.0 broadcast >> 192.168.1.255 >> inet6 fe80::912a:e81d:940:6768 prefixlen 64 >> scopeid > > The IPv6 link-local (LL) setup is needed for IPv6 > configuration, but it does not mean "that programs inside > think that IPv6 is available". > > On a machine with LL only, any application that attempts to > connect to a non-LL IPv6 address will receive a "network > unreachable" error and just needs to handle that.
Well, that is precissely my point! chrony should know that there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
Now it (chrony) knows that address could not be reached. Good.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address.
I'm stopping here, this talk is only creating superfluous noise, and we are not getting anywhere. Feel free to take it to off-topic.
I don't understand this last comment, Per. It seems like you perhaps haven't understood/absorbed the whole thread and Carlos is trying to catch you up to where he's at. I thought he was succeeding but it seems not? Sorry, I don't know enough to make a substantive comment. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Tue, 08 Sep 2020 22:23:13 +0200 Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió:
> El 2020-09-08 a las 12:09 +0200, Per Jessen escribió: >> Carlos E. R. wrote:
>> >>> And openSUSE machines get/create a linklocal(?) IPv6 >>> addresses, so it seems that programs inside think that IPv6 >>> is available: >>> >>> thinkpadE15:~ # ifconfig >>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>> inet 192.168.1.134 netmask 255.255.255.0 broadcast >>> 192.168.1.255 >>> inet6 fe80::912a:e81d:940:6768 prefixlen 64 >>> scopeid >> >> The IPv6 link-local (LL) setup is needed for IPv6 >> configuration, but it does not mean "that programs inside >> think that IPv6 is available". >> >> On a machine with LL only, any application that attempts to >> connect to a non-LL IPv6 address will receive a "network >> unreachable" error and just needs to handle that. > > Well, that is precissely my point! chrony should know that > there is no IPv6 and not try it :-)
The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
Now it (chrony) knows that address could not be reached. Good.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address.
I'm stopping here, this talk is only creating superfluous noise, and we are not getting anywhere. Feel free to take it to off-topic.
I don't understand this last comment, Per. It seems like you perhaps haven't understood/absorbed the whole thread and Carlos is trying to catch you up to where he's at. I thought he was succeeding but it seems not?
Hi Dave, I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function. -- Per Jessen, Zürich (15.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-09 a las 08:14 +0200, Per Jessen escribió:
Dave Howorth wrote:
On Tue, 08 Sep 2020 22:23:13 +0200 Per Jessen <> wrote:
Carlos E. R. wrote:
El 2020-09-08 a las 20:34 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-08 a las 19:27 +0200, Per Jessen escribió: >> El 2020-09-08 a las 12:09 +0200, Per Jessen escribió: >>> Carlos E. R. wrote:
>>> The IPv6 link-local (LL) setup is needed for IPv6 >>> configuration, but it does not mean "that programs inside >>> think that IPv6 is available". >>> >>> On a machine with LL only, any application that attempts to >>> connect to a non-LL IPv6 address will receive a "network >>> unreachable" error and just needs to handle that. >> >> Well, that is precissely my point! chrony should know that >> there is no IPv6 and not try it :-) > > The easiest way to find out is to try it.
Sorry, try what? :-?
Try to reach an IPv6 address.
It fails, obviously.
Now it (chrony) knows that address could not be reached. Good.
I got a default network install with a default chrony install, and it does try to use Ipv6, on Leap 15.2
Good.
No, bad, as we determined there is no IPv6 and that the program (chrony) should know it as there is no routeable IPv6 address.
I'm stopping here, this talk is only creating superfluous noise, and we are not getting anywhere. Feel free to take it to off-topic.
I don't understand this last comment, Per. It seems like you perhaps haven't understood/absorbed the whole thread and Carlos is trying to catch you up to where he's at. I thought he was succeeding but it seems not?
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed. When it happened, I did not know how to verify. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse). -- Per Jessen, Zürich (19.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse).
But I pasted my log, it showed problems: carlos@Rescate:~> grep chrony /var/log/messages 2020-09-04T01:55:00.304034+02:00 install chronyd[1465]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-04T01:55:12.502311+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T01:56:16.829596+02:00 install chronyd[1465]: Selected source 178.255.228.77 2020-09-04T01:59:30.696451+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T02:25:17.504984+02:00 install chronyd[1465]: Source 2606:4700:f1::123 replaced with 2001:720:424:1::1:15 2020-09-04T02:55:08.658645+02:00 install chronyd[1465]: Source 2606:4700:f1::1 replaced with 2001:720:1014:a202::2 2020-09-04T03:25:01.548423+02:00 install chronyd[1465]: Source 2001:720:424:1::1:15 replaced with 178.32.88.247 2020-09-04T03:54:53.688796+02:00 install chronyd[1465]: Source 2001:720:1014:a201::2 replaced with 2606:4700:f1::1 2020-09-04T04:24:45.734513+02:00 install chronyd[1465]: Source 2001:720:1014:a202::2 replaced with 2001:720:424:1::1:15 carlos@Rescate:~> -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse).
But I pasted my log, it showed problems:
I don't see any problems in what you posted. You also later posted output from "chronyc tracking", saying clearly it works fine. The log you posted looks like normal operations to me. The chrony faq says "The clients [chronies] will automatically replace the servers when they become unreachable, or otherwise unsuitable for synchronisation, with new servers from the pool." -- Per Jessen, Zürich (23.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-09 a las 15:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse).
But I pasted my log, it showed problems:
I don't see any problems in what you posted. You also later posted output from "chronyc tracking", saying clearly it works fine.
No, you are confused. At that point I had already disabled IPv6 in sysconfig/chronyd.
The log you posted looks like normal operations to me. The chrony faq says "The clients [chronies] will automatically replace the servers when they become unreachable, or otherwise unsuitable for synchronisation, with new servers from the pool."
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-09 a las 15:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse).
But I pasted my log, it showed problems:
I don't see any problems in what you posted. You also later posted output from "chronyc tracking", saying clearly it works fine.
No, you are confused. At that point I had already disabled IPv6 in sysconfig/chronyd.
Maybe you can post something that shows how it is _not_ working ? IMO, the log does not show any problems.
The log you posted looks like normal operations to me. The chrony faq says "The clients [chronies] will automatically replace the servers when they become unreachable, or otherwise unsuitable for synchronisation, with new servers from the pool."
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed. -- Per Jessen, Zürich (24.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-09 a las 15:35 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-09 a las 15:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
But I pasted my log, it showed problems:
I don't see any problems in what you posted. You also later posted output from "chronyc tracking", saying clearly it works fine.
No, you are confused. At that point I had already disabled IPv6 in sysconfig/chronyd.
Maybe you can post something that shows how it is _not_ working ? IMO, the log does not show any problems.
The log in the OP to me shows problems.
The log you posted looks like normal operations to me. The chrony faq says "The clients [chronies] will automatically replace the servers when they become unreachable, or otherwise unsuitable for synchronisation, with new servers from the pool."
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed.
Yes, IMO what happens is a problem. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed.
Yes, IMO what happens is a problem.
Then the next step is one of two - https://bugzilla.opensuse.org or the chrony mailing list: chrony-users@chrony.tuxfamily.org -- Per Jessen, Zürich (25.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-09 a las 17:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed.
Yes, IMO what happens is a problem.
Then the next step is one of two -
or the chrony mailing list:
chrony-users@chrony.tuxfamily.org
Yes, I was thinking of that, but I will loose access to that machine soon. Unless I switch some of my machines to chronyd. Just for comparison, see the log on the same machine when it does not try IPv6 servers: 2020-09-09T14:52:28.027807+02:00 thinkpadE15 chronyd[8184]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-09T14:52:28.028180+02:00 thinkpadE15 chronyd[8184]: Frequency 1.803 +/- 0.286 ppm read from /var/lib/chrony/drift 2020-09-09T14:52:36.282110+02:00 thinkpadE15 chronyd[8184]: Selected source 37.187.205.149 2020-09-09T14:58:00.921203+02:00 thinkpadE15 chronyd[8184]: Selected source 185.132.136.116 It is now 21:04 hours, and the log is silent, which means it has a correct source. When it uses IPv6 addresses, every half hour it tries another, because it does not work. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
Carlos E. R. wrote:
El 2020-09-09 a las 17:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed.
Yes, IMO what happens is a problem.
Then the next step is one of two -
or the chrony mailing list:
chrony-users@chrony.tuxfamily.org
Yes, I was thinking of that, but I will loose access to that machine soon. Unless I switch some of my machines to chronyd.
That is very easy to do, you can switch back and forth between ntp and chrony with two commands. systemctl disable --now ntpd systemctl enable --now chrony Go back to ntp: systemctl disable --now chrony systemctl enable --now ntpd
It is now 21:04 hours, and the log is silent, which means it has a correct source.
Actually, 'chronyc sources' will tell you that, not the log.
When it uses IPv6 addresses, every half hour it tries another, because it does not work.
That is an assumption - it probably works very well, but chrony might be looking for a better time source. (my guess). I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that? -- Per Jessen, Zürich (17.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/09/2020 09.26, Per Jessen wrote:
Carlos E. R. wrote:
...
Yes, I was thinking of that, but I will loose access to that machine soon. Unless I switch some of my machines to chronyd.
That is very easy to do, you can switch back and forth between ntp and chrony with two commands.
systemctl disable --now ntpd systemctl enable --now chrony
I know that :-D I have to make sure that my 15.1 laptop has it installed, and also that my scripts may have things to start/stop ntp when the machine hibernates or changes network. ...
I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that?
No, I changed nothing. Maybe you do not get in the default pool IPv6 addresses. Ha, It is happening again today: 2020-09-10T00:56:15.550071+02:00 thinkpadE15 chronyd[1256]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-10T00:56:15.550822+02:00 thinkpadE15 chronyd[1256]: Frequency -6.043 +/- 0.040 ppm read from /var/lib/chrony/drift 2020-09-10T01:15:20.928264+02:00 thinkpadE15 chronyd[1279]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-10T01:15:20.929226+02:00 thinkpadE15 chronyd[1279]: Frequency -6.043 +/- 0.040 ppm read from /var/lib/chrony/drift 2020-09-10T01:15:42.951674+02:00 thinkpadE15 chronyd[1279]: Selected source 185.132.136.116 2020-09-10T01:45:47.748265+02:00 thinkpadE15 chronyd[1279]: Source 2001:720:1014:a202::2 replaced with 178.32.88.247 2020-09-10T02:15:39.865731+02:00 thinkpadE15 chronyd[1279]: Source 2606:4700:f1::1 replaced with 51.38.162.10 Well, not happening, but happened. Two sources replaced. It is just chance. thinkpadE15:~ # chronyc tracking Reference ID : B9848874 (elv06.icfo.es) Stratum : 3 Ref time (UTC) : Thu Sep 10 10:08:24 2020 System time : 0.000211445 seconds fast of NTP time Last offset : +0.000166632 seconds RMS offset : 0.000228474 seconds Frequency : 3.062 ppm fast Residual freq : +0.001 ppm Skew : 0.015 ppm Root delay : 0.039669745 seconds Root dispersion : 0.003374388 seconds Update interval : 1026.7 seconds Leap status : Normal thinkpadE15:~ # thinkpadE15:~ # chronyc sources -v 210 Number of sources = 12 .-- Source mode '^' = server, '=' = peer, '#' = local clock. / .- Source state '*' = current synced, '+' = combined , '-' = not combined, | / '?' = unreachable, 'x' = time may be in error, '~' = time too variable. || .- xxxx [ yyyy ] +/- zzzz || Reachability register (octal) -. | xxxx = adjusted offset, || Log2(Polling interval) --. | | yyyy = measured offset, || \ | | zzzz = estimated error. || | | \ MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* elv06.icfo.es 2 10 377 31m -589us[ -422us] +/- 21ms ^- dns01.masbytes.es 3 10 377 602 +8318us[+8318us] +/- 136ms ^+ ntp.redimadrid.es 2 10 377 607 +22us[ +22us] +/- 28ms ^+ 213.251.52.234 2 10 377 650 +1446us[+1446us] +/- 76ms ^+ 90.165.120.190 2 10 377 550 +367us[ +367us] +/- 64ms ^+ 178.255.228.77 2 10 377 601 -1628us[-1628us] +/- 34ms ^+ time.cloudflare.com 3 10 377 672 +255us[ +255us] +/- 25ms ^+ sarah.vandalsweb.com 2 10 377 32 +113us[ +113us] +/- 65ms ^- ntp9.kashra-server.com 2 10 377 386 +3489us[+3489us] +/- 37ms ^+ time.cloudflare.com 3 10 377 612 +1697us[+1697us] +/- 27ms ^+ dnscache-madrid.ntt.eu 2 10 377 637 +456us[ +456us] +/- 66ms ^+ fw.dessoft.es 2 10 377 896 +563us[ +563us] +/- 44ms thinkpadE15:~ # Well, chrony does seem to handle the situation, but IMO it should not even try IPv6 as there is no routable IPv6 interface in the machine. Maybe, as James says, it is not a bug but a feature. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 10/09/2020 09.26, Per Jessen wrote:
I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that?
No, I changed nothing.
Maybe you do not get in the default pool IPv6 addresses.
2.opensuse.pool.ntp.org - four IPv6 addresses. office24:~ # host 2.opensuse.pool.ntp.org 2.opensuse.pool.ntp.org has address 195.186.1.101 2.opensuse.pool.ntp.org has address 62.202.141.23 2.opensuse.pool.ntp.org has address 162.159.200.123 2.opensuse.pool.ntp.org has address 193.33.30.39 2.opensuse.pool.ntp.org has IPv6 address 2001:470:b6d6:4::12 2.opensuse.pool.ntp.org has IPv6 address 2001:620:0:fffc::123:47 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::1 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::123 I have just switched my main laptop (Leap 15.2) to ipv4-only and chrony, same thing, no such messages. What does 'ip -6 route show' say on your machine, with ipv6 enabled? I would expect 2 entries, ::1 for loopback and fe80::/64 for eth0.
Well, chrony does seem to handle the situation, but IMO it should not even try IPv6 as there is no routable IPv6 interface in the machine.
An application has to try it to find out, that's the point. Same for IPv4 for that matter. -- Per Jessen, Zürich (22.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/09/2020 13.15, Per Jessen wrote:
Carlos E. R. wrote:
On 10/09/2020 09.26, Per Jessen wrote:
I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that?
No, I changed nothing.
Maybe you do not get in the default pool IPv6 addresses.
2.opensuse.pool.ntp.org - four IPv6 addresses.
office24:~ # host 2.opensuse.pool.ntp.org 2.opensuse.pool.ntp.org has address 195.186.1.101 2.opensuse.pool.ntp.org has address 62.202.141.23 2.opensuse.pool.ntp.org has address 162.159.200.123 2.opensuse.pool.ntp.org has address 193.33.30.39 2.opensuse.pool.ntp.org has IPv6 address 2001:470:b6d6:4::12 2.opensuse.pool.ntp.org has IPv6 address 2001:620:0:fffc::123:47 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::1 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::123
I have just switched my main laptop (Leap 15.2) to ipv4-only and chrony, same thing, no such messages. What does 'ip -6 route show' say on your machine, with ipv6 enabled? I would expect 2 entries, ::1 for loopback and fe80::/64 for eth0.
thinkpadE15:~ # ip -6 route show ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev wlan1 proto kernel metric 600 pref medium thinkpadE15:~ # But those are not routable. The laptop is neither switched for -4 or -6. It has whatever network manager decides based on the router given information, automatically.
Well, chrony does seem to handle the situation, but IMO it should not even try IPv6 as there is no routable IPv6 interface in the machine.
An application has to try it to find out, that's the point. Same for IPv4 for that matter.
thinkpadE15:~ # ping 2001:470:b6d6:4::12 connect: Network is unreachable thinkpadE15:~ # ping6 2001:470:b6d6:4::12 connect: Network is unreachable thinkpadE15:~ # Instant answer. No need to waste half an hour trying (chrony tries for half an hour). -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 9/8/20 5:08 AM, Carlos E. R. wrote:
My router is supplied by the ISP and is prepared or configured by the ISP to provide IPv6 if available. But at the same time, the ISP does not provide IPv6, at least not to home users. They did a test run at some point, but they did not deploy it.
If your ISP doesn't provide IPv6, you can use a tunnel broker, such as he.net, to get it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 2020-09-08 a las 09:07 -0400, James Knott escribió:
On 9/8/20 5:08 AM, Carlos E. R. wrote:
My router is supplied by the ISP and is prepared or configured by the ISP to provide IPv6 if available. But at the same time, the ISP does not provide IPv6, at least not to home users. They did a test run at some point, but they did not deploy it.
If your ISP doesn't provide IPv6, you can use a tunnel broker, such as he.net, to get it.
Yes, I tried once, I have an account there, but failed to set it up. Anyway, that is not the issue. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))
On 9/8/20 5:08 AM, Carlos E. R. wrote:
And openSUSE machines get/create a linklocal(?) IPv6 addresses, so it seems that programs inside think that IPv6 is available:
thinkpadE15:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::912a:e81d:940:6768 prefixlen 64 scopeid 0x20<link>
Every IPv6 capable device gets a link local address. However, if it doesn't also get a routeable address it will not assume IPv6 is available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/8/20 4:56 AM, J Leslie Turriff wrote:
On 2020-09-04 04:39:14 Carlos E.R. wrote:
Still, there is the philosophical question, which we have been discussing here for years -;-) - whether it is wise for the default being allowing IPv6, or programs preferring it, etc etc. That would depend on one's location. Some countries use IPv6 in preference to IPv4 others, vice versa. I suspect that's why they are both enabled by default.
Actually, it's usually determined by the operating system. Linux defaults to IPv6 when available. Of course, some apps can be configured to prefer IPv4. Also, it has nothing to do with countries. The world is moving to IPv6, though some countries are slower than others. Frankly, avoiding moving to IPv6 is head in the sand stupidity. IPv4 hasn't been adequate for over 20 years. I have been running IPv6 on my home network for over 10 years. Both my ISP and cell carrier (same company) provide IPv6. In fact, my cell phone is IPv6 only. It has to use 464XLAT to handle IPv4 only sites. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
[snip]
What should I look at? The system is with default configurations, installed hours ago.
First question - is there a problem? I don't use chrony myself, but it looks like it selected two IPv4 sources, which sounds good. IIUC, the "source replaced with" message simply means that an unreachable server was swapped out for another one (not necessarily more reachable). -- Per Jessen, Zürich (15.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 08.11, Per Jessen wrote:
Carlos E. R. wrote:
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
[snip]
What should I look at? The system is with default configurations, installed hours ago.
First question - is there a problem? I don't use chrony myself, but it looks like it selected two IPv4 sources, which sounds good. IIUC, the "source replaced with" message simply means that an unreachable server was swapped out for another one (not necessarily more reachable).
Well, I don't know if there is a problem. Hard to see if the clock is off or not. To me it looks like if first tries an IPv4 address, then one minute later it selects another, I guess because the first one doesn't work. After 3 minutes it selects another. This doesn't look to me like it is using 3 ipv4 sources in parallel, but maybe I'm reading wrong. Then half an hour later it replaces one ipv6 source with another. And repeats this several times about every half an hour. Thew laptop has been suspended for the night, and now (via ssh) I see: 2020-09-04T05:24:54.104836+02:00 install chronyd[1465]: Selected source 213.251.52.234 2020-09-04T05:25:59.368539+02:00 install chronyd[1465]: Selected source 185.132.136.116 2020-09-04T05:30:13.671323+02:00 install chronyd[1465]: Source 138.68.46.177 offline 2020-09-04T05:30:13.671570+02:00 install chronyd[1465]: Source 178.255.228.77 offline 2020-09-04T05:30:13.671761+02:00 install chronyd[1465]: Source 178.32.88.247 offline 2020-09-04T05:30:13.671940+02:00 install chronyd[1465]: Source 213.251.52.234 offline 2020-09-04T05:30:13.672196+02:00 install chronyd[1465]: Source 5.56.160.3 offline 2020-09-04T05:30:13.672371+02:00 install chronyd[1465]: Source 51.38.162.10 offline 2020-09-04T05:30:13.672541+02:00 install chronyd[1465]: Source 81.19.96.148 offline 2020-09-04T05:30:13.672700+02:00 install chronyd[1465]: Source 95.39.224.42 offline 2020-09-04T05:30:13.672869+02:00 install chronyd[1465]: Source 185.132.136.116 offline 2020-09-04T05:30:13.673032+02:00 install chronyd[1465]: Can't synchronise: no selectable sources 2020-09-04T11:14:35.792823+02:00 install chronyd[1465]: Forward time jump detected! all that may be a side effect of suspend. Then: 2020-09-04T11:14:35.793005+02:00 install chronyd[1465]: Source 185.132.136.116 online 2020-09-04T11:14:35.793125+02:00 install chronyd[1465]: Source 213.251.52.234 online 2020-09-04T11:14:35.793252+02:00 install chronyd[1465]: Source 5.56.160.3 online 2020-09-04T11:14:35.793348+02:00 install chronyd[1465]: Source 95.39.224.42 online 2020-09-04T11:14:35.793427+02:00 install chronyd[1465]: Source 178.255.228.77 online 2020-09-04T11:14:35.793510+02:00 install chronyd[1465]: Source 138.68.46.177 online 2020-09-04T11:14:35.793600+02:00 install chronyd[1465]: Source 178.32.88.247 online 2020-09-04T11:14:35.793681+02:00 install chronyd[1465]: Source 81.19.96.148 online 2020-09-04T11:14:35.793758+02:00 install chronyd[1465]: Source 51.38.162.10 online 2020-09-04T11:16:47.544563+02:00 install chronyd[1465]: Selected source 185.132.136.116 Rescate:~ # This morning it seems to use IpV4 addresses. But I guess it only actually use the last source, the one that says "selected". Looking now at /etc/chrony.conf, I see pool 0.opensuse.pool.ntp.org iburst pool 1.opensuse.pool.ntp.org iburst pool 2.opensuse.pool.ntp.org iburst pool 3.opensuse.pool.ntp.org iburst ! pool pool.ntp.org iburst -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E.R. wrote:
On 04/09/2020 08.11, Per Jessen wrote:
Carlos E. R. wrote:
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
[snip]
What should I look at? The system is with default configurations, installed hours ago.
First question - is there a problem? I don't use chrony myself, but it looks like it selected two IPv4 sources, which sounds good. IIUC, the "source replaced with" message simply means that an unreachable server was swapped out for another one (not necessarily more reachable).
Well, I don't know if there is a problem. Hard to see if the clock is off or not. To me it looks like if first tries an IPv4 address, then one minute later it selects another, I guess because the first one doesn't work. After 3 minutes it selects another. This doesn't look to me like it is using 3 ipv4 sources in parallel, but maybe I'm reading wrong.
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc. Ah yes, google tells me: "chronyc tracking".
From the Fedora projects sysadmin guide :-)
-- Per Jessen, Zürich (20.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc.
Ah yes, google tells me: "chronyc tracking".
plus "chronyc sources". -- Per Jessen, Zürich (20.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 11.43, Per Jessen wrote:
Per Jessen wrote:
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc.
Ah yes, google tells me: "chronyc tracking".
plus "chronyc sources".
Rescate:~ # chronyc sources 210 Number of sources = 11 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* time.cloudflare.com 3 6 377 12 +78us[ +29us] +/- 22ms ^+ time.cloudflare.com 3 6 377 11 -428us[ -428us] +/- 22ms ^+ fw.dessoft.es 2 6 377 11 -1441us[-1441us] +/- 67ms ^+ ntp9.kashra-server.com 2 6 367 8 +990us[ +990us] +/- 33ms ^+ sarah.vandalsweb.com 2 6 377 9 -504us[ -504us] +/- 61ms ^? ntp.redimadrid.es 0 6 0 - +0ns[ +0ns] +/- 0ns ^? shackleton.red.uv.es 0 6 0 - +0ns[ +0ns] +/- 0ns ^? bjaaland.red.uv.es 0 6 0 - +0ns[ +0ns] +/- 0ns ^? time.cloudflare.com 0 6 0 - +0ns[ +0ns] +/- 0ns ^+ 213.251.52.234 2 6 377 9 -515us[ -515us] +/- 73ms ^- dns01.masbytes.es 3 6 377 13 +4885us[+4836us] +/- 145ms Rescate:~ # The config has: # Use public servers from the pool.ntp.org project. # Please consider joining the pool (http://www.pool.ntp.org/join.html). pool 0.opensuse.pool.ntp.org iburst pool 1.opensuse.pool.ntp.org iburst pool 2.opensuse.pool.ntp.org iburst pool 3.opensuse.pool.ntp.org iburst ! pool pool.ntp.org iburst It is not using the opensuse pool :-? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 04/09/2020 11.43, Per Jessen wrote:
Per Jessen wrote:
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc.
Ah yes, google tells me: "chronyc tracking".
plus "chronyc sources".
[snip]
It is not using the opensuse pool :-?
The pool addresses are not time servers themselves, it is just a DNS round-robin setup. -- Per Jessen, Zürich (20.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2020 12.01, Per Jessen wrote:
Carlos E. R. wrote:
On 04/09/2020 11.43, Per Jessen wrote:
Per Jessen wrote:
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc.
Ah yes, google tells me: "chronyc tracking".
plus "chronyc sources".
[snip]
It is not using the opensuse pool :-?
The pool addresses are not time servers themselves, it is just a DNS round-robin setup.
Ah! That is clear then. How does one join the openSUSE pool in particular? Just curious. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 04/09/2020 11.37, Per Jessen wrote:
Carlos E.R. wrote:
On 04/09/2020 08.11, Per Jessen wrote:
Carlos E. R. wrote:
Notice how chronyd is trying to use IPv6 addresses, when my home doesn't have IPv6. The network is autoconfigured with DHCP (network manager) from the ISP provided and configured router.
[snip]
What should I look at? The system is with default configurations, installed hours ago.
First question - is there a problem? I don't use chrony myself, but it looks like it selected two IPv4 sources, which sounds good. IIUC, the "source replaced with" message simply means that an unreachable server was swapped out for another one (not necessarily more reachable).
Well, I don't know if there is a problem. Hard to see if the clock is off or not. To me it looks like if first tries an IPv4 address, then one minute later it selects another, I guess because the first one doesn't work. After 3 minutes it selects another. This doesn't look to me like it is using 3 ipv4 sources in parallel, but maybe I'm reading wrong.
There must be a query tool for that - like ntpq - to show which sources, stratum, availability etc.
Ah yes, google tells me: "chronyc tracking".
From the Fedora projects sysadmin guide :-)
It is the first time I actually "use" chrony, and it is not my main goal on that machine - I got sidetracked because the entries are visible in the log ;-) Thanks for spotting that. Rescate:~ # chronyc tracking Reference ID : A29FC87B (time.cloudflare.com) Stratum : 4 Ref time (UTC) : Fri Sep 04 09:45:52 2020 : 0.000405651 seconds fast of NTP time Last offset : +0.000112012 seconds RMS offset : 0.000965670 seconds Frequency : 1.897 ppm fast Residual freq : +1.000 ppm Skew : 0.966 ppm Root delay : 0.041225310 seconds Root dispersion : 0.001239378 seconds Update interval : 62.7 seconds Leap status : Normal Rescate:~ # But this is after restart with IPv6 disabled. It is not synced to the opensuse pool. The important line to me would be "System time". Pretty good! I'm starting to like chronyd. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
Thanks for spotting that.
Rescate:~ # chronyc tracking Reference ID : A29FC87B (time.cloudflare.com) Stratum : 4 Ref time (UTC) : Fri Sep 04 09:45:52 2020 : 0.000405651 seconds fast of NTP time Last offset : +0.000112012 seconds RMS offset : 0.000965670 seconds Frequency : 1.897 ppm fast Residual freq : +1.000 ppm Skew : 0.966 ppm Root delay : 0.041225310 seconds Root dispersion : 0.001239378 seconds Update interval : 62.7 seconds Leap status : Normal Rescate:~ #
But this is after restart with IPv6 disabled. It is not synced to the opensuse pool.
It is actually, "time.cloudflare.com" is a member of 0.opensuse.pool.ntp.org. -- Per Jessen, Zürich (21.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, 2020-09-04 at 05:00 +0200, Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
This other output is most interesting. Machine is freshly booted (Leap 15.2). carlos@Rescate:~> grep -i IPv /etc/sysconfig/chronyd # Resolve hostnames with IPv4 CHRONY_IPV4="yes" # Resolve hostnames with IPv6 #CHRONY_IPV6="yes" CHRONY_IPV6="no" carlos@Rescate:~> As you see, IPv6 is disabled. Yet: 2020-09-12T23:19:45.040595+02:00 Rescate chronyd[1466]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-12T23:19:45.114522+02:00 Rescate chronyd[1466]: Frequency 4.098 +/- 6.041 ppm read from /var/lib/chrony/drift 2020-09-12T23:23:14.402392+02:00 Rescate chronyd[1466]: Selected source 185.132.136.116 2020-09-12T23:23:14.402766+02:00 Rescate chronyd[1466]: System clock wrong by -1.012141 seconds, adjustment started 2020-09-12T23:23:14.403028+02:00 Rescate chronyd[1466]: System clock was stepped by -1.012141 seconds 2020-09-12T23:24:19.609496+02:00 Rescate chronyd[1466]: Selected source 162.159.200.123 2020-09-12T23:53:18.298463+02:00 Rescate chronyd[1466]: Source 2606:4700:f1::123 replaced with 213.172.105.106 2020-09-13T00:07:26.856909+02:00 Rescate chronyd[1466]: Selected source 185.132.136.116 Yet, as you can see, it tried to use an IPv6 server. Look at the start line, it clearly says +IPv6, it is ignoring the configuration. -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) El 2020-09-04 a las 05:00 +0200, Carlos E. R. escribió:
13.09.2020 01:25, Carlos E. R. пишет:
On Friday, 2020-09-04 at 05:00 +0200, Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
This other output is most interesting. Machine is freshly booted (Leap 15.2).
carlos@Rescate:~> grep -i IPv /etc/sysconfig/chronyd # Resolve hostnames with IPv4 CHRONY_IPV4="yes" # Resolve hostnames with IPv6 #CHRONY_IPV6="yes" CHRONY_IPV6="no"
Those settings are leftover from sysvinit time and are not used at all today. This is the only real bug here.
carlos@Rescate:~>
As you see, IPv6 is disabled. Yet:
2020-09-12T23:19:45.040595+02:00 Rescate chronyd[1466]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) 2020-09-12T23:19:45.114522+02:00 Rescate chronyd[1466]: Frequency 4.098 +/- 6.041 ppm read from /var/lib/chrony/drift 2020-09-12T23:23:14.402392+02:00 Rescate chronyd[1466]: Selected source 185.132.136.116 2020-09-12T23:23:14.402766+02:00 Rescate chronyd[1466]: System clock wrong by -1.012141 seconds, adjustment started 2020-09-12T23:23:14.403028+02:00 Rescate chronyd[1466]: System clock was stepped by -1.012141 seconds 2020-09-12T23:24:19.609496+02:00 Rescate chronyd[1466]: Selected source 162.159.200.123 2020-09-12T23:53:18.298463+02:00 Rescate chronyd[1466]: Source 2606:4700:f1::123 replaced with 213.172.105.106 2020-09-13T00:07:26.856909+02:00 Rescate chronyd[1466]: Selected source 185.132.136.116
Yet, as you can see, it tried to use an IPv6 server. Look at the start line, it clearly says +IPv6, it is ignoring the configuration.
You seriously expected that changing /etc/sysconfig/chronyd would recompile chronyd binary with disabled IPv6 support? If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
On Friday, 2020-09-04 at 05:00 +0200, Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
This other output is most interesting. Machine is freshly booted (Leap 15.2).
carlos@Rescate:~> grep -i IPv /etc/sysconfig/chronyd # Resolve hostnames with IPv4 CHRONY_IPV4="yes" # Resolve hostnames with IPv6 #CHRONY_IPV6="yes" CHRONY_IPV6="no"
Those settings are leftover from sysvinit time and are not used at all today. This is the only real bug here.
It is a new computer freshly installed with 15.2...
Yet, as you can see, it tried to use an IPv6 server. Look at the start line, it clearly says +IPv6, it is ignoring the configuration.
You seriously expected that changing /etc/sysconfig/chronyd would recompile chronyd binary with disabled IPv6 support?
You seriously expect me to know that I have to recompile chrony for it to read the configuration file distributed with openSUSE?
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Ok, I'll try that. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
On Friday, 2020-09-04 at 05:00 +0200, Carlos E. R. wrote:
Hi,
Look at this output on a newly installed Leap 15.2 system:
This other output is most interesting. Machine is freshly booted (Leap 15.2).
carlos@Rescate:~> grep -i IPv /etc/sysconfig/chronyd # Resolve hostnames with IPv4 CHRONY_IPV4="yes" # Resolve hostnames with IPv6 #CHRONY_IPV6="yes" CHRONY_IPV6="no"
Those settings are leftover from sysvinit time and are not used at all today. This is the only real bug here.
It is a new computer freshly installed with 15.2...
I guess the maintainer forgot to remove those sysconfig entries. A bit misleading, I agree. -- Per Jessen, Zürich (21.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work. ThinkPadE15:~ # systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2020-09-13 11:53:16 CEST; 6s ago Docs: man:chronyd(8) man:chrony.conf(5) Process: 2858 ExecStartPost=/usr/lib/chrony/helper update-daemon (code=exited, status=0/SUCCESS) Process: 2850 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2852 (chronyd) Tasks: 1 CGroup: /system.slice/chronyd.service └─2852 /usr/sbin/chronyd -4 <=================== Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Starting NTP client/server... Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) It has +IPV6 in there. Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: Frequency 3.398 +/- 0.114 ppm read from /var/lib/chrony/drift Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Started NTP client/server. Sep 13 11:53:21 ThinkPadE15.Lenovo chronyd[2852]: Selected source 162.159.200.123 ThinkPadE15:~ # -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work.
How do you determine that?
CGroup: /system.slice/chronyd.service └─2852 /usr/sbin/chronyd -4 <===================
Looks good.
Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Starting NTP client/server... Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
It has +IPV6 in there.
That is a compile time option. -- Per Jessen, Zürich (21.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/09/2020 12.25, Per Jessen wrote:
Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work.
How do you determine that?
The option is ignored. I see "+IPV6" in the output.
CGroup: /system.slice/chronyd.service └─2852 /usr/sbin/chronyd -4 <===================
Looks good.
Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Starting NTP client/server... Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
It has +IPV6 in there.
That is a compile time option.
I understood Andrei as saying that if I want chronyd to use "IPv4 only" to write: OPTIONS=-4 in /etc/sysconfig/chronyd The man page says: -4 With this option hostnames will be resolved only to IPv4 addresses and only IPv4 sockets will be created. No mention of having to recompile the program. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/09/2020 12.25, Per Jessen wrote:
Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work.
How do you determine that?
The option is ignored. I see "+IPV6" in the output.
It is a compile time option, it cannot be changed by a runtime argument. It merely indicates that chronyd was built with _support_ for IPv6. As you have done, use '-4' to restrict chronyd to IPv4 - at runtime. -- Per Jessen, Zürich (22.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/09/2020 12.39, Per Jessen wrote:
Carlos E. R. wrote:
On 13/09/2020 12.25, Per Jessen wrote:
Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work.
How do you determine that?
The option is ignored. I see "+IPV6" in the output.
It is a compile time option, it cannot be changed by a runtime argument. It merely indicates that chronyd was built with _support_ for IPv6.
Ah. You say that the information line are the compiled options, not the active options. Confusing.
As you have done, use '-4' to restrict chronyd to IPv4 - at runtime.
Well, I will have to see. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-09-13 04:55:38 Carlos E. R. wrote:
On 13/09/2020 08.29, Andrei Borzenkov wrote:
13.09.2020 01:25, Carlos E. R. пишет:
If you want to force IPv4 only, use OPTIONS=-4 in /etc/sysconfig/chronyd or modify chronyd.service.
Doesn't seem to work.
ThinkPadE15:~ # systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2020-09-13 11:53:16 CEST; 6s ago Docs: man:chronyd(8) man:chrony.conf(5) Process: 2858 ExecStartPost=/usr/lib/chrony/helper update-daemon (code=exited, status=0/SUCCESS) Process: 2850 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2852 (chronyd) Tasks: 1 CGroup: /system.slice/chronyd.service └─2852 /usr/sbin/chronyd -4 <===================
Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Starting NTP client/server... Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
It has +IPV6 in there.
Sep 13 11:53:16 ThinkPadE15.Lenovo chronyd[2852]: Frequency 3.398 +/- 0.114 ppm read from /var/lib/chrony/drift Sep 13 11:53:16 ThinkPadE15.Lenovo systemd[1]: Started NTP client/server. Sep 13 11:53:21 ThinkPadE15.Lenovo chronyd[2852]: Selected source 162.159.200.123 ThinkPadE15:~ #
I noticed in several posts in this thread that, though the "version 3.2 starting" message lists +IPV6, it also says later, "Selected source 162.159.200.123..." which indicates that it is using IPV4. Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/09/2020 04.59, J Leslie Turriff wrote:
On 2020-09-13 04:55:38 Carlos E. R. wrote:
I noticed in several posts in this thread that, though the "version 3.2 starting" message lists +IPV6, it also says later, "Selected source 162.159.200.123..." which indicates that it is using IPV4.
It happens that the starting line lists the compiled in options or features, not those that are active at run time. This was confusing me. Also, the line CHRONY_IPV6="no" in /etc/sysconfig/chronyd doesn't work. It has to be: OPTIONS=-4 -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
J Leslie Turriff -
James Knott -
Per Jessen