search for: aa365152

...rt, making these new > dependencies less of a concern. > it is entirely possible to write code that uses threads on Win32 and forks on POSIX by abstracting the communication bits generically. Signalling could work over pipes on both. https://msdn.microsoft.com/en-us/library/windows/desktop/aa365152(v=vs.85).aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20151111/3cf3e7d7/attachment.html>

Hi Guus, Unfortunately, I often notice that even with the advanced UDP hole punching mechanisms that tinc uses, I still come across cases on my network where two nodes behind NATs cannot talk to each other because one of the nodes is behind a "strict" NAT that won't use consistent source ports for UDP packets that are sent to different destination addresses. More formally, this

...l <davidnicol at gmail.com> wrote: > it is entirely possible to write code that uses threads on Win32 and forks > on POSIX by abstracting the communication bits generically. Signalling could > work over pipes on both. > > https://msdn.microsoft.com/en-us/library/windows/desktop/aa365152(v=vs.85).aspx Hum... yes of course, but I don't see how that addresses my concern. My point was, we either need to do something different between Win32 and POSIX (whether that implies different thread APIs or different process models is besides the point), which means we'll end up with #i...