Re: [Openvpn-devel] Preliminary Wintun support in OpenVPN2

2019-06-13 Thread Lev Stipakov
For the record - it seems that TransmitPackets is a Windows equivalent of sendmmsg which sends each passed buffer in its own UDP datagram, I have created a test project to understand better how it works, https://github.com/lstipakov/TransmitPackets/blob/master/TransmitPackets.cpp , will try at som

Re: [Openvpn-devel] Preliminary Wintun support in OpenVPN2

2019-06-12 Thread Lev Stipakov
> WSASend / WSASendTo methods, which we use to write to link on Windows, > already support multiple buffers (but we do not use that feature): > Argh, turns out that WSASend combines multiple buffers (openvpn packets) into single UDP packet, which doesn't work for openvpn - we expect UDP packet to

Re: [Openvpn-devel] Preliminary Wintun support in OpenVPN2

2019-06-12 Thread Lev Stipakov
Hi, Agree. This is the first thought I had when I heard about "you must > have privileges to access wintun" - just use our existing privilege > handling mechanism. I have no idea how to actually *do* that (= pass > a handle to wintun over our service pipe), but I'm all willing to > review and te

Re: [Openvpn-devel] Preliminary Wintun support in OpenVPN2

2019-06-11 Thread Gert Doering
Hi, On Tue, Jun 11, 2019 at 05:55:43PM -0400, Selva Nair wrote: > A quick comment: > > IMO, we should use the interactive service to open the pipe and pass > the handle to OpenVPN.exe. This avoids allowing arbitrary users to > access the pipe or requiring users to start OpenVPN as admin which is

Re: [Openvpn-devel] Preliminary Wintun support in OpenVPN2

2019-06-11 Thread Selva Nair
Hi, Copying devel list as there is good info in here.. On Tue, Jun 11, 2019 at 4:24 PM Simon Rozman wrote: > > Hi, > > > > I've taken Jason out of the loop – he's hostile and competitive, and I do not > approve his attitude towards OpenVPN and other nice people trying to use our > technology.