{{Header}}
{{#seo:
|description=Development Notes about Network Manager
}}

= Network Manager =
{{mbox
| image   = [[File:Ambox_warning_pn.svg.png|40px|alt={{project_name_long}} first time users warning]]
| text    = This page is out of date.
}}
{{mbox
| image   = [[File:Ambox_warning_pn.svg.png|40px|alt={{project_name_short}} first time users warning]]
| text    = At time of writing, Qubes(-{{project_name_short}}) does not use ifupdown, but Qubes custom implementation.
}}

It would be desirable to have a graphical network manager installed in {{project_name_workstation_long}}. There are a few main use cases. Changing {{project_name_workstation_long}} internal IP address for [[Multiple Whonix-Workstation|Multiple {{project_name_workstation_long}}]], setting up a post-Tor-VPN using a graphical user interface and other kinds of advanced network configurations over Tor which are simpler to set up using a grapical user interface.

At the moment networking still managed by the ordinary ifupdown way. ([[Template:Network_Config]])

If you want to install the KDE Network Manager.

<pre>sudo apt install network-manager-kde</pre>

Then it can be started from the Start Menu.

<pre>Start menu &rarr; System Settings &rarr; Network Settings</pre>

You won't see {{project_name_short}} internal network interface right away. You could make it visible in Network Manger, by editing /etc/NetworkManager/NetworkManager.conf and setting managed to true.

<pre>
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true
</pre>

That would be quite useful, if changing settings where possible. However, the NetworkManager.conf man page says, write support for ifupdown managed devices is not planned.

The Fedora wiki has a nice page about [https://fedoraproject.org/wiki/Tools/NetworkManager Network Manager] which is useful for a distro packager perspective.

Quote: "''NM is slowly changing from a desktop network connection configurator to a universal network configuration software that could be used as a part of the base system.''"

Once NM can do everything ifupdown can do (i.e. suitable for all tasks also from command line), ifupdown in {{project_name_short}} could get completely replaced with NM.

Since IPv6 support in NM is said to be not in a production state yet, I am hesitate to switch to NM. Tor recently added support for IPv6 bridges and full IPv6 support could come in future. If Tor fixes IPv6 support first, there would eventually still (again) need for ifupdown. Therefore I think at the moment it is best to let NM mature.

For running NM on {{project_name_gateway_long}} it would be required to check if the pre-up hook to start the firewall works flawless. Having a pre-up hook which fails closed like ifupdown currently provides is desirable, because when there is a tiny syntax error in the firewall, the network won't come up and nothing leaks. Alternatively, an init.d script could be developed, it would have to be researched, if it can provide the same fail closed protections.

Since many people are interested in post-Tor-VPNs (user &rarr; Tor &rarr; VPN), it is open for debate if network-manager-kde should be pre-installed on {{project_name_workstation_short}}. Would the user be confused because it won't show the (virtual) wired internal network interface? Would it be less/more confusing if the (virtual) wired internal network interface where shown but impossible to edit? Shouldn't it be pre-installed for these confusion reasons and recommended to be installed manually for users interested in post-Tor-VPNs?

As a footnote, it is also possible to use Gnome applications in {{project_name_short}} (KDE based), such as [[Tunnels/Examples#GNOME_Network_Manager|Gnome Network Manager chapter on Tunnels/Examples page]].

[https://bugzilla.gnome.org/show_bug.cgi?id=689339#c4 Quote]:

<blockquote>"''Please also understand that currently networkmanager is not a security tool at all. VPN plugins are regarded as connectivity plugins, not security plugins.''"
</blockquote>

Missing auto-reconnect feature: https://bugzilla.gnome.org/show_bug.cgi?id=349151

So perhaps using NM to set up VPNs for security is not a good idea.

Doesn't look like NM has a fail closed mechanism: [[VPN-Firewall]]

{{Footer}}

[[Category:Development]]