similar to: Different UDP and TCP ports?

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, Guus I did some test regarding the points you mentioned below, and yes, you’re right, but some of points may need further adjusted: 1. The destination of IPv4 wouldn’t be changed, Yes I agree, that’s the goal and final destination for the communication. But during the path, it may be encapsulated into another packet(tunnel mode), where the outside IP header is the physical address, but the

Sure, let me reply all here for my finding. @Lars @Guus A’s tinc.conf: Name = bright AddressFamily = ipv4 ConnectTo = aly_hk A’s tinc-up: #!/bin/sh ifconfig $INTERFACE 10.0.0.110 netmask 255.255.255.0 A’s host config: Subnet = 10.0.0.110/32 (VPN address) Subnet = 192.168.31.0/24 (LAN address) IndirectData = yes (enabled for every tinc nodes) The node aly_hk (vpn address 10.0.0.3) connects with

On Tue, May 02, 2017 at 09:53:15PM +0800, Bright Zhao wrote: > When tinc daemon get up on A(together with some manual scripts for destination to 8.8.8.8), the route table looks like below: > 10.0.0.0/24 dev tun0 > 10.0.0.3 dev tun0 > 8.8.8.8 via 10.0.0.3 dev tun0 IPv4 packets have only two addresses in their header: the source and the destination address. If you want to send a packet

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

On Tue, May 02, 2017 at 05:40:40PM +0100, Peter Whisker wrote: > 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. It's not directly supported by

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

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

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

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,

I currently am using tinc 1.0.33 on a 4 node Ubuntu 14.04 server network at Digital Ocean connecting on the Eth1 private network interfaces. This works great. Recently I added two more Ubuntu 18.04 servers at the same location and attempted to link them to the Tinc mesh already established. The 18.04 servers do not allow me to use the net-tools ipconfig command and so I have adapted my

On Wed, May 03, 2017 at 02:15:36PM +0800, Bright Zhao wrote: > 1. The destination of IPv4 wouldn’t be changed, Yes I agree, that’s the goal and final destination for the communication. But during the path, it may be encapsulated into another packet(tunnel mode), where the outside IP header is the physical address, but the inner destination remain unchanged, and I think Tinc encapsulates into

Hi Lars, Appreciate all your help, unfortunately the problem remains. I've marked up below: >>> Lars Kruse <lists at sumpfralle.de> 22-May-19 4:02 PM >>> Hello Robert, Am Mon, 20 May 2019 11:11:39 +0700 schrieb "Robert Horgan" <Robert at gainplus.asia>: > These are my files: > > On server 1: db2 > > /etc/tinc/nets.boot > # >

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, Lars Thanks for your suggestion, will give it a try later to see how it performs. But, yesterday, I did a below test: A ConnectTo B and C, B ConnectTo D, C ConnectTo D; All nodes turned "IndirectData" on in its host configuration, so the tunnel only follow metacomnection instead of direct connect. D announced default route by having the Subnet = 0.0.0.0/0 statement in its host

Hello, I already consulted related lists @freebsd.org [1,2] but I have remained unsuccessful to solve the following issue: VPN works for an internal IPv4 subnet, but I doesn't for an internal IPv6 subnet with ULAs. To be honest, I don't have any experience setting up a local IPv6; so I guess that I'm doing something wrong here. For those that know FreeBSD: The main aim is to connect

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 =

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, after trying for days I ended up with a working tinc configurazion of 2 subnets, now my goal is to add 2 more subnets and comunicate. I might seem dumb at this point but honestly I don't work in IT or Networking stuff, and so I dont have that deep knowledge. A little explanation of my configuration is HOST A (VPN server) Public IP: 1.2.3.4 tun0 Subnet = 192.168.10.0/24 tun0 IP =

I have now got the tinc demons (on network OFFICES) on BranchB and BranchA talking to each other, and I have been able to access services (like AFP, Apple file sharing) between the two hosts (in both directions), but not beyond the local network connected to BanchA. I am unclear which routing can be provided by tinc and which routing would I have to add manually. The aim is: BranchB is a