Bug#745103: [Pkg-utopia-maintainers] Bug#745103: Bug#795023: [network-manager] Bricks DNS when disconnecting from a VPN, separately ignores instruction not to use VPN DNS servers
On Thu, Apr 04, 2024 at 10:28:08AM +0200, Michael Biebl wrote: > Am 04.04.24 um 07:21 schrieb Julian Gilbey: > > > 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. > > Don't forget to remove the configuration from /etc/network/interfaces (or > completely remove that file) after uninstalling ifupdown. Thanks; I figured that out after a while ;-) And I'm pleased to say it's all working well now. Best wishes, Julian
Bug#745103: [Pkg-utopia-maintainers] Bug#745103: Bug#795023: [network-manager] Bricks DNS when disconnecting from a VPN, separately ignores instruction not to use VPN DNS servers
Am 04.04.24 um 07:21 schrieb Julian Gilbey: 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. Don't forget to remove the configuration from /etc/network/interfaces (or completely remove that file) after uninstalling ifupdown. Michael OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#745103: [Pkg-utopia-maintainers] Bug#745103: Bug#795023: [network-manager] Bricks DNS when disconnecting from a VPN, separately ignores instruction not to use VPN DNS servers
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
Bug#745103: [Pkg-utopia-maintainers] Bug#745103: Bug#795023: [network-manager] Bricks DNS when disconnecting from a VPN, separately ignores instruction not to use VPN DNS servers
Am 03.04.24 um 13:42 schrieb Julian Gilbey: On Thu, Aug 20, 2015 at 09:20:10PM +0100, OmegaPhil wrote: Package: network-manager Version: 1.0.4-1 I have played around with this some more - the idea with the work VPN connection is not that it takes over everything, but simply that one particular IP address gets routed to it - everything else works as normal. This is why I'm ignoring routes etc, with 'Automatic (VPN) addresses only' used with the intention of not fiddling with the current DNS configuration, which is failing. The workaround is to manually set 'DNS servers' and 'Search domains' to the normal values outside of the VPN, rather than leaving them blank, which Network Manager can't seem to cope with. 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. OpenPGP_signature.asc Description: OpenPGP digital signature
