similar to: Windows TAP driver issues

Hi Todd, I did some tests with NDIS 6 TAP-Windows about three years ago. The outcome of that was https://github.com/gsliepen/tinc/pull/73/commits/ 0c010ff9fe50b4046b5c7977bafac3e74037f075 It was a long time ago and I don't remember the details, but I remember I was quite confused because I couldn't explain why OpenVPN did not seem to exhibit any performance issues on the same driver,

Thanks for the info, that is very helpful. It does look like that change got back-ported to master, albeit in a different form. I'll take a look at how OpenVPN does its windows device I/O. - todd

Thank you very much. I can confirm that the TAP-WIN32 driver behaves differently. The quick tests so far revealed that it either reconnected after Standby and Hibernation. I think that at some point I started using the OpenVPN drivers when I had either had trouble with unsigned drivers or the network detection and then just stayed with it. Thanks for pointing out my self-made problem. On

Etienne Dechamps <etienne at ...> writes: > > You should mention your tinc version and the version of the > "TAP-Windows Adapter V9" driver for the virtual network device you're > using (i.e. the contents of "Driver version" as seen in the Device > Manager). > > On Mon, Dec 15, 2014 at 10:04 PM, Adam Del Vecchio <adam at ...> wrote: >

On Mon, 22 Jan 2018 18:08:22 +0100, Guus Sliepen wrote: > Thanks for reporting this bug! Indeed, that code is wrong. It should > free cache->ai instead of cache->aip. Even if it didn't crash on Linux, > it was a memory leak. A fix is now in the git repository. The fix leads to a use after free bug which is visible on macOS. It doesn't seem to be much of a problem on most

Hello tincers, I was recently trying to add a new Windows client to my tinc network and ran into an interesting error; upon starting tinc I am met with the usual successful startup (debug level 0; detects TAP device; Ready), however it appears that any writes/reads from the TAP device fail with: "Error while writing to Windows tap device <device ID truncated>: (997) Overlapped I/O

On Windows, freeaddrinfo(NULL) will result in a segv. In get_recent_address(), there is the following block of code: if(cache->aip) { sockaddr_t *sa = (sockaddr_t *)cache->aip->ai_addr; cache->aip = cache->aip->ai_next; if(!cache->aip) { freeaddrinfo(cache->aip);

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

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

A heads up: very soon the code base of tinc will be reformatted using Artistic Style. I've already pushed the .astylerc to the master and 1.1 branches, including a Makefile rule so you can run "make astyle" from the top directory and have all source files automatically formatted. The .astylerc reflects the current code style of tinc, but with the following important changes: -

Hello Community, I'm using tinc a while, but now it's the first time i have to install it on my first windows 10 client... bah, i hate windows 10, but anyway... so i just got the latest stable version of tinc and installed it the usual way - so far no problem... tap virtual adapter is present and configured, tinc config is the same as usual, so i just started the daemon... and it

Hello, I successfully set up a tunnel with tinc using the tun interface. however I need a tap device, because I need to run the OLSR routing protocol on the tunnel and if I use the tun mode OLSR will just skip the interface. (It is a well known thing, I had this issue before also when using OpenVPN in the past). The problem is that I cannot make tinc use a tap device. I created the tap0

Hello, I've been experimenting with tinc to get to know it and I got to point where the tinc service wouldn't start anymore. Starting with debug options gave me a ".. not a usable Windows TAP Device.. File not found" report. After a lengthy period of digging, I discovered that my registry was littered with connection bindings for all the previous install/uninstall's

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

yes, ip_forward was turned on. iptables is defaulted to ACCEPT policy on all the 3 chains. On Sat, May 14, 2016 at 1:24 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote: > > > I have a Debian 8 64-bit machine set up as a server and apt-got the tinc > > package. I configured tinc as a bridge and everything seems

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

Hi, I had some performance problems with TINC running on Windows XP. I had a VPN tunnel running over a wireless network to a Linux VPN server. Web browsing through the tunnel was a pain. Big web pages with lots of pictures loaded very slow compared to a plain network connection. When the VPN client was running on a Linux computer, and a Windows computer was browsing the web through the VPN