tinc devel - May 2015 - tinc 1.1 never seems to accept UDP packets from 1.0.24 hosts

Hallo,

I have a couple of tinc hosts in the same network, some using the latest 
tinc 1.1 git and some using 1.0.24.

It seems like traffic between 1.1 and 1.0 nodes is always transfered 
using TCP (and an intermediate node, if not directly connected), never 
with UDP.


Viewed from host W (tinc 1.1):

(All after successfully pinging an IP behind the remote side to trigger 
UDP path probing, and no blocking firewall on the way)

# tinc info T:
(tinc 1.0.24, directly connected)
Node:         T
Node ID:      97e7a2ff259b
Address:      1.2.3.4 port 4200
Online since: 2015-05-13 22:38:45
Status:       validkey visited reachable
Options:      pmtu_discovery clamp_mss
Protocol:     17.0
Reachability: directly with TCP

# tinc info V:
(tinc 1.0.24, no direct connect)
Node:         V
Node ID:      80a618663578
Address:      2.3.4.5 port 20316
Online since: 2015-05-13 22:38:45
Status:       validkey visited reachable
Options:      pmtu_discovery clamp_mss
Protocol:     17.0
Reachability: none, forwarded via H

# tinc info H
(tinc 1.1 git, direct connect)
Node:         H
Node ID:      68050b57da8f
Address:      3.4.5.6 port 443
Online since: 2015-05-13 22:40:07
Status:       validkey visited reachable sptps udp_confirmed
Options:      pmtu_discovery clamp_mss
Protocol:     17.7
Reachability: directly with UDP
PMTU:         1439

# tinc info O
(tinc 1.1, no direct connect)
Node:         O
Node ID:      613b32c62e2a
Address:      4.5.6.7 port 29115
Online since: 2015-05-13 23:16:08
Status:       validkey visited reachable sptps udp_confirmed
Options:      pmtu_discovery clamp_mss
Protocol:     17.7
Reachability: directly with UDP
PMTU:         1439


Debug output of communication W (1.1) trying to talk to V (1.0):

It seems that it does not understand the UDP probe answer:

# tinc log 5 | grep 2.3.4.5
Sending UDP probe length 18 to V (2.3.4.5 port 20316)
Received UDP packet from unknown source 2.3.4.5 port 20316

So real data is sent over TCP:

Sending packet of 168 bytes to V (2.3.4.5 port 20316)
Packet for V (2.3.4.5 port 20316) larger than minimum MTU, forwarding via H
Sending packet of 308 bytes to V (2.3.4.5. port 20316)
Packet for V (2.3.4.5 port 20316) larger than minimum MTU, forwarding via H


c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

On Wed, May 13, 2015 at 11:28:23PM +0200, Sven-Haegar Koch wrote:
> I have a couple of tinc hosts in the same network, some using the latest 
> tinc 1.1 git and some using 1.0.24.
> 
> It seems like traffic between 1.1 and 1.0 nodes is always transfered 
> using TCP (and an intermediate node, if not directly connected), never 
> with UDP.
[...]
> # tinc log 5 | grep 2.3.4.5
> Sending UDP probe length 18 to V (2.3.4.5 port 20316)
> Received UDP packet from unknown source 2.3.4.5 port 20316
This should be fixed in the latest commit.

-- 
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: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20150515/7ec574ff/attachment.sig>

On Fri, 15 May 2015, Guus Sliepen wrote:
> On Wed, May 13, 2015 at 11:28:23PM +0200, Sven-Haegar Koch wrote:
> 
> > I have a couple of tinc hosts in the same network, some using the
latest
> > tinc 1.1 git and some using 1.0.24.
> > 
> > It seems like traffic between 1.1 and 1.0 nodes is always transfered 
> > using TCP (and an intermediate node, if not directly connected), never
> > with UDP.
> [...]
> > # tinc log 5 | grep 2.3.4.5
> > Sending UDP probe length 18 to V (2.3.4.5 port 20316)
> > Received UDP packet from unknown source 2.3.4.5 port 20316
> 
> This should be fixed in the latest commit.
Thanks Guus!
Looks Good!

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.