Bug 1310002 - s390x device has ipv6 setup even if profile has ipv6.ignore
Summary: s390x device has ipv6 setup even if profile has ipv6.ignore
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 08:25 UTC by Vladimir Benes
Modified: 2016-11-25 13:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-25 13:48:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vladimir Benes 2016-02-19 08:25:24 UTC
Description of problem:
I have a clean install profile (generated by dracut) that has no ipv6 section. 
[root@ibm-z10-29 ~]# cat /etc/sysconfig/network-scripts/ifcfg-enccw0.0.8000 
# Generated by dracut initrd
NAME="enccw0.0.8000"
SUBCHANNELS="0.0.8000,0.0.8001,0.0.8002"
NETTYPE="qeth"
OPTIONS="layer2=1 portname=z10-29 portno=0"
DEVICE="enccw0.0.8000"
ONBOOT=yes
NETBOOT=yes
UUID="f4d76d82-cfbe-4290-a04a-9a6caf111308"
BOOTPROTO=none
IPADDR="10.16.66.220"
PREFIX="21"
GATEWAY="10.16.71.254"
TYPE=Ethernet
DNS1="10.11.5.19"

but I have ipv6 correctly set
2: enccw0.0.8000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 02:de:ad:be:ef:1d brd ff:ff:ff:ff:ff:ff
    inet 10.16.66.220/21 brd 10.16.71.255 scope global enccw0.0.8000
       valid_lft forever preferred_lft forever
    inet6 2620:52:0:1040:de:adff:febe:ef1d/64 scope global mngtmpaddr dynamic 
       valid_lft 2591957sec preferred_lft 604757sec
    inet6 fe80::de:adff:febe:ef1d/64 scope link 
       valid_lft forever preferred_lft forever

NM up and running:
[root@ibm-z10-29 ~]# systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2016-02-19 02:59:06 EST; 16min ago
 Main PID: 13600 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─13600 /usr/sbin/NetworkManager --no-daemon

 
shouldn't be ipv6 disabled?

this is because this is set, right?
[root@ibm-z10-29 ~]# sysctl -a |grep ipv6|grep encc
net.ipv6.conf.enccw0/0/8000.accept_dad = 1
net.ipv6.conf.enccw0/0/8000.accept_ra = 1
net.ipv6.conf.enccw0/0/8000.accept_ra_defrtr = 1
net.ipv6.conf.enccw0/0/8000.accept_ra_pinfo = 1
net.ipv6.conf.enccw0/0/8000.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.enccw0/0/8000.accept_ra_rtr_pref = 1

Is this a bug or not? I suppose these values are set differently on x86_64.
[root@wlan-r2s22 ~]# sysctl -a |grep eth0|grep ipv6
net.ipv6.conf.eth0.accept_dad = 1
net.ipv6.conf.eth0.accept_ra = 1
net.ipv6.conf.eth0.accept_ra_defrtr = 0
net.ipv6.conf.eth0.accept_ra_pinfo = 0
net.ipv6.conf.eth0.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.eth0.accept_ra_rtr_pref = 0

no matter if method is ignore or auto. But this makes a difference as when ra is enabled s390x obtains ipv6 addresses but x86_64 not. Shouldn't this be consistent?


Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-27.el7.x86_64

Comment 3 Thomas Haller 2016-02-19 12:02:40 UTC
There is currently no ipv6.method=disabled.

There is "ignore", but ignore means just, don't touch, leave it to the kernel. As such, I think this is expected behavior.

NM just didn't reset the ipv6 sysctl values from whatever was set before NetworkManager starts.


Note You need to log in before you can comment on or make changes to this bug.