El 01-11-2018 a las 9:41, Paul Menzel escribió:
If yes, do you have any hints before I start to dig into that?
opening TUN/TAP interfaces and changing routing is a privileged operation.
___
systemd-devel mailing list
Hello Paul, ...
As one option, it is possible to spin up a systemd-nspawn container, run
the openvpn server in there with it's own networking namespace, and map the
port of the openvpn server to the host.
You can make all kind's of scenarios, ...
Greetings, ...
Paul Menzel ezt írta (időpont:
Dear systemd folks,
Our users sometimes need to access the internal network of another
organization, but unfortunately SSH access is blocked, and it’s only possible
over OpenVPN. With that, they could use their browser and SSH to access the
internal network.
Due to security reasons, we do not
On Thu, Nov 1, 2018 at 11:34 AM piliu wrote:
>
> Hi,
>
> I encounter an issue during the poweroff. In my bash script, firstly I
> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
> as a bake up if the poweroff fails. But during tests, many times, the
> machine is rebooted
Am 01.11.18 um 09:34 schrieb piliu:
> I encounter an issue during the poweroff. In my bash script, firstly I
> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
> as a bake up if the poweroff fails. But during tests, many times, the
> machine is rebooted directly, without
Hi,
I encounter an issue during the poweroff. In my bash script, firstly I
use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
as a bake up if the poweroff fails. But during tests, many times, the
machine is rebooted directly, without waiting for the result of poweroff.
Since
