Hi Jason, Thank you for your prompt response.
We are trying to use wgctrl way of configuring the wireguard devices and facing issues while creating/configuring the wireguard device on windows. 1) First problem was while creating the wintun device using wintun.dll and using wgctrl for configuring it. It hangs in wgclient.ConfigureDevice api() 2) So tried to first create the device through wireguard.exe. And then used wgctrl way to configure it, but wgClient.Devices() is not able to get the devices on our test windows boxes (even though it works on my development machine) So was trying to investigate how wireguard works on windows. With wgctrl package I was able to get it working on linux/mac, but facing such issues on windows. The reason for using wgctrl was to make it configurable through our own APP. Regard, Dev On Thu, Feb 25, 2021 at 7:54 AM Jason A. Donenfeld <[email protected]> wrote: > > I'm curious to learn what you're trying to debug this way; you're > better off using wireguard-windows. > > The pipe permissions are too strict internally, it appears. Try > running as Local System. > > Jason
