[Bug 381586] Re: Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager
I haven't seen reports of such issues on new installs and updating /etc/network/interfaces on existing installs is out of the question. I think it'd have probably been a good idea to indeed do that change when we switched to Network Manager for the desktop but don't think it's worth the trouble doing it now (4 years later). ** Changed in: ifupdown (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/381586 Title: Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/381586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381586] Re: Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager
** Description changed: - Binary package hint: ifupdown + There are a lot of people seeking help, because they followed some old + how-to and caused their network interfaces to became unmanaged. And they + will have no idea why the pretty GUI(NetworkManager) has stopped + working. - There are a lot of people seeking help, because they followed some old "how to" and their network interfaces became unmanaged. - A warning at the top of /etc/network/interfaces could help this situation. + A warning at the top of /etc/network/interfaces could help this + situation: - Example of such a "how to": https://help.ubuntu.com/community/ADSLPPPoE - (following this will turn off DHCP on eth0 and make it unmanaged and people will wonder why NetworkManager is not working) + Example of such a how-to: https://help.ubuntu.com/community/ADSLPPPoE + For example this how-to instruct them to add eth0 to the "interfaces" file and as a result it becomes unmanaged. -- Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager https://bugs.launchpad.net/bugs/381586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381586] Re: Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager
** Description changed: -- Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager https://bugs.launchpad.net/bugs/381586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381586] Re: Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager
** Description changed: Binary package hint: ifupdown There are a lot of people seeking help, because they followed some old "how to" and their network interfaces became unmanaged. A warning at the top of /etc/network/interfaces could help this situation. Example of such a "how to": https://help.ubuntu.com/community/ADSLPPPoE - (following this will turn off DHCP on eth0 and make it unmanaged) + (following this will turn off DHCP on eth0 and make it unmanaged and people will wonder why NetworkManager is not working) -- Add a warning to the interfaces file that interfaces present in this file won't be managed by network-manager https://bugs.launchpad.net/bugs/381586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs