Re: [Openvpn-devel] Viscosity patch to TAP driver (was: Summary of the community meeting) 2018)

Hi, On Thu, Apr 12, 2018 at 10:50 AM, Gert Doering wrote: > Hi, > > On Thu, Apr 12, 2018 at 10:27:08AM -0400, Selva Nair wrote: > > > > This change was made not because of any actual performance gains, but > > > > because of user reports that certain firewall or AV software

Re: [Openvpn-devel] Viscosity patch to TAP driver (was: Summary of the community meeting) 2018)

Hi, On Thu, Apr 12, 2018 at 10:27:08AM -0400, Selva Nair wrote: > > > This change was made not because of any actual performance gains, but > > > because of user reports that certain firewall or AV software tries to > > > QoS the adapter based on its reported adapter speed, which is of course > >

Re: [Openvpn-devel] Viscosity patch to TAP driver (was: Summary of the community meeting) 2018)

Hi, On Thu, Apr 12, 2018 at 4:26 AM, Gert Doering wrote: > Hi Eric, > > On Thu, Mar 22, 2018 at 02:25:56PM +1100, Eric Thorpe wrote: > > One of the Viscosity developers here. The TAP driver used by Viscosity > > is based on the OpenVPN TAP-Windows driver. We're surprised to

Re: [Openvpn-devel] Viscosity patch to TAP driver (was: Summary of the community meeting) 2018)

Hi Eric, On Thu, Mar 22, 2018 at 02:25:56PM +1100, Eric Thorpe wrote: > One of the Viscosity developers here. The TAP driver used by Viscosity > is based on the OpenVPN TAP-Windows driver. We're surprised to hear of > any performance differences, as the changes we've made are very minimal. > >