Bug 523064
| Summary: | ifup/ifdown should call NM for NM-controlled devices | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | W. Michael Petullo <mike> | |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 12 | CC: | dcbw, iarlyy, jonathan, maier, notting, plautrba, rvokal, thomas.mey, thvv | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | initscripts-9.08-1.fc13 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 550154 (view as bug list) | Environment: | ||
| Last Closed: | 2010-03-03 21:34:39 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 550154 | |||
|
Description
W. Michael Petullo
2009-09-13 20:09:51 UTC
The configuration that NetworkManager wrote was: ESSID="XXX" MODE=Managed KEY_MGMT=WPA-PSK TYPE=Wireless BOOTPROTO=dhcp PEERDNS=yes PEERROUTES=yes NAME="XXX" UUID=XXX ONBOOT=yes I found that this was fixed by adding: DEVICE=eth1 akmod-wl sets up /etc/udev/rules.d/70-persistent-net.rules so that my device is eth1. So, since this was fixed by adding a DEVICE=eth1 line, should this be a NetworkManager bug? Yes - if it's not named after the device, there needs to be a DEVICE= line. NM doesn't add DEVICE= because your device names can change, irregardless of the udev rules to keep them the same because that doesn't always work. In any case, that connection can apply fine to *any* device you plug in, not just eth1, and you didn't choose to limit it to only eth1 in the connection editor (by locking the connection to the device's MAC address). I seem to recall that if there's an HWADDR, the initscripts will try to find that device even without a DEVICE= line Bill? Or is that just that when there's both DEVICE and HWADDR, it makes sure DEVICE actually has that specific HWADDR? *** Bug 525816 has been marked as a duplicate of this bug. *** It's just used to make sure config + hwaddr match. We *could* make it try to automatically figure out the device, but there's no code for that now. Ok, moving this to a bug about ifup/ifdown integration like we'd talked about for a long time making ifup/ifdown direct NM for NM-controlled devices. *** Bug 526317 has been marked as a duplicate of this bug. *** ------- Comment From kumarr.com 2009-10-19 18:14 EDT------- Mirroring *** Bug 513453 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 The first cut of this will be in 9.07-1. initscripts-9.07-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/initscripts-9.07-1.fc13 The new initscripts-9.07-1.fc13 package seems to work. Thanks, Bill and Dan. Cool. Note that configurations that don't specify a device (like some wireless connections) aren't fully supported yet; ifup will work, but ifdown won't. initscripts-9.08-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |