graphviz

[Guus Sliepen]

On Sun, Dec 15, 2013 at 06:37:14PM +0100, folkert wrote:

> I propose that the "ad-hoc connections" (localdiscovery) are also
> displayed in the graph (graphdumpfile) as it is useful for debugging.
> I find the command-line tooling a bit cumbersome to find out where the
> problem is - maybe a web-interface can be added to tincd? Implementing a
> http server is trivial I found out.

Tinc 1.1's CLI should give you a lot of information in an easy way. In
particular, if you want to know all about a single node, you can give this
command:

tinc -n <netname> info <node>

Example output:

Node:         foo
Address:      93.184.216.119 port 655
Online since: 2013-12-05 18:00:00
Status:       validkey visited reachable udp_confirmed
Options:      pmtu_discovery clamp_mss
Protocol:     17.0
Reachability: directly with UDP
PMTU:         1444
Edges:        bar baz quux
Subnets:      192.168.1.0/24 fec0:1:1:0:0:0:0:0/48

The line with Reachability tells you if and how tinc communicates with the
peer. The Address is the actual address used to communicate with foo using
UDP.

Implementing a HTTP server does, in itself, nothing to help debugging; it
merely presents information through another channel.  What information do you
want to get that is currently hard to extract from tinc?

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20131215/4dc06130/attachment.sig>