View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007272||CentOS-7||gnome-desktop3||public||2014-06-28 15:57||2014-07-02 19:35|
|Platform||Windows||OS||8.1 Professional||OS Version||8.1|
|Summary||0007272: CentOS 7 Gnome network profiles automatically created|
|Description||I use CentOS 7 (build of 26-06-2014) in Microsoft Hyper-V on Microsoft Windows 8.1 Professional for testing purpose. The live CD images installs fine, during installation network setting manually defined are working. After installation the Gnome network preference manager is ignoring static IP4 profile and is creating a new automatic IP6 network profile (Auto Ethernet) if I turn the network off and on. Disabling IP4 and IP6 in automatic created profile isn't working, because after off/on Gnome is creating a new identically profile and set it to active. The static created IP4 network profile (no DHCP server) is inactive.|
I can't set the static profile active nor delete all created automatic network profiles. So in the end of the day I have no active network.
|Steps To Reproduce||Start gnome network manager configure a profile.|
|Additional Information||Gnome is showing that the network is set to on, but in the top network icon it shows off.|
|Tags||No tags attached.|
|Changing the auto generated network profile to static IP settings isn't working either. After off/on there is a new auto generated network profile.|
This is a somewhat known issue, though the exact causes are unclear.
I've seen a few things listed as workarounds.
Please try the following:
1. yum install NetworkManager-config-server # This *should* do the trick for you, though you'll likely have to reset the interfaces again.
2. If the above doesn't work, please try adding 'no-auto-default=*' (without quotes) to /etc/NetworkManager/NetworkManager.conf
This tells NM to ignore everything it's not explicitly told to manage.
|OK, option 2 did the trick. It seems, if an IPv6 device is in the network Gnome is using this regardless of the network settings. In my case there is a router which is offering IPv6-DHCP service even if this service is turned off (Speedport v724 Typ C). So, the DHCP client is never getting an IP address.|