My Tumbleweed system does not get a public IPv6 address. The reason is
unknown, but it must be a configuration problem, because all other dual
boot OS, TW in rescue mode and even the KVM VMs get an IPv6 address on
the same hardware. The router is OpenWrt based and seems to work fine. I
already tried to copy the network configuration from the rescue system.
I use a Wicked based network configuration, set up with YaST.
For privacy reasons I replaced some numbers with "xx".
# wicked ifstatus br0
br0 up
link: #16, state up, mtu 1454
type: bridge, hwaddr xx:xx:xx:xx:xx:xx
config: compat:suse:/etc/sysconfig/network/ifcfg-br0
leases: ipv4 dhcp granted
leases: ipv6 dhcp requesting
addr: ipv4 192.168.xxx.xxx/24 [dhcp]
route: ipv4 default via 192.168.xxx.xxx proto dhcp
# cat /etc/sysconfig/network/ifcfg-br0
BOOTPROTO='dhcp'
STARTMODE='auto'
ZONE='home'
BRIDGE='yes'
BRIDGE_PORTS='eno1'
BRIDGE_STP='on'
BRIDGE_FORWARDDELAY='2'
# ip -6 addr show br0
16: br0:
On 31. 05. 21, 12:34, Bjoern Voigt wrote:
My Tumbleweed system does not get a public IPv6 address. The reason is unknown, but it must be a configuration problem, because all other dual boot OS, TW in rescue mode and even the KVM VMs get an IPv6 address on the same hardware. The router is OpenWrt based and seems to work fine. I already tried to copy the network configuration from the rescue system. I use a Wicked based network configuration, set up with YaST.
Are you sure the other systems use ipv6+dhcp? What does output of ip -6 addr on the other systems look like?
# sysctl net.ipv6.conf.all.disable_ipv6 net.ipv6.conf.all.disable_ipv6 = 0 # sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1
What about net.ipv6.conf.all.autoconf and net.ipv6.conf.all.accept_ra here and on other systems? regards, -- js suse labs
Jiri Slaby wrote:
On 31. 05. 21, 12:34, Bjoern Voigt wrote:
My Tumbleweed system does not get a public IPv6 address. The reason is unknown, but it must be a configuration problem, because all other dual boot OS, TW in rescue mode and even the KVM VMs get an IPv6 address on the same hardware. The router is OpenWrt based and seems to work fine. I already tried to copy the network configuration from the rescue system. I use a Wicked based network configuration, set up with YaST.
Are you sure the other systems use ipv6+dhcp? What does output of ip -6 addr on the other systems look like? My Linux Minut 19 KVM VM uses Network Manager with the following DHCPv6 configuration:
/sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf
/run/dhclient-ens3.pid -lf
/var/lib/NetworkManager/dhclient-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-ens3.lease
-cf /var/lib/NetworkManager/dhclient-ens3.conf ens3
/var/lib/NetworkManager/dhclient-ens3.conf:
# Created by NetworkManager
send fqdn.fqdn "mybox-mint"; # added by NetworkManager
send fqdn.server-update on;
also request dhcp6.name-servers;
also request dhcp6.domain-search;
also request dhcp6.client-id;
# ip -6 addr
1: lo:
# sysctl net.ipv6.conf.all.disable_ipv6 net.ipv6.conf.all.disable_ipv6 = 0 # sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1
What about net.ipv6.conf.all.autoconf and net.ipv6.conf.all.accept_ra here and on other systems? net.ipv6.conf.all.autoconf = 1 net.ipv6.conf.all.forwarding = 1
I found here https://bugzilla.opensuse.org/show_bug.cgi?id=1166358 two tips which together solve the problem: sysctl -w net.ipv6.conf.all.accept_ra=2 sysctl -w net.ipv6.conf.br0.forwarding=0 Unfortunately the bug report is closed with RESOLVED INVALID. I do not agree that the report has been closed. There bug report contains only temporary solutions (with sysctl or echo). Also YaST oder Wicked could be patched, so that they can detect an inconsistent configuration (DHCPv6 is activated, but net.ipv6.conf is wrong) and report this to the user (YaST) or log this (Wicked). Jiri, do you agree and could you reopen the bug report? Greetings, Björn* *
On 01. 06. 21, 11:48, Bjoern Voigt wrote:
I found here https://bugzilla.opensuse.org/show_bug.cgi?id=1166358 two tips which together solve the problem:
sysctl -w net.ipv6.conf.all.accept_ra=2 sysctl -w net.ipv6.conf.br0.forwarding=0
Unfortunately the bug report is closed with RESOLVED INVALID. I do not agree that the report has been closed.
There bug report contains only temporary solutions (with sysctl or echo). Also YaST oder Wicked could be patched, so that they can detect an inconsistent configuration (DHCPv6 is activated, but net.ipv6.conf is wrong) and report this to the user (YaST) or log this (Wicked).
Jiri, do you agree and could you reopen the bug report?
I suggest you to "Clone This Bug", instead. regards, -- js suse labs
participants (2)
-
Bjoern Voigt
-
Jiri Slaby