[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Changed in: network-manager (Ubuntu)
Assignee: Alexander Sack (asac) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/303159
Title:
IFUPDOWN -
** Changed in: network-manager (Ubuntu)
Milestone: jaunty-alpha-6 = None
--
IFUPDOWN - connections that are mapped should be locked to the mapping device
https://bugs.launchpad.net/bugs/303159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is milestoned, thus assigning to Alex. Alex, please fix, reassign
to someone else, or unmilestone (since this is a wishlist bug, this
would be appropriate). Thanks!
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
--
IFUPDOWN - connections that
The ifupdown interpretation of the mapping is:
a. If auto stanza exists run ifup $DEVICE at startup
b. When ifup $DEVICE is run for a mapping, run the mapping script, and
apply the config.
My personal preference for the ideal user-side experience for a mapping
device would be:
a. when device is
On Thu, Dec 04, 2008 at 04:01:57PM -, Stephan Trebels wrote:
I dont think I understand what you are trying to do.
We could determine the MAC from HAL, right. The issue is, that we cannot
do anything from there, I really wonder how this ever worked for me even
with the eth0-XXX naming
On Sat, Nov 29, 2008 at 08:45:13PM -, Stephan Trebels wrote:
** Description changed:
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
I dont think I understand what you are trying to do.
We could determine the MAC from HAL, right. The issue is, that we cannot
do anything from there, I really wonder how this ever worked for me even
with the eth0-XXX naming convention, how did it know which interface to
operate on? Consider the
** Attachment added: sample /etc/network/interfaces
http://launchpadlibrarian.net/20059194/interfaces
--
IFUPDOWN - connections that are mapped should be locked to the mapping device
https://bugs.launchpad.net/bugs/303159
You received this bug notification because you are a member of Ubuntu
** Attachment added: sample /usr/local/sbin/detect-network
http://launchpadlibrarian.net/20059214/detect-network
--
IFUPDOWN - connections that are mapped should be locked to the mapping device
https://bugs.launchpad.net/bugs/303159
You received this bug notification because you are a member
** Description changed:
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
12 matches
Mail list logo
