** Changed in: network-manager (Ubuntu)
Target: None => ubuntu-7.10
** Summary changed:
- ifup fails to bring up alias interfaces like eth0:10
+ n-m brings down slave interfaces like eth0:10
--
n-m brings down slave interfaces like eth0:10
https://bugs.launchpad.net/bugs/95968
You receiv
The problem is that network will still attempt to manage eth0 blantly
ignoring that when taking down the primary interface, all the slaves
like eth0:10 will go down too.
If you look at the backend code, you will see that network manager will
register the interfaces in its list, but does not know h
Fabio, can you please elaborate on that a bit? I don't see what network-
manager does wrong with those devices, it simply ignores them. So this
should rather be assigned back to ifupdown?
--
ifup fails to bring up alias interfaces like eth0:10
https://bugs.launchpad.net/bugs/95968
You received th
Martin, sorry but this is a bug and needs to be addressed. My fix for
ipv6 doesn't solve this specific issue.
There are multiple problems here. one n-m that doesn't know how to cope
with alias interfaces. two the kernel brings down the alias interfaces
when shutting down the main one (that's what
Current Feisty's version brings up the interfaces on boot with your
/e/n/i, and network-manager ignores them (goes into 'manual
configuration' state). However, n-m does shut down the subinterfaces
when I remove the main 'eth0' stanza. However, this is not a supported
configuration, it seems, since
** Changed in: network-manager (Ubuntu)
Target: ubuntu-7.04 => None
--
ifup fails to bring up alias interfaces like eth0:10
https://bugs.launchpad.net/bugs/95968
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
** Changed in: ifupdown (Ubuntu)
Target: None => ubuntu-7.04
--
ifup fails to bring up alias interfaces like eth0:10
https://launchpad.net/bugs/95968
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Fabio Massimo Di Nitto
--
ifup fails to bring up alias interfaces like eth0:10
https://launchpad.net/bugs/95968
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The problem her e is network-manager that doesn't know how to handle
alias interfaces.
When n-m resets the primary interface, the alias is taken down but not
reconfigured.
Fabio
** Changed in: network-manager (Ubuntu)
Sourcepackagename: ifupdown => network-manager
Assignee: Fabio Massimo Di
I confirm this behavior in Feisty. The same information in
'/etc/network/interfaces' works in Edgy.
--
ifup fails to bring up alias interfaces like eth0:10
https://launchpad.net/bugs/95968
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
Status: Unconfirmed => Confirmed
--
ifup fails to bring up alias interfaces like eth0:10
https://launchpad.net/bugs/95968
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo
Here is the interfaces file.
I have tried with and without the network and broadcast settings.
David Ames
** Attachment added: "/etc/network/interfaces file"
http://librarian.launchpad.net/7035361/interfaces
--
ifup fails to bring up alias interfaces like eth0:10
https://launchpad.net/bugs/
12 matches
Mail list logo
