| 2007-03-25 16:05:26 |
David Ames |
bug |
|
|
added bug |
| 2007-03-28 14:21:06 |
David Ames |
bug |
|
|
added attachment 'interfaces' (/etc/network/interfaces file) |
| 2007-03-28 17:46:11 |
Brian Murray |
ifupdown: status |
Unconfirmed |
Confirmed |
|
| 2007-03-28 17:46:11 |
Brian Murray |
ifupdown: importance |
Undecided |
Medium |
|
| 2007-03-28 17:46:11 |
Brian Murray |
ifupdown: statusexplanation |
|
|
|
| 2007-03-30 12:39:37 |
Tollef Fog Heen |
ifupdown: assignee |
|
fabbione |
|
| 2007-03-30 14:10:09 |
Fabio Massimo Di Nitto |
ifupdown: assignee |
fabbione |
|
|
| 2007-03-30 14:10:09 |
Fabio Massimo Di Nitto |
ifupdown: statusexplanation |
|
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 |
|
| 2007-04-10 17:05:48 |
Scott James Remnant (Canonical) |
network-manager: statusexplanation |
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 |
|
|
| 2007-04-13 12:43:02 |
Martin Pitt |
bug |
|
|
added subscriber Fabio Massimo Di Nitto |
| 2007-04-13 12:46:32 |
Martin Pitt |
network-manager: status |
Confirmed |
Fix Released |
|
| 2007-04-13 12:46:32 |
Martin Pitt |
network-manager: statusexplanation |
|
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 ifupdown itself is not able to bring it up (it fails with 'SIOCSIFFLAGS: Cannot assign requested address'). Thus this network-manager upload has fixed this case:
network-manager (0.6.4-6ubuntu4) feisty; urgency=low
* /etc/network/interfaces can have more than one instance of the same
interface. For example:
iface eth0 inet dhcp
and later
iface eth0 inet6 static
The function ifparser_getif is capable only to return the first instance
of eth0 that is a legal entry for NM to take over, but NM still does not
know how to handle what's next.
Patch 19_interfaces_can_have_more_than_one_instance.patch creates a sub
list of linked if_block via nextsame, binding together all if_block's
related to the same interface and preserving if_data for each block.
Patch 20_do_not_take_over_dhcpv4iface_when_v6_is_configured.patch
blacklist interfaces that have dhcp for inet configuration but have an
inet6 entry following later on. NM does not know yet how to
store/restore/configure IPv6 (blacklisted too) so for now we tell NM
to keep the hands off these interfaces.
(Closes LP: #93636)
-- Fabio M. Di Nitto <fabbione@ubuntu.com> Fri, 30 Mar 2007 11:17:42 +0200
|
|
| 2007-04-14 10:21:32 |
Fabio Massimo Di Nitto |
network-manager: status |
Fix Released |
Confirmed |
|
| 2007-04-14 10:21:32 |
Fabio Massimo Di Nitto |
network-manager: statusexplanation |
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 ifupdown itself is not able to bring it up (it fails with 'SIOCSIFFLAGS: Cannot assign requested address'). Thus this network-manager upload has fixed this case:
network-manager (0.6.4-6ubuntu4) feisty; urgency=low
* /etc/network/interfaces can have more than one instance of the same
interface. For example:
iface eth0 inet dhcp
and later
iface eth0 inet6 static
The function ifparser_getif is capable only to return the first instance
of eth0 that is a legal entry for NM to take over, but NM still does not
know how to handle what's next.
Patch 19_interfaces_can_have_more_than_one_instance.patch creates a sub
list of linked if_block via nextsame, binding together all if_block's
related to the same interface and preserving if_data for each block.
Patch 20_do_not_take_over_dhcpv4iface_when_v6_is_configured.patch
blacklist interfaces that have dhcp for inet configuration but have an
inet6 entry following later on. NM does not know yet how to
store/restore/configure IPv6 (blacklisted too) so for now we tell NM
to keep the hands off these interfaces.
(Closes LP: #93636)
-- Fabio M. Di Nitto <fabbione@ubuntu.com> Fri, 30 Mar 2007 11:17:42 +0200
|
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 triggers n-m to remove everything basically).
The kernel "issue" is a well known and wanted behaviour.
NM needs to grow a patch similar to the ipv6 one in order to track nextsamealias and ignore the main interface if the pointer is non null in the list.
Fabio
PS alias interfaces are common and support. we support the kernel and we do support ifupdown and they work just fine here. |
|
| 2007-04-25 07:38:51 |
Martin Pitt |
network-manager: statusexplanation |
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 triggers n-m to remove everything basically).
The kernel "issue" is a well known and wanted behaviour.
NM needs to grow a patch similar to the ipv6 one in order to track nextsamealias and ignore the main interface if the pointer is non null in the list.
Fabio
PS alias interfaces are common and support. we support the kernel and we do support ifupdown and they work just fine here. |
|
|
| 2007-04-25 07:39:14 |
Martin Pitt |
title |
ifup fails to bring up alias interfaces like eth0:10 |
n-m brings down slave interfaces like eth0:10 |
|
| 2007-09-21 16:53:38 |
Alexander Sack |
network-manager: status |
Confirmed |
Fix Released |
|
