Bug 443968
Summary: | [enh] ifcfg-rh: handle device aliases | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Davide Moretti <dave> | ||||
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 14 | CC: | 98036119lmak, akostadi, axel.thimm, dcbw, ingvar, jklimes, jns, john, mal, mike, mishu, oggust, pierre-bugzilla, pkgale, sbonnevi, stsp2, voas0113, wendellcraigbaker, wtogami | ||||
Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-08-16 21:50:59 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Davide Moretti
2008-04-24 13:06:44 UTC
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I am seeing a similar type problem. After installing Fedora 9 my network failed to start automatically. NetworkManager showed the two Wired connections, both marked as "never", and not started. Manually running: service network restart starts the network normally. After investigating, I found that neither of my wired network connections were marked as controlled by NetworkManager. I marked both connections as managed by network manager, and manually entered the Mac address into NetworkManager. After that, NetworkManager was able to start connection 1, but not connection 2. Since I am not using wireless, I finally decided just to use the good old "network" init.d script, and to disable NetworkManager. So the two features I could not get to work with NetworkManager: 1. For NetworkManager to work automatically post install. 2. Multicasting with DHCP and a static address. 3. Both IPV6 and IPV4 enabled. Here is my networking-script configurations that work with "network" but I can't get to work with NetworkManager: [root@localhost network-scripts]# grep -v DNS1 ifcfg-eth0 | grep -v SEARCH # Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:19:b9:11:5e:e2 IPV6INIT=yes IPV6_AUTOCONF=yes ONBOOT=yes NM_CONTROLLED=no TYPE=Ethernet USERCTL=yes PEERDNS=yes [root@localhost network-scripts]# grep -v DNS1 ifcfg-eth0:1 |grep -v SEARCH # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. TYPE=Ethernet DEVICE=eth0:1 BOOTPROTO=none NETMASK=255.255.255.0 IPADDR=192.168.2.201 USERCTL=yes PEERDNS=yes IPV6INIT=no ONPARENT=yes NM_CONTROLLED=no See related bug #439103 *** Bug 474901 has been marked as a duplicate of this bug. *** This bug has been triaged -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** Bug 490274 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Bumped to F10 for now.... I have to check in F11... NetworkManager on F11 allows to assign multiple IP to an interface so this issue is resolved in F11. (it did that in F10 too) but we still need to at least interpret the ifcfg-eth0:1 style files in /etc/sysconfig/network-scripts in the ifcfg-rh system settings backend plugin. *** Bug 509641 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** Bug 561589 has been marked as a duplicate of this bug. *** It still exists in the release version of Fedora 12. Additionally, if you work around this bug by defining the loopback (eth0:1) in rc.local, it will get disabled later on. /var/log/messages says that ntpd is disabling it, but that could be due to this issue. This is especially fun in conjunction with RHEL 6 bug 633984 where initscripts can't understand how NetworkManager sets multiple IP addresses the modern way on a single interface, either. So there's no consistent way to set multiple IPs per interface in the configuration files that both initscripts and NetworkManager understand. (Mind you, I'd be happy if initscripts understood IPADDR2/PREFIX2, but it'd be best if everything worked either way.) This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Created attachment 459129 [details]
[PATCH] support ifcfg aliases
The patch implements basic alias support in 'ifcfg-rh' plugin.
It recognizes alias files and puts the addresses to base connection instead of creating another connection.
However, the implementation has several limitations and differences against initscripts. As a legacy thing, I think, it's not worth to completely simulate initscripts behaviour, as it would require big effort and some workarounds in NM.
Differences, not implemented stuff:
- ifcfg-$DEV-range* files with IP ranges are not implemented
- no virtual interfaces are created (all addresses are configured on main interface)
- updating a connection merges all IPs into main ifcfg file and alias files are removed
- base file has to have manual IP configuration (when it's DHCP, IP aliases won't be added)
Review, comments, suggestions, improvements are welcomed.
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Dan, would you find a while to review the patch? F16 NetworkManager is not capable of making alias, at least not GUI configurable way. (In reply to comment #20) > F16 > NetworkManager is not capable of making alias, at least not GUI configurable > way. It's not capable of making aliases, but you certainly can configure multiple IP addresses on the same interface, which was the whole point of the hack that is interface aliases in the first place. (In reply to comment #17) > Created attachment 459129 [details] > [PATCH] support ifcfg aliases > > The patch implements basic alias support in 'ifcfg-rh' plugin. > It recognizes alias files and puts the addresses to base connection instead of > creating another connection. > > However, the implementation has several limitations and differences against > initscripts. As a legacy thing, I think, it's not worth to completely simulate > initscripts behaviour, as it would require big effort and some workarounds in > NM. > > Differences, not implemented stuff: > - ifcfg-$DEV-range* files with IP ranges are not implemented > - no virtual interfaces are created (all addresses are configured on main > interface) > - updating a connection merges all IPs into main ifcfg file and alias files are > removed > - base file has to have manual IP configuration (when it's DHCP, IP aliases > won't be added) > > Review, comments, suggestions, improvements are welcomed. Patch looks good from a quick review, though we should definitely get some testcases for this functionality too. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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 |