On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
From: Samuel Sieb <samuel(a)sieb.net>
Date: Thu, 28 Sep 2023 10:32:55 -0700
To: users(a)lists.fedoraproject.org
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: F38: systemd-resolved.service oddity
On 9/28/23 05:02, Ranjan Maitra wrote:
> $ resolvectl dns
> Global: [IP addresses associated with my VPN site] {*}
> Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 {**}
> Link 22 (cscotun0):
>
> $ resolvectl domain
> Global: [VPN connection domainname] [ISP]
> Link 2 (enp57s0u2u1u1): [ISP]
> Link 22 (cscotun0):
>
> where [VPN connection] stands for the address that is associated with VPN.
>
> After stopping VPN:
>
> $ resolvectl dns
> Global: [Same as {*}]
> Link 2 (enp57s0u2u1u1): [Same as {**}]
>
> $ resolvectl domain
> Global: [VPN connection domainname] [ISP]
> Link 2 (enp57s0u2u1u1): [ISP]
>
> After $ sudo systemctl restart systemd-resolved.service
>
> $ resolvectl dns
> Global:
> Link 2 (enp57s0u2u1u1): [Same as {**}]
>
> $ resolvectl domain
> Global:
> Link 2 (enp57s0u2u1u1): [ISP]
>
> Seems to me there is something "sticky" about the VPN connection?
The problem is that the VPN is setting its options on the global state
instead of the tunnel where they should be. Normally, when the tunnel goes
away, so do the special settings for it, but here they're global, so they
don't. I use a VPN at work and I have a little script that I run after
connecting that sets the options for me.
Thanks, so what changed in the last week? Is it at the VPN end? I don't see an update
of my client (Cisco SecureClient).
Best wishes,
Ranjan