Comment 13 for bug 95968
Revision history for this message
| Paul Collins (paul-collins-iii) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
I'd like to reopen this bug. I believe N-M has incorrect behavior in this case. When a interface is reset (say network cable unplugged), and N-M brings back up the primary interface, it should also bring up any aliased interfaces with it. Case in point, I eth0 and eth0:0
eth0 is DHCP
eth0:0 is statically assigned
When the network goes down for whatever reason eth0 & eth0:0 go down. When it comes back, eth0 comes back up but eth0:0 has to be done manually. Additionally, N-M has no way for me to see the aliased interface or to interact with it.