Timeline for Bypass PIA VPN on Hyper-V
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2023 at 16:06 | comment | added | Tom Yan | Adding to my comment above, the only option you have is probably using an "external" switch instead (i.e., bridge your VM to your LAN). If that for some reason is not acceptable / feasible, then you should give up. (Your gut about "excluding the virtual adapter" makes more sense than the discussion about "process". If you really want to dig deeper, research on whether Windows has unlikely introduced policy routing and multiple route tables in its recent versions / builds. IMHO even that is less wasteful of time.) | |
| Dec 5, 2023 at 16:02 | comment | added | music2myear | @harrymc does that actually remove WindowsTerminal.exe, or just change the default? This probably isn't relevant, but OPs statement that they don't have it installed makes me wonder. | |
| Dec 5, 2023 at 15:31 | comment | added | harrymc | @music2myear: The poster might have set Settings > System > For developers > Terminal to "Windows Console Host". | |
| Dec 5, 2023 at 15:20 | comment | added | music2myear | Could you explain how you've removed/prevented the installation of WindowsTerminal.exe? That is a core function of Windows now, and how you've modified your system may be relevant to finding the correct answer to this problem you're facing. | |
| Dec 5, 2023 at 15:07 | comment | added | harrymc | You may exclude whatever is the executable. If unsure, get Process Explorer and drag the bullseye icon over the window. | |
| Dec 5, 2023 at 15:01 | history | edited | rettiseert | CC BY-SA 4.0 |
deleted 7 characters in body
|
| Dec 5, 2023 at 15:00 | comment | added | rettiseert | @harrymc I don't have Windows Terminal installed so WindowsTerminal.exe is not present in my machine. | |
| Dec 4, 2023 at 15:51 | comment | added | Tom Yan |
"Split tunnel" feature that allows me to select an application The problem is, traffics from VMs do not originate from a (local) "application" (unless the hypervisor provide the connectivity with something like "userspace NAT", which is not the case of Hyper-V or WSL). Network stack level IP forwarding is what is involved behind the scene. What you need would be alternate routing for some/all forwarded traffics. It is feasible in Linux. Not so sure about Windows.
|
|
| Dec 4, 2023 at 15:39 | comment | added | harrymc |
WSL instances run under WindowsTerminal.exe, so you may try to exclude it, then run the WSL distribution.
|
|
| Dec 4, 2023 at 12:54 | history | edited | rettiseert | CC BY-SA 4.0 |
deleted 3 characters in body
|
| S Dec 4, 2023 at 12:53 | review | First questions | |||
| Dec 4, 2023 at 12:54 | |||||
| S Dec 4, 2023 at 12:53 | history | asked | rettiseert | CC BY-SA 4.0 |