Make systemd-timesyncd not listen to IPv6
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
On one of my servers (Debian 9) I disabled IPv6. Now I receive the following error in the system's syslog:
systemd-timesyncd[645]: Failed to setup connection socket:
Address family not supported by protocol
How can I disable IPv6 for systemd-timesyncd?
debian systemd
asked Sep 5 at 15:37
chevallier
8591116
add a comment |Â
up vote
0
down vote
favorite
On one of my servers (Debian 9) I disabled IPv6. Now I receive the following error in the system's syslog:
systemd-timesyncd[645]: Failed to setup connection socket:
Address family not supported by protocol
How can I disable IPv6 for systemd-timesyncd?
debian systemd
asked Sep 5 at 15:37
chevallier
8591116
1
Have you specified your time server by IP address or by name? If by name, rungetent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.
– telcoM
Sep 5 at 17:23
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
On one of my servers (Debian 9) I disabled IPv6. Now I receive the following error in the system's syslog:
systemd-timesyncd[645]: Failed to setup connection socket:
Address family not supported by protocol
How can I disable IPv6 for systemd-timesyncd?
debian systemd
asked Sep 5 at 15:37
chevallier
8591116
On one of my servers (Debian 9) I disabled IPv6. Now I receive the following error in the system's syslog:
systemd-timesyncd[645]: Failed to setup connection socket:
Address family not supported by protocol
How can I disable IPv6 for systemd-timesyncd?
debian systemd
debian systemd
asked Sep 5 at 15:37
chevallier
8591116
asked Sep 5 at 15:37
chevallier
8591116
asked Sep 5 at 15:37
chevallier
8591116
asked Sep 5 at 15:37
chevallier
8591116
asked Sep 5 at 15:37
chevallier
8591116
8591116
1
Have you specified your time server by IP address or by name? If by name, rungetent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.
– telcoM
Sep 5 at 17:23
add a comment |Â
1
Have you specified your time server by IP address or by name? If by name, rungetent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.
– telcoM
Sep 5 at 17:23
1
1
Have you specified your time server by IP address or by name? If by name, run
getent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.– telcoM
Sep 5 at 17:23
Have you specified your time server by IP address or by name? If by name, run
getent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.– telcoM
Sep 5 at 17:23
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
It seems to be a known systemd bug in Arch. Did not find any reference for Debian itself, but is possible there is a similar bug. From the arch wiki relevant post
systemd-timesyncd will contact servers in turn until one is found that
responds. Arch uses the zones in the order of 0, 1, 2, 3. However, all
pool.ntp.org zones only have IPv6 and IPv4 enabled on the 2 subdomain.
All others are IPv4 only. Therefore, 2 should be placed first in order
to properly provide support for IPv6/IPv4 hosts.
It is also possible DHCP is giving you a wrong NTP server.
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses.
During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd
will contact all configured system or per-interface servers in turn
until one is found that responds. This setting defaults to an empty
list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be
used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this
setting, as do any servers set via NTP= above. This setting is hence
only used if no other NTP server information is known. If this option
is not given, a compiled-in list of NTP servers is used instead.
Possible workaround: disabling systemd-timesyncd and installing chrony
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It seems to be a known systemd bug in Arch. Did not find any reference for Debian itself, but is possible there is a similar bug. From the arch wiki relevant post
systemd-timesyncd will contact servers in turn until one is found that
responds. Arch uses the zones in the order of 0, 1, 2, 3. However, all
pool.ntp.org zones only have IPv6 and IPv4 enabled on the 2 subdomain.
All others are IPv4 only. Therefore, 2 should be placed first in order
to properly provide support for IPv6/IPv4 hosts.
It is also possible DHCP is giving you a wrong NTP server.
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses.
During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd
will contact all configured system or per-interface servers in turn
until one is found that responds. This setting defaults to an empty
list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be
used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this
setting, as do any servers set via NTP= above. This setting is hence
only used if no other NTP server information is known. If this option
is not given, a compiled-in list of NTP servers is used instead.
Possible workaround: disabling systemd-timesyncd and installing chrony
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
add a comment |Â
up vote
0
down vote
It seems to be a known systemd bug in Arch. Did not find any reference for Debian itself, but is possible there is a similar bug. From the arch wiki relevant post
systemd-timesyncd will contact servers in turn until one is found that
responds. Arch uses the zones in the order of 0, 1, 2, 3. However, all
pool.ntp.org zones only have IPv6 and IPv4 enabled on the 2 subdomain.
All others are IPv4 only. Therefore, 2 should be placed first in order
to properly provide support for IPv6/IPv4 hosts.
It is also possible DHCP is giving you a wrong NTP server.
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses.
During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd
will contact all configured system or per-interface servers in turn
until one is found that responds. This setting defaults to an empty
list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be
used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this
setting, as do any servers set via NTP= above. This setting is hence
only used if no other NTP server information is known. If this option
is not given, a compiled-in list of NTP servers is used instead.
Possible workaround: disabling systemd-timesyncd and installing chrony
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It seems to be a known systemd bug in Arch. Did not find any reference for Debian itself, but is possible there is a similar bug. From the arch wiki relevant post
systemd-timesyncd will contact servers in turn until one is found that
responds. Arch uses the zones in the order of 0, 1, 2, 3. However, all
pool.ntp.org zones only have IPv6 and IPv4 enabled on the 2 subdomain.
All others are IPv4 only. Therefore, 2 should be placed first in order
to properly provide support for IPv6/IPv4 hosts.
It is also possible DHCP is giving you a wrong NTP server.
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses.
During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd
will contact all configured system or per-interface servers in turn
until one is found that responds. This setting defaults to an empty
list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be
used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this
setting, as do any servers set via NTP= above. This setting is hence
only used if no other NTP server information is known. If this option
is not given, a compiled-in list of NTP servers is used instead.
Possible workaround: disabling systemd-timesyncd and installing chrony
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
It seems to be a known systemd bug in Arch. Did not find any reference for Debian itself, but is possible there is a similar bug. From the arch wiki relevant post
systemd-timesyncd will contact servers in turn until one is found that
responds. Arch uses the zones in the order of 0, 1, 2, 3. However, all
pool.ntp.org zones only have IPv6 and IPv4 enabled on the 2 subdomain.
All others are IPv4 only. Therefore, 2 should be placed first in order
to properly provide support for IPv6/IPv4 hosts.
It is also possible DHCP is giving you a wrong NTP server.
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses.
During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd
will contact all configured system or per-interface servers in turn
until one is found that responds. This setting defaults to an empty
list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be
used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this
setting, as do any servers set via NTP= above. This setting is hence
only used if no other NTP server information is known. If this option
is not given, a compiled-in list of NTP servers is used instead.
Possible workaround: disabling systemd-timesyncd and installing chrony
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
edited Sep 5 at 18:36
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
answered Sep 5 at 18:21
Rui F Ribeiro
36.8k1273117
36.8k1273117
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
add a comment |Â
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
Someone more familiar with systemd than myself might also suggest a systemd-timesyncd friendly workaround.
– Rui F Ribeiro
Sep 5 at 18:24
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f467053%2fmake-systemd-timesyncd-not-listen-to-ipv6%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Have you specified your time server by IP address or by name? If by name, run
getent hosts <name-of-NTP-server>. If you get an IPv6 address back, your DNS resolver library is still preferring IPv6 over IPv4 and you'll need to fix that.– telcoM
Sep 5 at 17:23