Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Michael Smith <msmith@cbnco.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: IPsec tunnel forwarding in net-next-2.6 since 452edd59
Date: Tue, 15 Mar 2011 23:16:51 +0100	[thread overview]
Message-ID: <1300227411.2565.7.camel@edumazet-laptop> (raw)
In-Reply-To: <4D7FB054.2090902@cbnco.com>

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 <msmith@cbnco.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
index 1ba0258..027e3c6 100644
--- a/net/xfrm/xfrm_policy.c
+++ b/net/xfrm/xfrm_policy.c
@@ -2175,7 +2175,7 @@ int __xfrm_route_forward(struct sk_buff *skb, unsigned short family)
 	struct net *net = dev_net(skb->dev);
 	struct flowi fl;
 	struct dst_entry *dst;
-	int res = 0;
+	int res = 1;
 
 	if (xfrm_decode_session(skb, &fl, family) < 0) {
 		XFRM_INC_STATS(net, LINUX_MIB_XFRMFWDHDRERROR);
@@ -2186,7 +2186,7 @@ int __xfrm_route_forward(struct sk_buff *skb, unsigned short family)
 
 	dst = xfrm_lookup(net, skb_dst(skb), &fl, NULL, 0);
 	if (IS_ERR(dst)) {
-		res = 1;
+		res = 0;
 		dst = NULL;
 	}
 	skb_dst_set(skb, dst);




  reply	other threads:[~2011-03-15 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 18:30 IPsec tunnel forwarding in net-next-2.6 since 452edd59 Michael Smith
2011-03-15 22:16 ` Eric Dumazet [this message]
2011-03-15 22:28   ` David Miller
2011-03-15 22:31     ` Eric Dumazet
2011-03-15 22:51   ` Michael Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1300227411.2565.7.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=msmith@cbnco.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox