similar to: UPnP support in tinc

On 12 November 2015 at 21:29, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Wed, Nov 11, 2015 at 09:04:20PM +0000, Etienne Dechamps wrote: >> According to an online NAT check service, around 50% of NATs in the >> wild have this problem, making this a very real issue: >> http://nattest.net.in.tum.de/results.php > > Are you referring to port restricted NAT in the

On Wed, Nov 11, 2015 at 09:04:20PM +0000, Etienne Dechamps wrote: > 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 [...]. This type of NAT > will stop any UDP hole

fauno <fauno at kiwwwi.com.ar> writes: > Etienne Dechamps <etienne at edechamps.fr> writes: >> (I realize that this means UPnP support could possibly be achieved >> simply by suggesting that the user spawn some standalone UPnP client >> process in the background from the tinc-up hook. That's not very >> user-friendly, though. Especially on Windows.) >

On Thu, Nov 12, 2015 at 10:05:19PM +0000, Etienne Dechamps wrote: > My best guess is that it's simply a direct application of > probabilities: if the probability that a NAT is "compliant" is 70%, > then the probability that *both* NATs at both ends of the tunnel are > "compliant" is only 50% (0.70*0.70). Indeed both NATs need to be > compliant in order for

On Wed, Nov 11, 2015 at 3:04 PM, Etienne Dechamps <etienne at edechamps.fr> wrote: > miniupnpc only provides a blocking API, there is no way to > integrate it into an event loop. That pretty much means we will need > to run the UPnP code in a separate thread. Which means using pthreads > on POSIX, and then we would either have a dependency on pthreads-Win32 > on Windows, or

On 11 November 2015 at 21:57, David Nicol <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

On 13 April 2018 at 19:34, Alex Corcoles <alex at corcoles.net> wrote: > > Note that it would be easier to set up tinc nodes on your Windows > > desktop and Linux laptops, to avoid the additional complication of > > having to relay broadcast packets between your local networks and the > > tinc network. This is what I do in my setup. > > But both systems will

Currently Tinc Pre-release Windows binaries do not come with UPnP support compiled in. I'm not sure what cross-build environment tinc project currently uses to make tinc 1.1 Windows binaries but in MSYS2 it's enough to depends() on miniupnpc library and add --enable-miniupnpc to configure which seems trivial. I've been recompiling tinc with this one change for my project and UPnP

pc1(LANa) ----poor connection ----> VPS <--------- PC2(LANb) pc1 and pc2 used to connected directly with tinc, since pc1 used to have WAN IP(pppoe), but the pppoe IP is not WAN IP anymore (ISP changed to let all ADSL user in a LAN). if I let the two pc connect to a VPS with tinc, can later connections between pc1 and pc2 be directly ? for example, ssh from pc1 to pc2 but not proxyed by

On 12 November 2015 at 01:15, fauno <fauno at kiwwwi.com.ar> wrote: > Etienne Dechamps <etienne at edechamps.fr> writes: >> (I realize that this means UPnP support could possibly be achieved >> simply by suggesting that the user spawn some standalone UPnP client >> process in the background from the tinc-up hook. That's not very >> user-friendly, though.

Has anyone successfully got UPnP and Shorewall working together ? If so, has anyone created documentation on how to get it working ? Thanks in advance, Mark

Etienne Dechamps <etienne at edechamps.fr> writes: > (I realize that this means UPnP support could possibly be achieved > simply by suggesting that the user spawn some standalone UPnP client > process in the background from the tinc-up hook. That's not very > user-friendly, though. Especially on Windows.) something like this :P

Hi all, I am new to Tinc VPN and really would like to make full benefit of this implementation if possible. I would like to know whether I will be able to use Tinc to its full potential. My current setup is as follows, IPfire router/firewall(openvpn client) --->ISP(Internet)--->Amazon VPS(openvpn server). The ipfire router is behind a CARRIER-GRADE NAT, I am able to reach the network

I can confirm that Steam In-Home Streaming does work properly over tinc, for having tried it myself, as long as tinc is configured to route the broadcasts properly, as Guus described. Note that it would be easier to set up tinc nodes on your Windows desktop and Linux laptops, to avoid the additional complication of having to relay broadcast packets between your local networks and the tinc network.

On 10 February 2015 at 09:02, jg <webaccounts173 at jgoettgens.de> wrote: > > >> >> I get an occasional similar problem, we have Mikrotik firewalls and from >> tcpdump monitoring on the asterisk boxes I can see that the firewall >> (unbidden) has changed the IAX port. Usually a firewall reset and sometimes >> PBX reset combination fixes it. >>

Hello, Early this year I got help here to setup tinc tunnels between users and a company LAN. Now I would like to try something different for a home usage and I have a question regarding security. The setup would look like as follows: - My home LAN has a classical topology where my ISP router is doing NAT and is blocking all incoming connection. I'm planning to enable port forwarding on the

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

Hi, I've followed the guide at: http://blogs.operationaldynamics.com/andrew/software/research/using-tinc-vpn and have a working tinc VPN. Here's my topology: - CentralNode has a fixed public IP address that everyone connects to - Leaf1 and Leaf2 may have different IP addresses depending on where they are, and usually those will be behind NAT (think, two laptops going around and you get

Hi all, many thanks for the replies! On 14/05/18 19:05, Parke wrote: > On Mon, May 14, 2018 at 4:44 AM, Keith Whyte <keith at rhizomatica.org> wrote: >> but then I read that no, each host much have the key of >> the other to establish the direct connection. But I am looking at >> tcpdump right now in the terminal and seeing the UDP tunnel packets >> flowing from