Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split Tunnel rules sometimes do not apply properly after hibernation #54

Open
std-move opened this issue Mar 25, 2023 · 1 comment
Open

Comments

@std-move
Copy link

Describe the bug
Sometimes, after waking up from hibernation, Split Tunnel rules aren't applied properly.

My split tunnel is set to bypass VPN by default, with selected applications that should use the VPN.

For instance, I got 2 Firefox installations - with one excluded (implicitly) and one set to only VPN. However, it can happen that the excluded Firefox (the one that should bypass the VPN as its installation path exe is not configured in PIA) connects via the VPN anyway after I wake up from hibernation.

I found out about this due to a site I was logged onto saying my IP was blacklisted and subsequently verifying that the VPN connection was used in my excluded Firefox. There might be a race condition of some sort, perhaps?

Connection protocol used: Wireguard
DNS split mode: Follow app rules

To Reproduce
The issue seems intermittent, it happens most often after waking up from hibernating.

Expected behavior
Excluded applications should never connect via the VPN.

Observed on:
Windows 10 22H2 x64, PIA Client 3.3.1
2 independent PCs, one laptop, one desktop

@banister
Copy link

Thanks for the report, we'll attempt to reproduce and see if we can traige this for future work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants