Launch socat to listen and forward (through binary communication) to a socat (socat cygwin) in windows the tcp calls:
![checkpoint vpn client mtu checkpoint vpn client mtu](https://community.checkpoint.com/legacyfs/online/checkpoint/73170_pastedImage_9.png)
Set your WSL http_proxy env var to point to a socat TCP listening process:
![checkpoint vpn client mtu checkpoint vpn client mtu](https://sc1.checkpoint.com/documents/R76/CP_R76_VPN_AdminGuide/45342.gif)
Just dropping by to say that with socat and a local proxy you can circumvent altogether this problem, at least for http calls: This is not a great workaround, but it is a start. While still on VPN, shutting down WSL2 and restarting it, still worked.
Checkpoint vpn client mtu how to#
Since neither WSL2 VM nor networks devices appear normally in Hyper-V Manager (which only hurts the users, so thanks), I cannot figured out how to use Hyper-V Manager to remove the Switch. WARNING: You should always backup registry keys before you delete them, in case this breaks things! This has worked twice now using Sonicwall VPN, so I hope this works for someone else: Since the one time I got internet working on WSL2 was after an Windows 10 update, I was guessing that maybe somehow the network was reset, it and was because I started WSL2 while on VPN.
![checkpoint vpn client mtu checkpoint vpn client mtu](https://community.checkpoint.com/legacyfs/online/checkpoint/74737_pastedImage_2.png)
Workaround steps to get Internet working on VPN