NAT connections STUN etc

[Raimund Sacherer]

----- Original Message ----- 

> From: "Chris Clarke" <chris at listerthrawn.co.uk>
> To: tinc at tinc-vpn.org
> Sent: Monday, August 10, 2015 6:56:56 PM
> Subject: NAT connections STUN etc

> Hi all,

> Love tinc by the way. It's a great VPN.

> I'm having issues with 2 nodes always talking through an intermediate
> node. My set up is a VPS in a cloud somewhere that's running tinc and 2
> other nodes - one a roaming laptop (always NAT'd) and the other a server
> behind a dynamic IP home broadband connection (Not NAT'd but
> firewalled). Neither the laptop nor the home server have any firewall
> rules that accept incoming traffic for tinc.

> They can all talk to each other, but it always routes the traffic via
> the VPS which does have incoming traffic allowed.

> What method should tinc be using to create a direct link between them
> and what may be preventing it from working? Is it UDP hole punching via
> the connection they do have with each other through the intermediate
> node?

> I'm running the latest stable version 1.0.26

> Look forward to your ideas.
Hi, 

Without digging any further, did you try to activate the IndirectData config option, not sure if it will help you or if your problem is NAT related ...:

IndirectData = <yes|no> (no)
This option specifies whether other tinc daemons besides the one you specified with ConnectTo can make a direct connection to you. This is especially useful if you are behind a firewall and it is impossible to make a connection from the outside to your tinc daemon. Otherwise, it is best to leave this option out or set it to no.

Best
Ray
--