Invalid seqno and short packets

Daniel Schall schall at cs.uni-kl.de
Mon Aug 11 22:04:18 CEST 2014


Hi,

 

I just upgraded my entire environment from Tinc 1.0.24 (or prior) to the
most recent version from git (1.1pre10+), using ED25519.

 

Sometimes, especially after some failed authentication attempts or timed out
authentications, I get the following log messages:

 

2014-08-11 21:51:10 tinc.NNN[3376]: Connection with XXX (1.2.3.4 port 1)
activated

2014-08-11 21:51:10 tinc.NNN[3376]: Invalid packet seqno: 6 != 0

2014-08-11 21:51:10 tinc.NNN[3376]: Connection with YYY (9.8.7.6 port 1)
activated

2014-08-11 21:51:11 tinc.NNN[3376]: Invalid packet seqno: 7 != 0

2014-08-11 21:51:11 tinc.NNN[3376]: Received short packet

2014-08-11 21:51:11 tinc.NNN[3376]: Received short packet

2014-08-11 21:51:12 tinc.NNN[3376]: Received short packet

2014-08-11 21:51:12 tinc.NNN[3376]: Received short packet

2014-08-11 21:51:13 tinc.NNN[3376]: Received short packet

2014-08-11 21:51:13 tinc.NNN[3376]: Received short packet

 

Just wanted to report this, maybe the sequence number is not reset properly
when nodes disconnect?

 

 

Regards

 

Daniel Schall

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20140811/02421ef8/attachment.html>


More information about the tinc-devel mailing list