Re: Back to technical discussion? Yes! (was: network-manager as default? No!)
On Mon, Apr 4, 2011 at 9:20 PM, Stanislav Maslovski
>> Also note that there are NM plugins that enable NM to understand
>> /etc/network/interfaces and the Fedora/RHEL counterparts. This means
>> that if a server has NM enabled and an administrator wants to
>> configure networking manually, he can do it just fine even if NM is
>> installed. NM will gracefully understand that and won't try to do
>> anything stupid (see /etc/NetworkManager/NetworkManager.conf).
> The mentioned plugin is nothing more than just a rather primitive
> parser intended to read a limited set of common interface settings
> such as ip addresses, netmasks, dns servers, etc., from the existing
> /e/n/interfaces file for the ease of transition. The plugin simply
> translates these settings into the internal representation of NM. It
> is not intended to interoperate with the ifupdown infrastructure in
> any other way.
> Therefore, it is generally useless for an administrator that wants to
> configure network interfaces manually.
Yes, it's "just" a parser. It can still be used to "configure" NM via
/etc/network/interfaces, at least according to README.Debian (never
Managed mode will make NetworkManager manage all devices and will make
NetworkManager honour all dhcp and static configurations for wired and
Which means you should be able to keep using /etc/network/interfaces
for simple setup. ifupdown and friends will not work in that scenario,
or the other way around, obviously.
>> For servers using DHCP, you don't even have to create a connection.
>> Wired interfaces are already automatically configured to use DHCP in
>> NM. For the other cases, just use the legacy tools or configure
>> /etc/network/interfaces and set managed=true
> Accordingly to docs here http://live.gnome.org/NetworkManager/SystemSettings
> that should be actually "managed=false" if you want an interface to be
> completely ignored by NM.
Yes, it's managed=false, sorry. That's the default in Debian AFAICT,
which means that /etc/network/interfaces takes precedence.