Am 04.01.2016 um 19:39 schrieb Chris Chiappa: > > On Mon, Jan 04, 2016 at 06:30:31PM +0100, Michael Biebl wrote: >> Hi Chris >>> -- Configuration Files: >>> /etc/NetworkManager/NetworkManager.conf changed: >>> [main] >>> plugins=ifupdown,keyfile >>> [ifupdown] >>> managed=true >> >> This means, you configured NetworkManager to manage the devices >> configured in /etc/network/interfaces. >> The default is "false", so NM doesn't touch any interfaces listed in /e/n/i. >> See the documentation in README.Debian. > Hi, thanks for the quick reply. I will accept that I'm off the map at > this point and will just learn how to set this up via NM, but > README.Debian says: > > ---=== > You can tell NetworkManager to read and use the network configuration > from /etc/network/interfaces by editing > /etc/NetworkManager/NetworkManager.conf > and changing the configuration as follows: > > [ifupdown] > managed=true > ===--- > > "use the network configuration" says, to me, that the fact that eth0 > is configured as a static IP in /e/n/i should be respected. Up until > this most recent reboot, that is how it worked.
Nothing changed in that regard for a long while. If you configure NM via managed=true, you tell it to read the configuration from /e/n/i and configure the interface accordingly. If you already have ifupdown enabled, this of course means that the interface will be managed by two systems. This is the reason why managed=false is the default. If you want to use managed=true, you should consider disabling/uninstalling ifupdown. But it's much better to simply configure the interfaces directly via NetworkManager and remove the interface configurations from /e/n/i. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
