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 or the script from [strongswan#3615](https://wiki.strongswan.org/issues/3615)) : use `network-manager` (static) instead of `systemd-resolved` sudo systemctl disable systemd-resolved.service sudo systemctl stop systemd-resolved Put `dns=default` in the `[main]` section of your `/etc/NetworkManager/NetworkManager.conf`: [main] dns=default Delete the symlink /etc/resolv.conf rm /etc/resolv.conf Restart network-manager sudo service network-manager restart ** Bug watch added: wiki.strongswan.org/issues #3615 https://wiki.strongswan.org/issues/3615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783377 Title: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
