similar to: BindToAddress: TCP connections originate from random source address.

Hello, First of all thank you very much for Tinc. I have been using 1.0.24 under Debian & Alpine Linux 32 bit using 'BindToAddress' in tinc.conf without any issues to bind to an IPv6 ULA Address. With 1.1pre10 'BindToAddress' in tinc.conf on the client machines fails with: ============================================================================== tincd 1.1pre10 (Jun

Hi, thank you very much for reporting this! Sounds like a bug in the exec plugin – it never ceases to amaze me how many issues a single plugin can have ;) > > > This means that any plugin that does the usual pattern of: > > > > > > pid = fork (); Note that the exec plugin is the *only* plugin that does this. All other plugins are forbidden to fork(), popen() or

Hi, when building with the WITH_DEV conditional, either `libupsclient.pc' *or* `libupsclient-config' is installed. This is annoying when linking with libupsclient, because you basically have to do the check twice, once using `pkg-config' and once using `libupsclient-config'. Please consider the attached patch, which changes the behavior of `lib/Makefile.am' to install

Hi, I see there’re two configuration in tinc: In main configuration: BindToAddress = <address> [<port>] In host configuration: Port = <port> So, let’s say on svr1 /etc/tinc/test/tinc.conf: BindToAddress = ip_addr p1 BindToAddress = ip_addr p2 /etc/tinc/test/hosts/svr1: Port = p1 On the client side c1 /etc/tinc/test/tinc.conf: ConnectTo = svr1 /etc/tinc/test/hosts/svr1:

Hi there, I would need some help with my configuration. I have tried a long time, but did not find my error. Thus I would really appreciate your help. There are three hosts: 1. h181 2. h182: Should ConnectTo h181 3. h183: Should ConnectTo h181 *Files under /etc/tinc/vpn0/hosts* [h181:] Address = 94.130.108.xxx Subnet = 172.16.1.1/32 -----BEGIN RSA PUBLIC KEY----- *** -----END RSA PUBLIC

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/

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 =

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

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

Folks, We have a setup where each mobile node connects with 1 or more tinc instances (over different links) to a central node. tinc is running in switch mode. The link is chosen by setting the IP address on the active link's interface, and the central node sees this after the first packet on the link, and moves the MAC address to a different 'ethernet port' (link). This works really

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

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

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? > > > >

On Tue, May 24, 2016 at 08:17:07AM +0200, Niklaas Baudet von Gersdorff wrote: > I want to serve IPv4 subnets 10.1.0.0/16 (machine A) and 10.2.0.0/16 > (machine B), and IPv6 subnets fd16:dcc0:f4cc:0:0:1::/96 (machine A) and > fd16:dcc0:f4cc:0:0:2::/96 (machine B) respectively. The jails are > connected on lo1. [...] > A $ cat /usr/local/etc/tinc/klaas/tinc-up > ifconfig

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

A quick glance shows that the exec plugin actually is clearing the signal mask: https://github.com/collectd/collectd/blob/master/src/exec.c#L526 Can you give some more context when this problem comes up? Ideally in a Github issue (hint, hint ;). -- Florian octo Forster Hacker in training GnuPG: 0x0C705A15 http://octo.it/

tags 439986 upstream thanks Hi Florian, 2007/8/29, Florian Forster <octo at verplant.org>: > Package: nut-dev > Version: 2.2.0-1 > Severity: minor > > After upgrading from version 2.0.something to version 2.2.0-1 the type > `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for > software that is supposed to work with different versions of this >

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

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