Problems with Windows client over PulseSecure VPN
Peter Whisker
peter.whisker at gmail.com
Thu Mar 4 09:11:12 UTC 2021
Hi Jason
Yes, that PostUp line does solve the problem. Thanks! Four tunnels up
and working with two of them via the PulseSecure VPN. :)
Can I ask why you have the section bind code in there when it seems to
work fine without it?
Regards
Peter
On 03/03/2021 10:54, Jason A. Donenfeld wrote:
> Hey Peter,
>
> I had a strange idea for how to fix this without requiring
> recompilation or removal of that code.
>
> 1) Enable DangerousScriptExecution:
> https://git.zx2c4.com/wireguard-windows/about/docs/adminregistry.md#hklmsoftwarewireguarddangerousscriptexecution
>
> 2) Add a PostUp line to your [Interface] section:
>
> PostUp = wg set %WIREGUARD_TUNNEL_NAME% listen-port 0
>
> 3) Try it and tell me if it works?
>
> Regards,
> Jason
More information about the WireGuard
mailing list