similar to: Tinc1.1 generates Port automatically when port is occupied

> The goal is to create a working setup as easily as possible. > This is going fairly well with 1.1 ;-) thank you. > - if people are able to read it, you can just as well leave it to a > warning > > and suggest running again with a --autoport flag to enable automatic port > > generation > > I'm sure I will get some emails from people complaining that if tinc

On Mon, Feb 02, 2015 at 07:46:11PM +0100, Eric Feliksik wrote: > I like the config generator of tinc 1.1! An issue to consider on the > default behavior: > > It turns out 'tinc -n mynet init mynodename' makes up a default Port=... > when the standard port is taken: > "Warning: could not bind to port 655. Tinc will instead listen on port > 22911". The goal

Hi, I have been working with tinc network where one host will provide the IP addresses over DHCP to each connected node. Tinc runs in switch mode. It seems that the HWaddr of the tinc interface is regenerated every time when tinc is (re)started. As a result, DHCP server will assign a new IP for the host. Is there any configuration variable we could use to avoid HWaddr changing? Currently, I

c:\APPS\TINC\tincd.exe --mlock --net=mynet --config=C:\APPS\tinc\mynet Without --mlock, the service starts OK. With --mlock, the service fails to start.

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

You might want to try with https://github.com/gsliepen/tinc/pull/120 - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

I have the habit of putting the name of the host within the host file as a comment usually on the first line. Helps when files are renamed and tracking. The new version exports Name = victor and so the old comment style is not necessary. I would think the new version should still simply ignore lines that begin with the '#' character. For example, a normal host file named victor that

Dear all, I have been successfully running for quite some time a tinc 1.1 network in switch mode. I recently added a new node, that refuses to communicate over UDP. Running "tinc info mynode" from a different box returns: Reachability: directly with TCP It appears that tincd is not listening on UDP port 655 on "mynode". Running "ss -nlptu | grep tincd": tcp

Hi Maxim, I'm having the same result, though I got some more output with debug level 5; it's definitely failing to create the specified tincdev0 network device. Is there something I need to change on OS X to enable that? See: $ sudo tincd -D -c /etc/tinc/robotvpn -d tincd 1.0.26 (Nov 2 2015 06:12:50) starting, debug level 1 /dev/tap0 is a Generic BSD tap device ifconfig: interface

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

i have a switched and bridged tincd node with two addresses, each with a different port. Address = 37.70.156.168 28655 Address = 192.168.2.228 655 i was having trouble reliably connecting to it / thru it and noticed that a log from a remote tincd node indicated it may have mixed up the ports. It doesn't appear to use the 28655 port that would be needed for remote access. Before i

Hi Maxim, Not much to it: avahi-autoipd -D $INTERFACE # ifconfig $INTERFACE 169.254.45.23 netmask 255.255.0.0 up ip route add 172.20.0.0/16 dev $INTERFACE Mac OS X doesn't have "ip" by default, so I also installed the Homebrew package "iproute2mac", which provides an emulation of "ip" on top of the legacy ifconfig/route calls. The commented-out ifconfig

Tinc newbie here so apologies if this is obvious or has been discussed already; I did search but couldn't find anything. I'm testing tinc 1.1pre10 between a Windows 7 client and Linux server. The Linux machine is on the internet and the Windows machine is on my home network behind NAT. I have successfully configured a Linux client on my home network to communicate with the server

> kextload /Library/Extensions/tun.kext/ I didn't have a /Library/Extensions/tun.kext/ on my machine. I googled around, and downloaded and installed from http://tuntaposx.sourceforge.net/. Not sure why the macports install didn't work, but it seems I'm making progress. Now I get this: > sudo tincd -n dpsf -D -d3 tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3

Suppose tinc is installed on 100 routers in 100 sites. How to automate site-site vpn management across 100 sites? Some kind of vpn management solution? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180329/90f0198d/attachment.html>

Hello to all i have set up two tincd as mentioned on this site: http://mia.ece.uic.edu/~papers/volans/tincd.html but all i get on the client side is: [ root@mondhexe ]: # tail -f /var/log/tinc.log Trying to connect to naturstrom (80.132.178.186 port 655) Timeout from naturstrom (80.132.178.186 port 655) during authentication Closing connection with naturstrom (80.132.178.186 port 655) Trying to

Hey all, I'm trying to use tinc 1.0.26 from Homebrew on Mac OS X 10.10.5, and having some trouble. Is anyone successfully doing this? Here's my config: $ sudo cat /etc/tinc/robotvpn/tinc.conf Name = elendur Mode = switch AddressFamily = ipv4 Interface = tincdev0 Compression = 1 ConnectTo = robot_ph_cpe22_04 And here's the invocation: $ sudo tincd -D -c /etc/tinc/robotvpn -d tincd

Just search online why in general that is insecure via CLI vs programmatic for first class automation.. there is a reason why snmp, rest, ... exist. On Thu, Mar 29, 2018 at 3:50 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > You've mentioned security issues in your previous email, but now you're > hopping to management issues. > > Have you tried Ansible, Chef or

Hello, >From what I see with my current tinc setup, to add a new node to the network, I need to generate a certificate and exchange it with at least one already-connected (let's call it "known") node. I can easily give the known node's certs to other clients, but getting other nodes' certificates into the known node's config is non-trivial. Is there a way to join the