Description of problem: I installed fresh F10 system with static network configuration (I used F9 netinst ISO for installation start and selected NFS method and used F10 tree). Installation was successfull but after reboot machine was unreachable. Version-Release number of selected component (if applicable): anaconda-11.4.1.44-1.x86_64 How reproducible: always Steps to Reproduce: 1. Install F10 machine with static network configuration 2. reboot it after install 3. try ping it Actual results: machine unreachable Expected results: networking works fine Additional info: Problem is due NetworkManager - AFAIK it doesn't support static networking. There should be "NM_CONTROLLED=no" option in network device configuration file and "network" service enabled.
(In reply to comment #0) > Description of problem: > I installed fresh F10 system with static network configuration (I used F9 > netinst ISO for installation start and selected NFS method and used F10 tree). > Installation was successfull but after reboot machine was unreachable. > > Version-Release number of selected component (if applicable): > anaconda-11.4.1.44-1.x86_64 > > How reproducible: > always > > Steps to Reproduce: > 1. Install F10 machine with static network configuration > 2. reboot it after install > 3. try ping it > > Actual results: > machine unreachable > > Expected results: > networking works fine I just did an NFS install with a static network configuration. The install completely successfully and the static network configuration parameters were present on the system when it rebooted. > Additional info: > Problem is due NetworkManager - AFAIK it doesn't support static networking. > There should be "NM_CONTROLLED=no" option in network device configuration file > and "network" service enabled. NetworkManager is what we are enabling in anaconda from now on. The installer will not offer the ability to select the 'network' service over NetworkManager. The NetworkManager service can handle static and dynamic interface configurations, even a mix of the two. The nm-system-settings daemon starts up and reads the ifcfg-ethX files, which is how my interface was configured on reboot after I just completed the install. Make sure your installs are installing NetworkManager on the system. If you do not want to use NetworkManager, your only option during installation is to handle that through kickstart. You can enable the network service and configure your interfaces the old way, but only when doing a kickstart install. The interactive installer will not offer that option to you.