Better Thin Client/Netbook Support: UWP + Windows.Networking.Vpn

[TPS]

Issue Details

1 of my devices is a thin client/netbook/whatever they call a "PC w/ very few resources" this decade. I haven't run even AdGuard Windows full client on this device (thought I've available license slots), due to wanting to preserve those resources, but am relying on OS-configured subscription AGDNS + the AG browser extension. So the AGVPN client is comparatively quite a heavy always-on app.

Proposed solution

I'd like a way to access subscription AGVPN through Windows' own Networking VPN settings, since that's already integrated into the OS.

N.B.: I searched these issues looking for a similar request. If such exists, please feel free to close w/ a link to that.

Alternative solution

Maybe just the AGVPN extension? But that leaks everything outside the browser.

In place of original AG, AGDNS + browser extension plugs mostly everything for what I use. I'm looking for a VPN equivalent for that.

[ameshkov]

Well, when we experimented with Windows 10 VPN API many years ago (when mobile Windows was still alive), it was full of bugs and tbh almost unusable. Actually, the point back then was to try a full UWP version of AdGuard (we didn't have a VPN back then). Now MS does not seem to be pushing for UWP apps anymore.

From the performance perspective it does not provide any benefit compared to WinTun, basically the same approach just with a different type of driver routing traffic through the VPN app.

Anyways, let's keep this feature request open and see how many people would like to have it, but I'll rename it to better render what's required.

[TPS]

To be specific, I'm specifically requesting something w/o constantly-running client software (though maybe just a driver/service, depending on how "heavy" though https://github.com/AdguardTeam/AdGuardVPNForWindows/issues/579 would be a major blocker – I'm aware AG itself had/has such a mode, but decided against that on this device), just using Windows internal VPN settings, so I don't think "UWP" is relevant?

[ameshkov]

There are two solutions:

1. Provide a protocol that Windows natively support.
2. Implement a VPN service using Windows.Networking.Vpn, this way we can use AdGuard VPN proto.

The first option is already possible via IPSec/IKEV2 setup. It's a bit tricky as we only advertise it for routers, but anyways. In AdGuard personal account you can add a "router" device and it will show you IPSec/IKEV2 settings for the connection. Use this settings when setting up a native VPN connection on Windows (you'll probably need to Google how to do that).

[TPS]

There are two solutions:

1. Provide a protocol that Windows natively support.

The first option is already possible via IPSec/IKEV2 setup. It's a bit tricky as we only advertise it for routers, but anyways. In AdGuard personal account you can add a "router" device and it will show you IPSec/IKEV2 settings for the connection. Use this settings when setting up a native VPN connection on Windows (you'll probably need to Google how to do that).

I actually tried very hard to get this to work on this device, but it kept erroring out. How best to debug why?

[ameshkov]

That's the problem with this kind of setup, it's very hard to debug it in general:(

Maybe there's something useful in Windows event log?

[TPS]

I've been trying this the last several weekends again, but can find nothing useful in the Event Viewer, nor any troubleshooting steps other than plug-&-chug. 😖