On Wed, Apr 03, 2024 at 03:41:17PM +0200, Michael Biebl wrote: > Am 03.04.24 um 13:42 schrieb Julian Gilbey: > [...] > > I can confirm that something like this is still happening with > > network-manager 1.46.0-1 (Debian testing machine), when using > > network-manager-strongswan: before switching on the VPN, > > /etc/resolv.conf reads: > > > > nameserver 192.168.0.1 > > nameserver 0.0.0.0 > > If that is really /etc/resolv.conf verbatim, it means it was not created by > NetworkManager. Which somehow suggests you use another network management > tool besides NetworkManager. > A mix and match is not a good idea and as far as I'm concerned, > unsupportable.
Hi Michael, Ah, you've probably just solved my problem - thank you! I had no idea that there was another network management tool involved. A quick look suggests that it's ifupdown, so I'll try removing that and see what happens. Best wishes, Julian _______________________________________________ Pkg-utopia-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
