[Touch-packages] [Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

I would add https://wiki.strongswan.org/issues/3615 - Local workaround with a script triggered in `pre-up` stage to restart service - Explanation of upstream workaround (see previous comment/commit) that uses a dummy TUN device --- Also the workaround we use at the moment (choose from this one

[Touch-packages] [Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

A small script to do the job : * install 18.10 repository with lower pin priority * install a hook that restarts "systemd-resolved" on "vpn-pre-up" action ** Attachment added: "# Script to deploy strongswan's packages on 18.04 from 18.10 # and add logic to restart systemd-resolve service when

[Touch-packages] [Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

** Description changed: Ubuntu 18.04.1 / bionic + + systemd: + Installé : 237-3ubuntu10.3 Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required

[Touch-packages] [Bug 1783377] [NEW] systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

Public bug reported: Ubuntu 18.04.1 / bionic Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2):