search for: ndis6

...st the fixes and give feedback regarding the compatibility of tinc-vpn with Docker and Hyper-V VM switches. > I would also suggest you try with the "old" TAP 9.0.0.9 driver (the > one that ships with tinc). In experiments I did about 3 years ago, the > TAP-Win32 9.0.0.21 branch (NDIS6) was not as fast and reliable with > tinc as legacy 9.0.0.9. Before upgrading to TAP 9.21.2 I actually tried the old one that is bundled with tinc-vpn. Unfortunately that caused more errors on Windows Server 1709 and to me it therefore looks like the NDIS6 branch might be more stable on that Wi...

...k detection and then just stayed with it. Thanks for pointing out my self-made problem. On Tue, Aug 23, 2016 at 7:52 PM, Etienne Dechamps <etienne at edechamps.fr> wrote: > You should try using the older TAP-Win32 drivers that are bundled with > tinc (i.e. 9.0.0.9). Using the newer, NDIS6 drivers (>= 9.0.0.21) is not > recommended; according to some testing I did in the past it seems to result > in poor tinc performance (for reasons I wasn't quite able to determine). I > am using tinc 1.1 with 9.0.0.9 on Windows 10 and it behaves correctly when > returning from st...

Hi, I maintain a driver for a 10GbE nic which supports multiple hardware tx/rx rings. We can steer rx packets into rings using the "standard" NDIS6 Toeplitz hashing on TCP port numbers, IP addresses, etc. We can also steer packets based on MAC address. Would this NIC be considered to be capable of supporting crossbow? Also, can crossbow do things like steer outgoing packets to the correct ring (for serialization to prevent out-of-order pack...

Hello everyone, I am running into the following error messages everytime I try to use a docker overlay network on top of tinc-vpn: Error getting read result from Windows tap device {F30C422F-4524-435F-A15B-71A7E08C260D}: (995) The I/O operation has been aborted because of either a thread exit or an application request. Received packet of 106 bytes from ... (... port 655) Writing packet of 106

Hello, I am using tinc for about two years now, and server-side everything is perfect. But on my Windows 10 computer using tinc 1.1 and the OpenVPN TAP Provider 9.0.0.21 I always have to shutdown and restart the tinc service, when the computer returns from standby or hibernation. This problem is not related to the recent Windows updates. I am using Mode = switch ExperimentalProtocol = no

You should try using the older TAP-Win32 drivers that are bundled with tinc (i.e. 9.0.0.9). Using the newer, NDIS6 drivers (>= 9.0.0.21) is not recommended; according to some testing I did in the past it seems to result in poor tinc performance (for reasons I wasn't quite able to determine). I am using tinc 1.1 with 9.0.0.9 on Windows 10 and it behaves correctly when returning from standby. On 23 August...

Hello James, I am doing quite rigorous torture tests with Xen and GPLPV. Let me first repeat the test setup: Use Xen 4.1.1 and kernel 2.6.32.36 (commit ae333e9). Configure 2 HVMs called VM1 and VM2 as follows (per HVM): 2 VCPUs, 2 virtual disks, 1024 MB RAM, viridian=1 Install Windows 2008 R2 SP1, do install everything twice - never clone. Install GPLPV, iometer 2006.07.27, prime95 26.6 x64,

...do, I suspect you will observe improvements. Perhaps Guus might be inclined to cut a release so that people can try them. I would also suggest you try with the "old" TAP 9.0.0.9 driver (the one that ships with tinc). In experiments I did about 3 years ago, the TAP-Win32 9.0.0.21 branch (NDIS6) was not as fast and reliable with tinc as legacy 9.0.0.9. On 19 May 2018 at 11:26, Marc Hoersken <info at marc-hoersken.de> wrote: > Hello everyone, > > I am running into the following error messages everytime I try to use a > docker overlay network on top of tinc-vpn: > >...