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.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
