similar to: Multiple Windows setups

Hi, Thanks to John Wice for helping me with an earlier question. My two PCs behind the same router are still having problems connecting. Would appreciate thoughts on what I?m doing wrong? Router: Port 655 forwarded to 192.168.1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall

Hi - Thanks to Sven-Haegar and Donald, but still having issues setting up with Windows. Machine1 can't ping the VPN address of machine2. Regular IPv4 address for both machines in 192.168.1.xxx range. Router: Forwarding port 655 to 101.102.103.1, UDP and TCP Forwarding port 656 to 101.102.103.2, UDP and TCP Tinc.conf on machine user1 just three lines: Name = vpnuser1 ConnectTo =

Thanks. I played with it some more, and finally got it working. I am willing to write up a detailed how-to, including screen shots, if you guys are interested. Just tell me in what format you want the write-up. Cheers, From: Daniel J. Grinkevich Sent: Wednesday, July 22, 2015 7:26 AM To: tinc at tinc-vpn.org Subject: RE: Please help debug Windows setup Your port forward needs to

On Fri, Dec 12, 2014 at 02:21:08AM -0500, md at rpzdesign.com wrote: > Oops, I got it to work only after putting the WAN on port 656 so it > did not interfere with port 655 for the LAN. You should not need to have two tinc daemons just because you have a WAN and a LAN interface. By default (ie, if you don't specify BindToAddress and/or BindToInterface), tinc listens on all interfaces,

We are testing tinc inside Google Compute within a single region and an external region. Two boxes are created as follows: /etc/tinc/test/tinc_test_1 Subnet = 10.240.0.0/16 Subnet = 10.240.0.4/32 Address = 104.154.59.151 /etc/tinc/test/tinc_test_2 Subnet = 10.240.0.0/16 Subnet = 10.240.0.5/32 Address = 104.197.132.141 /etc/tinc/test/tinc.conf Name = $HOST AddressFamily = ipv4 Interface = tun0

Make sure your router supports nat reflection and has it enabled. On Mon, Jul 13, 2015 at 5:44 PM, Adam Macielinski <adam at macielinski.net> wrote: > Hi, > > > > Thanks to John Wice for helping me with an earlier question. My two PCs > behind the same router are still having problems connecting. Would > appreciate thoughts on what I?m doing wrong? > > > >

Hi Thanks removing the first line "ip tuntap add dev $INTERFACE mode tun" seems to have helped regarding the tun error, however it is not connecting. If I stop the tinc service and then run: root at web3:~# tincd -n gainplus -d -D tincd 1.0.33 starting, debug level 1 /dev/net/tun is a Linux tun/tap device (tun mode) Listening on 10.130.69.123 port 655 Ready Trying to connect to

Hello Lars, Thanks for your feedback. Unfortunately I made an error in writing the network I expected to connect to. I meant 10.3.0.0/24 The one I wrote in fact was one network of the already established VPN. I have included full details of my relevant files below. Background: I am trying to set up a second VPN between two servers: gtdb and db2. Both servers are already part of separate

Hi, I've stumbled upon a problem which I can't solve easily with the available options in tinc - at least as far as I see. If enlightenment is all I need, I'll happily accept pointers ;) I try to establish a connection between two hosts. Each host has multiple addresses assigned to it's internet interface. A stripped down list would be: Host 1: 2001:780:0:1e::1

Is it possible to use different port numbers for UDP and TCP? I'd like to open the TCP connection to one port on the remote server and stream the UDP packets to a different port. I've tried specifying both as BindToAddress and Address lines but it always just uses TCP. On 2 May 2017 17:36, "Guus Sliepen" <guus at tinc-vpn.org> wrote: On Tue, May 02, 2017 at 09:53:15PM

No parameters using DNS. - tinc.conf content Name = sito1 AddressFamily = ipv4 BindToAddress = <IPPUB>:665 BindToInterface = int Device=/dev/net/tun Interface = vpndrif Mode = router PingInterval = 60 PingTimeout = 5 ProcessPriority = normal - host/sito1 content Address = <IPPUB>:665 Subnet = <IPLOCAL>/<NETMASK> Port = 655 -----BEGIN RSA PUBLIC KEY----- ... -----END

It's down to corporate firewall rules I can't control. I've tried tricking it like you suggested but it didn't work. I guess iptables is the next port if call. It might be a useful addition to tinc. Thanks Petdf On 2 May 2017 17:50, "Guus Sliepen" <guus at tinc-vpn.org> wrote: > On Tue, May 02, 2017 at 05:40:40PM +0100, Peter Whisker wrote: > > > Is

Hi, We have a tinc network of about ~200 hosts and in the full mesh configuration we've had a lot of problems with the edge propagation storms taking the entire network down. Recently we had a setup with a small number of "hubs" to which all the other nodes connected to, which limited the number of meta connections, but that didn't help much with the edge propagation issues.

Hi, I am using tinc 1.0.23 in router mode and am having trouble with intermittent TCP connect timeouts that do not occur when routing the TCP over the internet directly. I am using a pure IPv6 setup (i.e direct IPv6 connections, and tunneled IPv6 subnets). My configs are as follows: Site 1: ----------------------- tinc.conf: Name = rsukmhb AddressFamily = ipv6 BindToAddress =

First off, thanks to all who have made tinc possible and continue to work developing it. I hope perhaps in time I can become a useful part of this community. :) I'm having an interesting issue with tincctl and was hoping someone could shed some light on it. Everything seems to work correctly when I build for OSX; however on linux and windows builds, I always receive connection

Albi Rebmann wrote: > Hallo, > > sorry to say again, but BindToInterface = interface [experimental] still > does not work here (tinc 1.08). I use SuSE Linux 8.0, 2.4 Kernel. > If I add a missing device I get an error, but I add ppp2 (my external > device) and tinc still listens on 0.0.0.0 > I hope you have an idea how I can bind tinc to only one ip address. Use

Hi I'm trying to implement a scheme in which the nodes will have a direct UDP tunnel to each other. First, all nodes make connection with one public node, and then make connections with each other. And I came across the following problem: Remotely located nodes can establish a direct UDP connection, but the nodes that are in the same local network can not, and all traffic goes through the

With pleasure we announce the release of tinc version 1.1pre10. Here is a summary of the changes: * Added a benchmark tool (sptps_speed) for the new protocol. * Fixed a crash when using Name = $HOST while $HOST is not set. * Use AES-256-GCM for the new protocol. * Updated support for Solaris. * Allow running tincd without a private ECDSA key present when ExperimentalProtocol is not

With pleasure we announce the release of tinc version 1.1pre10. Here is a summary of the changes: * Added a benchmark tool (sptps_speed) for the new protocol. * Fixed a crash when using Name = $HOST while $HOST is not set. * Use AES-256-GCM for the new protocol. * Updated support for Solaris. * Allow running tincd without a private ECDSA key present when ExperimentalProtocol is not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gus & Tinc-VPN List: It looks like I need to run 2 instances of tincd on each server. 1 instance of tincd will responsible for running a VPN over the LAN on eth1. This means Class C addresses from 10.0.1.10 -> 10.0.1.250 Another instance of tincd will be responsible for running a VPN over the WAN on eth0. This means Class C addresses from