search for: hoersken

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

...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: > > Error getting read result from Windows tap device > {F30C422F-4524-435F-A15B-71A7E08C260D}: (99...

...iptables in Linux seem quite complicated as well, messing with the network stack. I've seen a few tinc docker images that run tinc as a container - I haven't tried this. Please let us know if you do actually get it working - im very interested to know. Mike On 20 May 2018 12:55 am, 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: Error getting read result from Windows tap device {F30C422F-4524-435F-A15B-71A7E08C260D}: (995) The I/O operation has been abo...

Hi Etienne, Am 20.05.2018 um 10:58 schrieb Etienne Dechamps: > Hi Marc, > > A number of bugs have been found and fixed in the code that deals with > Windows devices in tinc 1.1: > > https://github.com/gsliepen/tinc/pull/169 > https://github.com/gsliepen/tinc/pull/173 > https://github.com/gsliepen/tinc/pull/174 > https://github.com/gsliepen/tinc/pull/181 >