Currently new openvpn client connection is marked as enabled and
immediately started after adding (after openvpn restart).

This can be quite dangerous, because enabling and starting new vpn
connection could mess up already running vpn connections or make router
inaccessible in certain circumstances, without simple way to disable
such vpn client.

Mark new vpn client as disabled after adding and force user to activate
it in additional separate action.

closes: #20

Temporary workaround for deprecated integration with setuptools since
version >=4.0

Traffic via newly added client won't pass through until firewall is reloaded.
Unfortunately it isn't triggered by network restart, so we have to make sure it happens.

Reloading firewall after removal of client on the other hand
seems to work fine most of the time, but still it isn't triggered by network restart reliably.
So this will force reload after removing vpn client as well.

Make flake8 happy :-)

Interface name has length limit we need to adhere to. Therefore cutting
the end of the VPN id.

Michal Hrusecky authored Jul 23, 2020 and Michal Hrusecky committed Oct 06, 2020

Add all VPN clients to firewall zone that is configured in similar way
as wan - enabled masquarading and everything prohibited.

Fixed indentation for "client" key

See merge request turris/foris-controller-openvpn_client-module!1