I was also noticing needing to muck with the network interfaces and
services during the beta. I find it interesting the need to disable
NetworkManager and enable the legacy network service. I found no
reference to this in the documentation for 3.3 and people seem to be
installing it without issue. Maybe these people are just disabling it
and not saying anything?
-
Thomas
On 09/04/2013 09:42 PM, Markus Stockhausen wrote:
Hello,
just in case someone else got this problem. For me it seems to be a naming
convention problem. ifcfg file names did not match the shown interfaces.
Steps to fix it included:
- rename ifcfg-enp1s0, ... scripts to real interface names ifcfg-p49p1, ...
- remove parameter NAME from these scripts
- Switch to network service
systemctl disable NetworkManager
systemctl stop NetworkManager.service
service network start
chkconfig network on
Markus