fairdk / fair-ubuntu-centre

MOVED: https://gitlab.com/fairdk/fair-ubuntu-centre
http://fair-ubuntu-centre.readthedocs.io/
GNU General Public License v3.0
3 stars 7 forks source link

Network Manager #2

Closed pdouglass closed 9 years ago

pdouglass commented 9 years ago

In 02-network.sh we remove the default (gnome) network manager, and go with a static configuration. This could be a liability because it makes it more difficult to change the servers network interfaces in the field.

Specifically, how would a USB-3G-dongle connected to the server be configured without a network manager. This, of course begs the question of how the mobile network interface would be configured with the network manager, but my assumption is that configuring an upling interface would be much smoother with the network manager, compared to editing /etc/network/interfaces.

benjaoming commented 9 years ago

I think we can keep the configuration static without removing the NetworkManager. But NM is actually removed because it interferes with the DNS server.

AFAIK, NetworkManager automatically detects when an interface is configured in /etc/network/interfaces.d -- so we should be able to keep it if we can work around the DNS issue.

Going with an interfaces.d configuration for the main interfaces is IMO a better approach as I would fear someone to mess with the network setup if it's available in the NetworkManager interface... and by "mess with" I mean mess it up so it doesn't work for 2 years.. having core configurations sort of locked down is totally fine.

pdouglass commented 9 years ago

Yes, it's a fine line between flexibility, and confusion.

But my test machine basically ignores interfaces.d, ifup and ifdown when the network manager is running.

I'll have to test the DNS server...

benjaoming commented 9 years ago

Dunno if NM was changed in Trusty... I hope not.. but it used to respect interfaces that were already configured when it starts (they would be shown in the NM applet's dropdown as disabled).

benjaoming commented 9 years ago

This has been fixed and has been working fine for a while :) :+1:

So it will just show the default eth0 interface as "not managed".