From: Michael Smith <hidden> Date: 2011-03-15 18:30:49
Hi,
I'm able to ping across a tunnel to a peer running net-next-2.6, but
only to an interface on the peer; trying to ping a host behind the peer
fails. The incoming packet shows up in encrypted and decrypted form in
tcpdump, but it's not forwarded. None of the XFRM error counters are
incremented; the packets just silently fail to be forwarded.
There are no iptables rules and net.ipv4.ip_forward=1. The same config
works on 2.6.38-rc8. git bisect pointed me to commit 452edd59 from March 2:
xfrm: Return dst directly from xfrm_lookup()
Instead of on the stack.
ip xfrm policy:
src 192.168.136.0/24 dst 192.168.137.0/24
dir out priority 2344 ptype main
tmpl src 1.1.1.136 dst 1.1.1.137
proto esp reqid 16385 mode tunnel
src 192.168.137.0/24 dst 192.168.136.0/24
dir fwd priority 2344 ptype main
tmpl src 1.1.1.137 dst 1.1.1.136
proto esp reqid 16385 mode tunnel
src 192.168.137.0/24 dst 192.168.136.0/24
dir in priority 2344 ptype main
tmpl src 1.1.1.137 dst 1.1.1.136
proto esp reqid 16385 mode tunnel
net-next-2.6 host is at 1.1.1.136 and 192.168.136.1. 2.6.35.10 host is
at 1.1.1.137 and 192.168.137.1. From that host:
ping -I 192.168.137.1 192.168.136.1 -> success
ping -I 192.168.137.1 192.168.136.2 -> silent failure
Thanks,
Mike
From: Eric Dumazet <hidden> Date: 2011-03-15 22:17:01
Le mardi 15 mars 2011 à 14:30 -0400, Michael Smith a écrit :
Hi,
I'm able to ping across a tunnel to a peer running net-next-2.6, but
only to an interface on the peer; trying to ping a host behind the peer
fails. The incoming packet shows up in encrypted and decrypted form in
tcpdump, but it's not forwarded. None of the XFRM error counters are
incremented; the packets just silently fail to be forwarded.
There are no iptables rules and net.ipv4.ip_forward=1. The same config
works on 2.6.38-rc8. git bisect pointed me to commit 452edd59 from March 2:
xfrm: Return dst directly from xfrm_lookup()
Instead of on the stack.
ip xfrm policy:
src 192.168.136.0/24 dst 192.168.137.0/24
dir out priority 2344 ptype main
tmpl src 1.1.1.136 dst 1.1.1.137
proto esp reqid 16385 mode tunnel
src 192.168.137.0/24 dst 192.168.136.0/24
dir fwd priority 2344 ptype main
tmpl src 1.1.1.137 dst 1.1.1.136
proto esp reqid 16385 mode tunnel
src 192.168.137.0/24 dst 192.168.136.0/24
dir in priority 2344 ptype main
tmpl src 1.1.1.137 dst 1.1.1.136
proto esp reqid 16385 mode tunnel
net-next-2.6 host is at 1.1.1.136 and 192.168.136.1. 2.6.35.10 host is
at 1.1.1.137 and 192.168.137.1. From that host:
ping -I 192.168.137.1 192.168.136.1 -> success
ping -I 192.168.137.1 192.168.136.2 -> silent failure
Thanks,
Thanks for this excellent bug report !
Could you try following patch ?
[PATCH] xfrm: fix __xfrm_route_forward()
This function should return 0 in case of error, 1 if OK
commit 452edd598f60522 (xfrm: Return dst directly from xfrm_lookup())
got it wrong.
Reported-and-bisected-by: Michael Smith [off-list ref]
Signed-off-by: Eric Dumazet <redacted>
---
From: David Miller <davem@davemloft.net> Date: 2011-03-15 22:27:47
From: Eric Dumazet <redacted>
Date: Tue, 15 Mar 2011 23:16:51 +0100
Could you try following patch ?
[PATCH] xfrm: fix __xfrm_route_forward()
This function should return 0 in case of error, 1 if OK
commit 452edd598f60522 (xfrm: Return dst directly from xfrm_lookup())
got it wrong.
Reported-and-bisected-by: Michael Smith [off-list ref]
Signed-off-by: Eric Dumazet <redacted>
Thanks so much for fixing this Eric, sheesh you are so awesome that
you don't even give me enough time to fix my own bugs. :-))))
Applied, and indeed thanks to Michael for the excellent report.
From: Michael Smith <hidden> Date: 2011-03-15 22:51:36
On Tue, 15 Mar 2011, Eric Dumazet wrote:
Could you try following patch ?
[PATCH] xfrm: fix __xfrm_route_forward()
This function should return 0 in case of error, 1 if OK
commit 452edd598f60522 (xfrm: Return dst directly from xfrm_lookup())
got it wrong.