While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed. This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST. I thought that disabled IPv6 entirely? Not so?
On 21.01.2024 21:58, joe a wrote:
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
When you ask questions, it helps to describe what settings you are talking about more precisely than "network config in YaST". If you mean "Enable IPv6" check button in "Global Options" tab - this setting disables IPv6 addresses on interfaces. It does not prevent applications from creating IPv6 sockets.
On 1/21/2024 14:17:11, Andrei Borzenkov wrote:
On 21.01.2024 21:58, joe a wrote:
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
When you ask questions, it helps to describe what settings you are talking about more precisely than "network config in YaST".
If you mean "Enable IPv6" check button in "Global Options" tab - this setting disables IPv6 addresses on interfaces. It does not prevent applications from creating IPv6 sockets.
Point taken. Yes, I meant that check box. One presumes the applications will have some means of specifying protocols to use and this will vary with each? Surely there is a way to disable it at the "system level"? I'll put that on my search list.
On 21.01.2024 22:52, joe a wrote:
On 1/21/2024 14:17:11, Andrei Borzenkov wrote:
On 21.01.2024 21:58, joe a wrote:
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
When you ask questions, it helps to describe what settings you are talking about more precisely than "network config in YaST".
If you mean "Enable IPv6" check button in "Global Options" tab - this setting disables IPv6 addresses on interfaces. It does not prevent applications from creating IPv6 sockets.
Point taken.
Yes, I meant that check box.
One presumes the applications will have some means of specifying protocols to use and this will vary with each?
Surely there is a way to disable it at the "system level"? I'll put that on my search list.
What is "it"? If you do not want to even have IPv6 protocol available, use ipv6 module disable=1 option.
On 1/21/2024 23:00:55, Andrei Borzenkov wrote:
On 21.01.2024 22:52, joe a wrote:
On 1/21/2024 14:17:11, Andrei Borzenkov wrote:
On 21.01.2024 21:58, joe a wrote:
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
When you ask questions, it helps to describe what settings you are talking about more precisely than "network config in YaST".
If you mean "Enable IPv6" check button in "Global Options" tab - this setting disables IPv6 addresses on interfaces. It does not prevent applications from creating IPv6 sockets.
Point taken.
Yes, I meant that check box.
One presumes the applications will have some means of specifying protocols to use and this will vary with each?
Surely there is a way to disable it at the "system level"? I'll put that on my search list.
What is "it"? If you do not want to even have IPv6 protocol available, use ipv6 module disable=1 option.
Depends on situation. Preferable perhaps to disable as desired rather than not have it available at all "system wide".
joe a composed on 2024-01-21 13:58 (UTC-0500):
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
I use only systemd-network, so can't configure using YaST. Here's evidence of disabling here: # dmesg | grep -i ipv6 [ 0.000000] Command line: <...> ipv6.disable=1 <...> [ 0.018438] Kernel command line: <...> ipv6.disable=1 <...> [ 0.885953] IPv6: Loaded, but administratively disabled, reboot required to enable [ 5.020243] systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. [ 5.020249] systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. # grep -Rnwi /etc -e 'ipv6' | grep -i able /etc/slp.conf:291:# that IPv4 is enabled, and IPv6 is disabled. Uncomment one or other of the /etc/sysctl.conf-ipv6-disable:21:net.ipv6.conf.all.disable_ipv6 = 1 /etc/sysctl.d/local.conf:2:net.ipv6.conf.all.disable_ipv6 = 1 /etc/sysconfig/network/dhcp:151:# IPv6 router RA and DHCLIENT6_MODE variable): /etc/sysconfig/network/config:27:# happen "post-mortem" and maybe even cause to disable ipv6 at all. /etc/sysconfig/windowmanager:44:# To disable IPv6 support within KDE. It might solve large timeouts due to # Lots of configuration stuff addressing ipv6 in Leap: # grep -Rnwi /etc -e 'ipv6' | wc -l 151 # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 1/21/2024 14:38:59, Felix Miata wrote:
joe a composed on 2024-01-21 13:58 (UTC-0500):
While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed.
This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST.
I thought that disabled IPv6 entirely? Not so?
I use only systemd-network, so can't configure using YaST. Here's evidence of disabling here:
# dmesg | grep -i ipv6 [ 0.000000] Command line: <...> ipv6.disable=1 <...> [ 0.018438] Kernel command line: <...> ipv6.disable=1 <...> [ 0.885953] IPv6: Loaded, but administratively disabled, reboot required to enable [ 5.020243] systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. [ 5.020249] systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. # grep -Rnwi /etc -e 'ipv6' | grep -i able /etc/slp.conf:291:# that IPv4 is enabled, and IPv6 is disabled. Uncomment one or other of the /etc/sysctl.conf-ipv6-disable:21:net.ipv6.conf.all.disable_ipv6 = 1 /etc/sysctl.d/local.conf:2:net.ipv6.conf.all.disable_ipv6 = 1 /etc/sysconfig/network/dhcp:151:# IPv6 router RA and DHCLIENT6_MODE variable): /etc/sysconfig/network/config:27:# happen "post-mortem" and maybe even cause to disable ipv6 at all. /etc/sysconfig/windowmanager:44:# To disable IPv6 support within KDE. It might solve large timeouts due to # Lots of configuration stuff addressing ipv6 in Leap: # grep -Rnwi /etc -e 'ipv6' | wc -l 151 #
I'll poke about.
There is a line "GRUB_CMDLINE_LINUX_DEFAULT" ... in your /etc/default/grub which you may add „ipv6.disable=1“ to. You may achieve this by Yast, too (add it to bootloader-> kernel options ). Another option is you add net.ipv6.conf.all.disable_ipv6 = 1 and net.ipv6.conf.default.disable_ipv6 = 1 to your /etc/sysctl . Preferred method is you use the command sysctl -w followed by the net.ipv.... and after that sysctl -p to apply the updates to services, ... -------- Ursprüngliche Nachricht -------- Van: joe a <joea-lists@j4computers.com> Aan: users@lists.opensuse.org Onderwerp: Disable IPv6? Datum: 21.01.2024 19:58:19 While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed. This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST. I thought that disabled IPv6 entirely? Not so?
Good to know, another lesson learnt. So in this case there is no second option, at least not this one. Thanks! -------- Ursprüngliche Nachricht -------- Van: Andrei Borzenkov <arvidjaar@gmail.com> Aan: users@lists.opensuse.org Onderwerp: Re: Disable IPv6? Datum: 22.01.2024 11:30:49 On Mon, Jan 22, 2024 at 1:02 PM GMX via openSUSE Users <users@lists.opensuse.org> wrote:
Another option is you add net.ipv6.conf.all.disable_ipv6 = 1 and net.ipv6.conf.default.disable_ipv6 = 1 to your /etc/sysctl .
Which is exactly what the YaST does.
On 1/22/2024 05:01:23, GMX via openSUSE Users wrote:
There is a line "GRUB_CMDLINE_LINUX_DEFAULT" ... in your /etc/default/grub which you may add „ipv6.disable=1“ to. You may achieve this by Yast, too (add it to bootloader-> kernel options ). Another option is you add net.ipv6.conf.all.disable_ipv6 = 1 and net.ipv6.conf.default.disable_ipv6 = 1 to your /etc/sysctl . Preferred method is you use the command sysctl -w followed by the net.ipv.... and after that sysctl -p to apply the updates to services, ... -------- Ursprüngliche Nachricht --------
In YAST I see under "Boot Loader Settings", with the choices "Boot Code Options, Kernel Parameters, Bootloader Options". I presume "Kernel Parameters, Optional Kernel Command Line Parameter", is where to insert "ipv6.disable=1"?
So it is. -------- Ursprüngliche Nachricht -------- Van: joe a <joea-lists@j4computers.com> Aan: users@lists.opensuse.org Onderwerp: Re: Disable IPv6? Datum: 22.01.2024 15:11:10 On 1/22/2024 05:01:23, GMX via openSUSE Users wrote:
There is a line "GRUB_CMDLINE_LINUX_DEFAULT" ... in your /etc/default/grub which you may add „ipv6.disable=1“ to. You may achieve this by Yast, too (add it to bootloader-> kernel options ). Another option is you add net.ipv6.conf.all.disable_ipv6 = 1 and net.ipv6.conf.default.disable_ipv6 = 1 to your /etc/sysctl . Preferred method is you use the command sysctl -w followed by the net.ipv.... and after that sysctl -p to apply the updates to services, ... -------- Ursprüngliche Nachricht --------
In YAST I see under "Boot Loader Settings", with the choices "Boot Code Options, Kernel Parameters, Bootloader Options". I presume "Kernel Parameters, Optional Kernel Command Line Parameter", is where to insert "ipv6.disable=1"?
participants (4)
-
Andrei Borzenkov -
Felix Miata -
GMX -
joe a