Apart from the bug itself I would like to ask why on earth is Network Manager (NM) NOT DESIGNED to ALSO enable system-wide fixed networks settings per interface?
NM is ok for most laptops, but when on a workstation or any other system providing services to other machines NO becomes completely USELESS.
Linux is a very powerfull platform for servers and networking... it seems a bit stupid to me that its best config tool to date are text-file editors likek gedit or vi. I should be able to do simple tasks on a GUI, for instance:
1) Setting up a fixed-server system wide network config (fixed ip + gw on interface)
2) Setting up a PERSISTENT route (not having to make and ad-hoc script undes /etc/network/if-up.d...)
3) Setting up custom network configurations per profile (per SSID depending on the wireless network I get into, or per profile name 'work' vs 'home' etc)
Apart from the bug itself I would like to ask why on earth is Network Manager (NM) NOT DESIGNED to ALSO enable system-wide fixed networks settings per interface?
NM is ok for most laptops, but when on a workstation or any other system providing services to other machines NO becomes completely USELESS.
Linux is a very powerfull platform for servers and networking... it seems a bit stupid to me that its best config tool to date are text-file editors likek gedit or vi. I should be able to do simple tasks on a GUI, for instance:
1) Setting up a fixed-server system wide network config (fixed ip + gw on interface) if-up.d. ..)
2) Setting up a PERSISTENT route (not having to make and ad-hoc script undes /etc/network/
3) Setting up custom network configurations per profile (per SSID depending on the wireless network I get into, or per profile name 'work' vs 'home' etc)