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
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