View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007483 | CentOS-7 | NetworkManager | public | 2014-08-09 07:37 | 2014-08-09 13:29 |
Reporter | ip6li | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 7.0-1406 | ||||
Summary | 0007483: ifup script does not work with dummy interface | ||||
Description | ifcfg-dummy0 copied from CentOS 6.5 system which is working in production, ifup dummy0 should bring up dummy0 interface, but it does not. | ||||
Steps To Reproduce | ifcfg-dummy0: DEVICE=dummy0 BOOTPROTO=none IPV6INIT=no NAME="dummy0" ONBOOT=yes TYPE=Ethernet USERCTL=no BRIDGE=br192_168_116 ifcfg-br192_168_116 DEVICE=br192_168_116 BOOTPROTO=none DEFROUTE="yes" IPADDR=192.168.116.1 NAME="System 192_168_116" ONBOOT=yes PREFIX=24 TYPE=Bridge USERCTL=no IPV6INIT=no [root@centos7 network-scripts]# LANG=C ifup dummy0 Error: no device found for connection 'dummy0'. Expected behaviour: Like CentOS 6.5 interface dummy0 should appear and come up. # cat /etc/modprobe.d/dummy.conf alias dummy0 dummy options dummy numdummies=3 [root@centos7 network-scripts]# lsmod |grep dummy [root@centos7 network-scripts]# ip link set dummy0 up [root@centos7 network-scripts]# lsmod |grep dummy dummy 12960 0 [root@centos7 network-scripts]# ifconfig dummy0 dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500 inet6 fe80::44dd:58ff:fea9:4fd2 prefixlen 64 scopeid 0x20<link> ether 46:dd:58:a9:4f:d2 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3 bytes 210 (210.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Module config is ok, exactly 3 dummy interfaces are available as configured in dummy.conf | ||||
Tags | No tags attached. | ||||
abrt_hash | |||||
URL | |||||
NM_CONTROLLED="no" seems to solve that. Is that behavior is intended? |
|
Manually using the scripts belonging to the network service ( i.e. those from /etc/sysconfig/network-scripts) while NetworkManager is in use is not really supported . One can say that the 2 systems "fight" for the same resources and to put it in polite words, the result is not always the intended one. I suggest that you try to use the nmcli interface. |
|