http://bugzilla.opensuse.org/show_bug.cgi?id=931595
Bug ID: 931595
Summary: YaST2 module network does not configure using wicked a
working IPv6 network
Classification: openSUSE
Product: openSUSE Factory
Version: 201505*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers@suse.de
Reporter: freek@opensuse.org
QA Contact: jsrain@suse.com
Found By: ---
Blocker: ---
I used the YaST GUI in KDE on Tumbleweed 20150516 to configure the Ethernet
interface having two IPv4 addresses and two IPv6 addresses. Using
NetworkManager with the same configuration works OK. Also DNS and routing are
configured the same as with NetworkManager. The first time I enabled this
configuration I noticed that "ip -6 r" did not show a default route. A ping6
could not reach a IPv6 host. After that I went back to the NetworkManager
setup. Now I changed it back to wicked and I see the following:
eiktum:~ # ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether e0:cb:4e:cd:d7:b6 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.6/24 brd 192.168.178.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet 192.168.178.7/24 brd 192.168.178.255 scope global secondary enp1s0
valid_lft forever preferred_lft forever
inet6 2001:980:xxxx::1:37/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:980:xxxx::1:36/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:980:xxxx:1::1:37/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:980:xxxx:1::1:36/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::e2cb:4eff:fecd:d7b6/64 scope link
valid_lft forever preferred_lft forever
eiktum:~ # ip -4 r
default via 192.168.178.1 dev enp1s0
default via 192.168.178.1 dev enp1s0 proto static metric 100
192.168.178.0/24 dev enp1s0 proto kernel scope link src 192.168.178.6
192.168.178.0/24 dev enp1s0 proto kernel scope link src 192.168.178.6
metric 100
eiktum:~ # ip -6 r
2001:980:xxxx::/64 dev enp1s0 proto kernel metric 256
2001:980:xxxx:1::/64 dev enp1s0 proto kernel metric 256
fd00::9ec7:a6ff:fe0a:1f48 dev enp1s0 proto static metric 100
fe80::/64 dev enp1s0 proto kernel metric 256
default via fd00::9ec7:a6ff:fe0a:1f48 dev enp1s0 proto static metric 100
eiktum:~ # more /etc/sysconfig/network/ifcfg-enp1s0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.178.6/24'
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
IPADDR_0='2001:980:xxxx::1:36/64'
LABEL_0='eiktumb6'
IPADDR_1='192.168.178.7/24'
LABEL_1='eiktuml'
IPADDR_2='2001:980:xxxx::1:37/64'
LABEL_2='eiktuml6'
eiktum:~ # more /etc/sysconfig/network/ifroute-enp1s0
default 192.168.178.1 - enp1s0
default fd00::9ec7:fe0a:1f48 - enp1s0
eiktum:~ # grep NETCONFIG_DNS_STATIC_SERVERS /etc/sysconfig/network/config
NETCONFIG_DNS_STATIC_SERVERS="192.168.178.1 fd00::9ec7:fe0a:1f48"
eiktum:~ #
It looks like the problem is not so much YaST, but wicked, because these
configuration files look OK.
--
You are receiving this mail because:
You are on the CC list for the bug.