High tinc traffic on ethernet without tinc load

[Maximilian Stein]

Yes, exactly. There are lots of packages exchanged between tinc processes  on port 655, accounting to 99 % of the Ethernet traffic, while the virtual interface stays almost idle.

Best,
Maximilian

Am 20. März 2020 21:09:18 MEZ schrieb Lars Kruse <lists at sumpfralle.de>:
>Hello Maximilian,
>
>Am Fri, 20 Mar 2020 19:43:35 +0100
>schrieb Maximilian Stein <m at steiny.biz>:
>
>> My current mitigation is to stop some tinc peers for ten seconds and
>to
>> start them again afterwards, that usually causes the excessive
>traffic
>> to stop without interrupting service too much.
>
>I am guessing now: the rise of traffic on the ethernet link is caused
>by
>packets being exchanged between the tinc processes (e.g. port 655)?
>I think, you did not mention this explicitly, but the effect of a tinc
>restart
>points in this direction. This information is quite relevant for the
>further
>discussion, I guess.
>
>Cheers,
>Lars
>_______________________________________________
>tinc mailing list
>tinc at tinc-vpn.org
>https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20200320/39db2e44/attachment.html>