Hi Michael,
Thanks for the troubleshooting. I think we have several options here
(as far as I see). We can also combined some of them:
- Modify ifupdown to be aware of networkmanager installation (as you
suggested)
- Modify networkmanager to remove/modify/backup /e/n/i interfaces managed
by it (at installation time only or automatically done after the interfaces
is managed by networkmanager - this last one is even complex?)
- Message in networkmanager at installation time if ifupdown is installed
(also include this information in /usr/share/doc)
- Modify networkmanager documentation (
http://wiki.debian.org/NetworkManager#Enabling_Interface_Management) to
point out Michael suggestion to manually remove references in /e/n/i for
interfaces managed by networkmanager (if not done automatically by previous
options)
What do you think?
Regards
On Sun, Nov 18, 2012 at 1:39 PM, Michael Biebl <bi...@debian.org> wrote:
> On 18.11.2012 13:29, Miguel A. Rojas wrote:
> > # The primary network interface
> > allow-hotplug eth0
> > iface eth0 inet static
> > address 192.168.2.2
> > netmask 255.255.255.0
> > network 192.168.2.0
> > broadcast 192.168.2.255
> > gateway 192.168.2.1
> > # dns-* options are implemented by the resolvconf package, if
> > installed
> > dns-nameservers 85.62.229.131 85.62.229.132
> > -------------------------------------------
> >
> > As you may see, after networkmanager installation,
> > /etc/network/interfaces was not modified (I do not know if this is the
> > default behaviour). I managed to enable interface managed according to
> > http://wiki.debian.org/NetworkManager#Enabling_Interface_Management.
> > After doing that, networkmanager was able to manage the interface and I
> > suppose it got the information from /etc/network/interfaces.
> >
> > Let me know if you need anything else from my side. I really do
> > not know where this route is coming from. Perhaps I did something wrong
> > in the procedure, but I just followed the standard manuals.
>
> So, the problem is basically this:
> You have eth0 configured in /etc/network/interfaces.
>
> This device is now configured *both* by ifupdown and NetworkManager if
> you set managed=true. So I actually do not recommend that as maintainer
> of network-manager (contrary to what the wiki says).
> So, if you want to manage eth0 with NetworkManager it is better to
> remove the (eth0) configuration from /etc/network/interfaces completely,
> so ifupdown does no longer touch it.
>
> Now, while NetworkManager does not enable a ethernet interface if there
> is no network link, ifupdown does not care.
> It simply runs "ifup eth0" during boot.
> This is why your eth0 network device is brought up and you have this
> route entry.
>
> So, in summary, I don't think there is actually a bug in
> network-manager. It's just the way what happens if you configure your
> system to use managed=true.
>
> Andrew, do you have a better idea how to handle this situation?
> Could ifup/ifdown be changed to check if managed=true is set and not
> configure the device in this case?
>
> Michael
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>
