Hide Forgot
Description of problem: I use system-config-network to create an alias of the wired Ethernet interface. I start it manually and it operates correctly. I configure it to start at boot just like the normal Ethernet device. On boot, the normal eth0 device is enabled but the eth0:1 is not reported at all by ifconfig. Version-Release number of selected component (if applicable): NetworkManager.x86_64 1:0.8.4-1.fc14 system-config-network.noarch 1.6.2-1.fc14 How reproducible: Every time. Steps to Reproduce: 1. Setup eth0 to get address by DHCP, controlled by NM, and start at boot. 2. Setup eth0:1 to masquerade on eth0 using static IP 192.168.1.20. This is outside of the IP range that the DHCP server manages. 3. Use system-config-network to manually enable eth0:1 4. Use ping to verify that this address is active from another computer. ping 192.168.1.20 5. Use ifconfig to show that eth0:1 is in the list of system network interfaces and that it has an address. 6. Reboot. Actual results: Use ifconfig to show the list of system network interfaces. Observe that eth0:1 is not present. Ping does not work. Expected results: ifconfig should show that eth0:1 is present and has address 192.168.1.20 ping should work. Additional info: 1. This does work if NM is not allowed to control either eth0 or eth0:1 using the older /etc/init.d/network daemon. 2. I have Fedora 15 running on a HP server with a AMD PhenomX6 processor. The older /etc/init.d/network daemon does not work for the Ethernet interface on this machine by NM does. I am not using masqerading on the F15 box at this time but I may need to in the future. I do not know if NM on F15 also has this problem but it indicates that sometimes the /etc/init.d/network workaround will not work. 3. I checked /var/log/messages and dmesg for information and saw nothing related to eth0.
I have this problem too. I'd like to see my ADSL-modem statistics time to time, while connected to Internet with public Internet address. In order to see ADSL-modem's info, eth0:1 has to be configured to 10.0.0.X/24. Network manager doesn't bring this eth0:1 interface up although it is configured with system-config-network (or either manually in /etc/sysconfig/network-scripts/) I can bring the eth0:1 up though manually by running # ifup eth0:1 ...after the Network manager has brought eth0 up with DHCP.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping