I can't commit to spending time on this with my limited understanding of
the actual problem and whether it's still an issue in NetworkManager
now. Could someone running into this kind of issue on a similar setup
report back here and confirm whether the latest changes to the ifupdown
code in NetworkManager in version 0.9 have resolved this?
Thanks!
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: network-manager (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/303159
Title:
IFUPDOWN - connections that are mapped should be locked to the mapping
device
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
Binary package hint: network-manager
When running in managed=true mode, ifupdown will export configurations
of a mapping entry in /etc/network/interfaces without locking it to
the mapping device origin.
If a device exists with a mapping stanza then the mapping script may
select any of iface stanza "devices". The script is pretty much in
control of the naming of the device, so a $DEV-.* regex is wrong to
assume. A priori not even the link to a physical device is possible
without running the script, as the same mapping may be applicable to
multiple devices.
Probably the right thing to do is to hide all iface/mapping
"connections" that do not correspond to HAL-known devices. Then treat
a mapping like a DHCP connection, where a script is called on
activation (as in ifupdown) to select the iface stanza "connection"
for configuration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/303159/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
