Hi,
Just to follow up on this, after trying the re-keying option set to
86400, we were still seeing the intermittent tcp timeouts.
However after switching TcpOnly option to on, we have now been having
reliable communication for 8 hours or so, whereas before we were getting
timeouts every couple of hours.
Sop hopefully this has solved the problem, and it looks like UDP data
was being dropped occasionally.
Tom
On 2013-11-28 17:57, [email protected] wrote:
OK makes sense.
How often would you expect to see the REQ_KEY and the PMTU probes
occurring?
They seem to happen quite a lot, is that normal?
Tom
On 2013-11-28 15:51, Guus Sliepen wrote:
On Thu, Nov 28, 2013 at 02:52:45PM +0000, [email protected] wrote:
Now that debugging is turned on properly, I am seeing some
interesting lines:
2013-11-28 14:48:48 tinc.dcvpn[31620]: Got type 2 MTU probe reply
1431 from rps (2001:1b40:5000:9::2 port 655)
2013-11-28 14:48:48 tinc.dcvpn[31620]: Got type 2 MTU probe reply
1431 from rps (2001:1b40:5000:9::2 port 655)
2013-11-28 14:48:48 tinc.dcvpn[31620]: Got type 2 MTU probe reply
1431 from rps (2001:1b40:5000:9::2 port 655)
2013-11-28 14:48:48 tinc.dcvpn[31620]: rps (2001:1b40:5000:9::2 port
655) RTT 0.49 ms, burst bandwidth 51.684 Mbit/s, rx packet loss
100.00 %
Specifically the bit about 100% packet loss.
Ignore the bit about packet loss, that is an estimate that doesn't
work
correctly yet.
It was shortly after following by:
2013-11-28 14:51:01 tinc.dcvpn[31620]: Got REQ_KEY from rps
(2001:1b40:5000:9::2 port 55170): 15 rps rsukmhb 21 AA...
I got a REQ_KEY request 12 times in 1s from rps.
That is also normal for tinc 1.1.
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
