On 09/01/2015 02:36 AM, Daniel Gnoutcheff wrote: > Package: freedombox-setup > Version: 0.5 > > If I use debian-installer to make a text-only system with (say) one > wired NIC, the installer usually creates a /etc/network/interfaces that > will have ifupdown manage that NIC. If I then install (and run) > freedombox-setup on said system, I end up with a FreedomBox whose wired > NIC is still managed by ifupdown and cannot be managed in Plinth > (wherein it's claimed to be "Not Active"). > > By default, network-manager will not manage any devices mentioned in > /etc/network/interfaces. debian-installer's netcfg copes with this by > suppressing the generation of that file (except for the loopback stanza) > when network-manager is installed [1] (e.g. by a desktop task). > > Perhaps we should be clearing out /etc/network/interfaces ourselves? > > [1] > http://sources.debian.net/src/netcfg/1.131/finish-install.d/55netcfg-copy-config/#L21 >
This seems like a reasonable proposal. Earlier we configured network interfaces only via entries in /etc/network/interfaces and this was not a problem. When we switched this configuration to NetworkManager, we stopped clearing the /etc/network/interfaces in hopes of not messing with existing configuration. This, however, didn't work out well given that PackageKit complains that network is offline when not even one connection is configured via NetworkManager. Also, not being able to configure the network interface from Plinth is not nice. We should go ahead with your proposal and clear out /etc/network/interfaces with merely an entry for "lo". -- Sunil
signature.asc
Description: OpenPGP digital signature
