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