search for: netnames

I did notice the that interface we have named br-lan did not have the proper broadcast and netmask information. I adjusted that and it looks like its now connecting but still running into issues. Here is a snipet from the new system we are trying to connect in (from the /var/log/tinc.log file) 2018-03-15 22:57:26 tinc.NETNAME[871]: Read packet of 74 bytes from Linux tun/tap device (tun mode)

Hi Team, I admit that I am not familiar with Tinc very well, but have Tinc running at approximately 20 sites and functioning as a mesh vpn/network. I am having issues adding an additional site as it will not communicate with the rest. I have taken the firmware of one and flashed it on another router to make it duplicate and then tested it working but when I change the hostname, and IP to what we

Hi all, I am trying to setup a configuration of Tinc to allow multiple tincd daemons for a same network (mixing bonding, etc...). I will post my solution later if I found one. This is to get better speeds in multiple gigabit/sec networks. So my question is not about this directly. I would like to know if the "netname" configured on each node, is used somewhere in communications

I admit that I am not familiar with Tinc very well but see that Tinc is running their current vpn connections. We have a scenario that has 20 different sites currently and successfully using tinc on openwrt but I am having issues adding an additional site as it will not communicate with the rest. I am not the one that originally setup the system but that person is no longer available. I have

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 think this is probably my first post to this mailing list, so hello! Occasionally I log in to my servers from IP addresses without reverse DNS configured, so sometimes I'll see an IP I don't recognise because I can't remember what I did the day before and get a bit spooked until I WHOIS the IP and find the netname reminds me I logged in from that IP. I set out prepared to script

...osts stuffed into a single > /etc/tinc/netname directory. The "netname" does not have to be the same on all nodes of a VPN. It is merely a quick way to tell tinc where its configuration data lives and how to name the VPN interface. So in your self-contained example, use four different netnames. If you don't like this, then you should properly simulate four different machines on a single one, either using containers (like LXC) or full virtualisation (like KVM). -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part ---...

greetings All, I have been reading over the Tinc manual and have become very interested in the "4.2 Multiple Networks" section of the manual. In particular, I am wondering if I read this correctly in that by using: `-n, --net=netname' Use configuration for net netname. then I can have multiple daemons running on the same machine. If I have 3 machines A, B, and C with A being

...xample, would it be better to run each data center on its own class C (Netmask 255.255.0.0) and then the routing commands to allow the local tincd daemon to just send the packets On the self contained example, I planned to run 4 instances of TINC. I could run them in 4 different directories with netnames /tinc1/conf/netname/ /tinc2/conf/netname/ /tinc3/conf/netname/ /tinc4/conf/netname/ Is there a way to run tinc without regard to netnames? /tinc1/tincd --config=/tinc1/conf /tinc2/tincd --config=/tinc2/conf /tinc3/tincd --config=/tinc3/conf /tinc4/tincd --config=/tinc4/conf /tinc1/conf/ /tinc1/...

Hi, Tinc experts I’m on-boarding for Tinc for just quite a few days, and trying to setup the connection between one client to multiple server, where multiple vpn tunnels from the client to different server. From the documentation, it indicate the tinc.conf can support multiple ConnecTo, also the tinc can support multiple netname, like /etc/tinc/net1, /etc/tinc/net2. My question is, for my above

...t3)/ \gw for tenant3—— Internet > On 3 May 2017, at 12:40 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > > On Tue, May 02, 2017 at 08:46:45PM +0800, Bright Zhao wrote: > >> For use case of multi-tenancy use case, should I use multiple netnames (/etc/tinc/tenant1, /etc/tinc/tenant2/, etc.) for the network, so that even different tenant have overlapped network address will be possible to work in the same physical host? or can not? > > If you have multiple netnames, then you can have overlapping network > addresses all you like as...

If you have multiple ConnectTo statements in your tinc.conf, then tinc will attempt to establish connections with *all* of them. It is not a fallback, though it is a good idea for every node to have at least two direct connections for improved resiliency and fault tolerance. As to whether you should have just one tinc network or multiple networks, well, that depends on what you're trying to

Here is some examples of using templates for TINC configurations and settings: In your startup script, BEFORE starting TINC VPN, put a number of entries to configure your VPN: sh ./templatewriter.sh LAN LOSI101 8540 255.255.255.0 0.0.0.0 10.99.0.11 10.98.0.11 ConnectTo=LOSI102 ConnectTo= ConnectTo= **PUT MORE ENTRIES HERE FOR MORE COMPLEX VPN setups ######Templatewriter.sh #!/bin/bash

Hi, How long can the the tinc netname be ? -n, --net=NETNAME Connect to net NETNAME. Perry

That's exactly right. Corollary: if you take one node from a tinc network and connect it to a node from another isolated tinc network, the two networks become one :) On 1 May 2017 at 13:16, Bright Zhao <startryst at gmail.com> wrote: > Hi, Etienne > > Thanks for your clarification, and this helped a lot. And in order to get > a better understanding for the mechanism of Tinc

Hi, Etienne Thanks for your clarification, and this helped a lot. And in order to get a better understanding for the mechanism of Tinc and the purpose of ConnectTo statement, can I think the ConnectTo is the way to get the node into the Tinc VPN domain, instead of establish VPN connection between nodes. Once any node ConnectTo the Tinc VPN domain, it learns all other nodes, subnets, and

Hi list ... I just observed a stange segfault: It seems tinc doesn't like my surname. # tincd -n Sattler -K Segmentation fault I tried several other netnames, there is no problem. The segfault only hap- pens with "Sattler" (capital "S"). I'm using tinc-1.0.22-r2 from Gentoo. Thomas

Hi, I'm having some trouble trying to run tinc over GNU httptunnel. On server A I have: /etc/tinc/netname/tinc-up: #!/bin/sh ifconfig $INTERFACE 10.3.0.1 netmask 255.255.0.0 /usr/bin/hts -F localhost:655 8888 /etc/tinc/netname/hosts/A: Address = foo.com Subnet = 10.3.0.0/24 TCPonly = yes /etc/tinc/netname/hosts/B: ConnectTo = A Subnet = 10.4.0.0/24 TCPonly = yes

systemctl enable tincd at NETNAME systemctl: command not found Please help? Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Mon, Feb 8, 2016 at 7:30 AM, Maxim Vorontsov <6012030 at gmail.com> wrote: > systemctl enable tincd at NETNAME for example > > -- > brgds > Max > On Feb 8, 2016 12:15 AM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: >

On Tue, Jan 27, 2015, Sandy McArthur Jr wrote: > I use the Tinc 1.0 series since I don't want to support my > own packages. <snip> > I wrote most of http://wiki.openwrt.org/doc/howto/vpn.tinc and that is > what I still use. Since then . . . Ok. I think I'll start with the 1.0 series packages that are already out there and get them working. and on Tue, Jan 27, 2015,