Hi,
I'll post just a few of my configuration files if that is okay. Each host uses a network interface called "vpn0" and a static IPv6 "1111:1::X". In addition, each host is responsible for a subnet "1111:1:X::/64". These examples are from the so called node01.
/usr/local/etc/tinc/sites/tinc.conf
Name = node01
AddressFamily = ipv6
Mode = switch
Interface = vpn0
AddressFamily = ipv6
Mode = switch
Interface = vpn0
/usr/local/etc/tinc/sites/tinc-up
#!/bin/bash
# interface and local subnet
ip -6 link set $INTERFACE up mtu 1280 txqueuelen 1000
ip -6 addr add 1111:1::1 dev $INTERFACE
ip -6 route add 1111:1::/48 dev $INTERFACE
ip -6 link set $INTERFACE up mtu 1280 txqueuelen 1000
ip -6 addr add 1111:1::1 dev $INTERFACE
ip -6 route add 1111:1::/48 dev $INTERFACE
/usr/local/etc/tinc/sites/hosts/node02
Address = <public ipv6 of node02>
Subnet = 1111:1:1::/64
# RSA and ED5519 key
Subnet = 1111:1:1::/64
# RSA and ED5519 key
/usr/local/etc/tinc/sites/hosts/node02-up
ip -6 route add 1111:1:2::/64 via 1111:1::2 metric 512
ip -6 route add <public ipv6 of node02>/64 via 1111:1::2 metric 512
ip -6 route add <public ipv6 of node02>/64 via 1111:1::2 metric 512
Kind regards
Christopher
Gesendet: Mittwoch, 01. Mai 2019 um 16:52 Uhr
Von: "Absolute Truth" <requiredtr...@gmail.com>
An: tinc@tinc-vpn.org
Betreff: Re: very high traffic without any load
Von: "Absolute Truth" <requiredtr...@gmail.com>
An: tinc@tinc-vpn.org
Betreff: Re: very high traffic without any load
Sound like your tincs are talking to each other over and over. Can we get some info from tinc.conf and tinc host files.. need to see some ip address configs for tinc.
On Wed, May 1, 2019, 10:46 AM Christopher Klinge <christ.kli...@web.de> wrote:
Hi everyone,
I am new to using tinc and currently trying to set up a full IPv6 mesh between 4 servers of mine. Setting it up went smoothly and all of the tinc clients do connect properly. Routing through the network works fine as well. There is however a large amount of management traffic which I assume should not be the case.
Here is a quick snapshot using "tinc -n netname top" showing cumulative values:
Tinc sites Nodes: 4 Sort: name Cumulative
Node IN pkts IN bytes OUT pkts OUT bytes
node01 98749248 67445198848 98746920 67443404800
node02 37877112 25869768704 37878860 25870893056
node03 34607168 23636463616 34608260 23637114880
node04 26262640 17937174528 26262956 17937287168
That's 67GB for node01 in approximately 1.5 hours. Needless to say, this kind of traffic is entirely prohibiting me from using tinc. I have read a few messages in this mailing list, but the only thing I could find were traffic spikes, likely caused by other systems using the same devices as tinc or by the tinc daemon running for too long. The later does not apply, as the entire network was up for an hour and a half only. Additionally I do not think the first one applies, as all of my machines use entirely fresh tun/tap devices when running the network. The problem appeared even after a fresh restart with not other noteworthy processes running besides tinc.
Any help would be appreciated.
Kind regards
Christopher
_______________________________________________
tinc mailing list
tinc@tinc-vpn.org
https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
_______________________________________________ tinc mailing list tinc@tinc-vpn.org https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
