Hide Forgot
Description of problem: If network card is set to not be maaged by Network Manager, the system ignores ONBOOT flag How reproducible: start system-config-network, edit network card check on boot and uncheck managed by Network maager Actual results: No network activated on boot Expected results: Network should be up Additional info: This functionality is needed because Network maager stops Lan and mobile Broadband working together
If you want the NIC to be activated on boot even when it's marked as NM_CONTROLLED=no, then you need to have network service enabled. If it's not enabled (check 'systemctl status network.service') you can do that with 'systemctl enable network.service'
Network service is enabled
How does the /etc/sysconfig/network-scripts/ifcfg-<iface> look like then ?
cat /etc/sysconfig/network-scripts/ifcfg-p18p1 GATEWAY=192.168.0.1 DEVICE=p18p1 BOOTPROTO=none NETMASK=255.255.255.0 TYPE=Ethernet HWADDR=00:01:6c:0d:a1:93 IPADDR=192.168.0.2 NM_CONTROLLED=no IPV6INIT=no PREFIX=24 ONBOOT=yes USERCTL=yes
What is the status of the network service?
always running
This is from syslog Dec 22 08:10:14 redtux NetworkManager[904]: ifcfg-rh: read connection 'System p18p1' Dec 22 08:10:14 redtux NetworkManager[904]: NetworkManager[904]: ifcfg-rh: read connection 'System p18p1' Dec 22 08:10:14 redtux NetworkManager[904]: ifcfg-rh: Ignoring connection 'System p18p1' and its device due to NM_CONTROLLED/BRIDGE/VLAN. Dec 22 08:10:14 redtux NetworkManager[904]: NetworkManager[904]: ifcfg-rh: Ignoring connection 'System p18p1' and its device due to NM_CONTROLLED/BRIDGE/VLAN.
What is the output of 'systemctl status network.service'?
I believe I am seeing this exact problem on F17, but only on machines that were installed from scratch. Machines upgraded from F15 or F16 are not showing this problem. Like the posts above, my cards are labelled "ONBOOT=yes" and "NM_CONTROLELD=no", network service is enabled and running, but the cards are not brought up during boot - only when I manually start the network service again from the command line.
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.