Description of problem: I reinstalled F15, (removed the alpha and installed the beta). I do use static ip, so when i tried to set it up i found that i could not! I do use KDE. I do use eth1, in the example below dhcp is used (default). With system-config-network, there are no devices to configure, so nothing can be done. # ifconfig em1 Link encap:Ethernet HWaddr 00:24:8C:38:2B:0C UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:43 Base address:0xa000 eth1 Link encap:Ethernet HWaddr 00:06:4F:5A:DD:A8 inet addr:192.168.1.112 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::206:4fff:fe5a:dda8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10245 errors:0 dropped:0 overruns:0 frame:0 TX packets:6021 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13020744 (12.4 MiB) TX bytes:481088 (469.8 KiB) Interrupt:19 Base address:0xdc00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:164 errors:0 dropped:0 overruns:0 frame:0 TX packets:164 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12912 (12.6 KiB) TX bytes:12912 (12.6 KiB) Only the loopback has its corresponding config file, maybe there is really no interface to configure... # ls -l /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 254 Apr 6 17:22 /etc/sysconfig/network-scripts/ifcfg-lo I did not experience this issue when i installed the alpha. (i installed before the emX stuff apeared). Version-Release number of selected component (if applicable): system-config-network-tui.noarch 1.6.2-2.fc15 @koji-override-0/$releasever How reproducible: allways Steps to Reproduce: 1. system-config-network (no interfaces to configure, cannot switch to static-ip) Actual results: no static ip, just NM dhcp. Expected results: be able to configure present nics Additional info:
I was able to configure it by manually creating the config file (in this case, /etc/sysconfig/network-scripts/ifcfg-eth1), mostly copied from F13 partition. Disabled NetworkManager Stoped network put eth1 down with ifconfig and lastly started network. as expected, eth1 was configured with static-ip correctly. it seems that F15 beta, does not create the ethernet devices config files under /etc/syconfig/network-scripts/ifcfg-* as previous versions.
(In reply to comment #1) > it seems that F15 beta, does not create the ethernet devices config files under > /etc/syconfig/network-scripts/ifcfg-* as previous versions. Not sure whether that's anaconda or NM issue. Let's start with NM.
*** Bug 650848 has been marked as a duplicate of this bug. ***
/etc/syconfig/network-scripts/ifcfg-* files for devices are firstly created by anaconda installer. That works for me. What do you get by ls /etc/syconfig/network-scripts/ifcfg-* after clean install? Over to anaconda.
> Only the loopback has its corresponding config file, maybe there is really > no interface to configure... > # ls -l /etc/sysconfig/network-scripts/ifcfg-* > -rw-r--r--. 1 root root 254 Apr 6 17:22 > /etc/sysconfig/network-scripts/ifcfg-lo Only the loopback config file was there after install. I noticed the issue when trying to setup static ip via system-config-network. system-config-network cannot operate with no config files, it does nothing.
Could you attach log files anaconda.log, anaconda.syslog, and anaconda.ifcfg.log from /var/log/anaconda directory please? I think system-config-network is deprecated tool, you should use NetworkManager Applet and NetworkManager Connection Editor to configure networking.
Created attachment 495531 [details] anaconda.ifcfg.log
Created attachment 495535 [details] anaconda.log There is no anaconda.syslog file, only anaconda.program and anaconda.storage. > I think system-config-network is deprecated tool, you should use NetworkManager > Applet and NetworkManager Connection Editor to configure networking. That is how i use my laptop or netbook, but in a desktop the first thing i do is disable NetwrokManager and set static-ip, i don't need or want NetworkManager for this type setup. Maybe F15 is different, but the sophistication of NM is not needed for a basic static ip 7/24. If system-config-network is really unsupported (not deprecated) it must be removed. If it is deprecated, it must work until it becomes unsuported.
Just to explain a bit: in live CD, anaconda doesn't write any ifcfg files because network should be configured with NetworkManager (applet and connection editor) of the live CD environment. NM would write the files only after saving an existing or changed configuration from its Connection Editor.
Then, for my case, the correct thing to do (starting with F15 onwards) is: * disable network manager (because i dont want to use it here) * create the network card config files by hand and enable network service i do not have a problem doing that by hand, just feels strange. --- is the dvd image different? --- the alpha behaved different and did not have this issue. --- again, if system-config-network is usupported, it must be removed. if i not mistaken, deprecated mean that it is supported but will be removed/unsuported in the future (not in the present) ---- I will reinstall again in the weekend and also will try some VMs. The only thing keeping from reinstalling now are those monstrous debug-symbols (my internet 'broadband' is 100k :-( ), so reinstalling now will interfere with debugging other bug-reports.
(In reply to comment #10) > Then, for my case, the correct thing to do (starting with F15 onwards) is: > > * disable network manager (because i dont want to use it here) > * create the network card config files by hand and enable network service > You could also (after installation) "Save" existing connection configuration in Connection Editor and NM will create ifcfg files for you. The editor can be run e.g. from gnome control center in Gnome3 (can be accessed via NM applet on panel) or from command line with nm-connection-editor. > > is the dvd image different? Yes in normal install we create default ifcfg files in loader stage which is not run in liveCD environment. > > the alpha behaved different and did not have this issue. > I don't recall any changes in anaconda between alpha and beta that could cause the change, but it might be also NM. > again, if system-config-network is usupported, it must be removed. > if i not mistaken, deprecated mean that it is supported but will be > removed/unsuported in the future (not in the present) > sorry, I am not sure about its present status
This bug-report was filled agains F15 beta. Fedora 17 was released some time ago. I think this bug-report can be closed.