On 9/29/23 20:58, Ranjan Maitra wrote:
Thanks!
On 9/28/23 19:03, Ranjan Maitra wrote:
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
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.
Btw, can I know more about this script? Though it would be nice not to have to
run anything as it just a week ago.
I don't know why it would have changed recently and I also don't have
anything on the global setting.
My script has:
resolvectl dns tun0 <vpn dns ip>
resolvectl default-route tun0 false
resolvectl domain tun0 <domains to resolve on vpn>
You probably need something more to remove the global settings as well.
Is this a bug that should be reported? Against what? The reason I hesitate is
because Cisco SecureClient VPN (a closed source proprietary application) is
involved.
And that's the only thing that could be doing it, so I don't think
there's much point in filing a bug. I'm curious how it's doing that though.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
