similar to: Release plans for 1.1?

Hello folks, for monitoring purposes I need to query the network status in order to get all a list of all "online" nodes (that are connected to the network right now). How can I do so? Thanks in advance, Keep smiling yanosz

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

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case

Hello, At OHM2013 (https://ohm2013.org/site/), there will be a lightning talk about tinc, and a workshop setting up tinc VPNs at the Milliways village. An exact time is not known yet but will follow later. OHM2013 will take place from July 31 to August 4 at the Geestmerambacht festival grounds, near Alkmaar, in the Netherlands. If you would like to meet at OHM2013 with other people using or

Hello, At OHM2013 (https://ohm2013.org/site/), there will be a lightning talk about tinc, and a workshop setting up tinc VPNs at the Milliways village. An exact time is not known yet but will follow later. OHM2013 will take place from July 31 to August 4 at the Geestmerambacht festival grounds, near Alkmaar, in the Netherlands. If you would like to meet at OHM2013 with other people using or

> > Maybe I should allow the reachable keyword for the dump graph command as > well, so you can do: > > tincctl -n <netname> dump reachable graph > > ...and not see any nodes which are unreachable. Is that what you want? This would help since dead nodes do not clutter the visual representation. What are the effects, if any, of dead nodes in the hosts/ dir? Thanks

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

Hello, http://www.tinc-vpn.org/examples/redirect-gateway/ explains how to set up a default route using tinc. However, in my understanding tinc's p2p traffic is routed via tinc there: Assume a network: Client A, Client B and a Server S. A and B have "ConnectTo S" in their config, S is used as a gateway providing 0.0.0.0/0 . All packets send from A to B will be delivered to

Hello folks, we're planning an IPv6-Deployment using tinc. A routed tinc-network should connect a couple of wireless access points. In order to avoiding scaling issues, the network should not be run in switched mode. Our site uses 2001:470:780f::/56 - Each ap gets a single /64 network, to be distributed to its wireless clients. Example: ap 1: 2001:470:780f:1::/64 ap 2:

*You should repeat this for all nodes you ConnectTo, or which ConnectTo you. However, remember that you do not need to ConnectTo all nodes in the VPN; it is only necessary to create one or a few meta-connections, after the connections are made tinc will learn about all the other nodes in the VPN, and will automatically make other connections as necessary. * The above is from the docs. Assuming

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

For my opinion, special function not needed, because at first time, oai set to NULL, freeaddrinfo tried to free each ai, until occurance of ai_next == NULL. But it works. Linux, Windows, coordinator with white IP, other nodes behind NAT's (1 or two NAT's, only direct connections allowed). There are some problems with MinGW make, at least - mingw-64 from Fedora 25. 1. No definition for

Hi, I use tinc-vpn to create private mesh vpn networks between office and house in different locations and it works really well. But somehow I'm considering if there were any possibility to add radius support for single node traffic management. I does think it will be really difficult to implement such functions as a feature of a mesh network,because all of the traffic was initiated end to

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.

I cant restart my tincd with 'tincctl restart -n $NETNAME' I get the message: 'Could not restart tinc daemon' It works with 'tincctl stop -n NETNAME && tincctl start -n NETNAME' but sometimes the /var/run/tinc.$NETNAME.pid file is missing so I need to kill tinc manually

Only the short -b option is missing, --batch works as expected. - todd diff --git a/src/tincctl.c b/src/tincctl.c index 9eb9a1b..766b769 100644 --- a/src/tincctl.c +++ b/src/tincctl.c @@ -168,7 +168,7 @@ static bool parse_options(int argc, char **argv) { int r; int option_index = 0; - while((r = getopt_long(argc, argv, "+c:n:", long_options, &option_index)) != EOF) { +

There are at least three cases: * Linux: check credentials and pid from client; restrict permissions from server * BSD: check credentials only from client; restrict permissions from server * Solaris: wide open --- configure.in | 4 ++-- src/control.c | 11 ++++++++++- src/control_common.h | 1 + src/tincctl.c | 38 ++++++++++++++++++++++++++++++++++---- 4

As part of the work on C++17, WG21 released a series of "Technical Specifications", (TS) which added proposed new features to the standard library. These were all defined in the namespace 'std::experimental' (and namespaces inside of that). Then, much of these features were merged into the main standard, and became part of namespace 'std'. Libc++ now has two

This approach is more complex than I'd like, but it works even on Solaris, which has neither credential passing nor permissions on the socket itself. --- src/control.c | 82 +++++++++++++++++++++++++++++++++++++++----------- src/control_common.h | 1 + src/tincctl.c | 67 +++++++++++++++++++++++++++++++++-------- src/tincd.c | 2 +- 4 files changed, 120