FYI - Tobias wasn't keen on the dummy interface option, per his response here https://github.com/strongswan/strongswan/discussions/2085#discussioncomment-9678750 (though maybe that is a good option, but dnsmasq needs to be changed to suit it?)
I also hit a problem where a server I wish to access over the VPN also has an IP address on the public internet - and whereas with the old resolvconf executable, somehow starting the VPN used to automatically switch me to using the VPN version of that server, using a dummy interface this didn't happen - it kept using the public ip address for this server. By setting iface in /etc/strongswan.d/charon/resolve.conf to my ethernet interface, it replaced the public DNS (1.1.1.1) on that interface with my VPN DNS servers, so things worked. Unfortunately, when the VPN went down, it didn't restore 1.1.1.1 (and I'd hoped might be possible with the resolvectl "revert" command - alas no) - it just removed all DNS on that link. I've almost zero knowledge in this space compared to Tobias, Lennart, etc - but it certainly feels like stuff that just worked with the old resolvconf has become quite the headache now - even if the new resolvectl resolvconf is better for a bunch of other reasons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067897 Title: Ubuntu 24.04 does not install resolvconf uses systemd-resolved instead which is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
