- 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`
I would add
https:/ /wiki.strongswa n.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
--- /wiki.strongswa n.org/issues/ 3615)) :
Also the workaround we use at the moment (choose from this one or the script from [strongswan#3615](https:/
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/NetworkMa nager/NetworkMa nager.conf` :
[main]
dns=default
Delete the symlink /etc/resolv.conf
rm /etc/resolv.conf
Restart network-manager
sudo service network-manager restart