All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Christophe Saout <christophe@saout.de>
Cc: Robert Borger <bborger@navcorp.com>,
	netfilter-devel@lists.netfilter.org,
	Andrew Hall <temp02@bluereef.com.au>
Subject: Re: NAT behind IPSEC GW working OK - please review patch
Date: Sun, 20 Mar 2005 17:12:52 +0100	[thread overview]
Message-ID: <423DA104.7000402@trash.net> (raw)
In-Reply-To: <1111256850.19630.11.camel@leto.cs.pocnet.net>

Christophe Saout wrote:
>>static inline int xfrm_policy_check(struct sock *sk, int dir, struct sk_buff
>>*skb, unsigned short family)
>>{
>>  if (sk && sk->sk_policy[XFRM_POLICY_IN])
>>    return __xfrm_policy_check(sk, dir, skb, family);
>>		
>>  return(!xfrm_policy_list[dir] && !skb->sp) ||
>>    (skb->sp && skb->sp->decap_done) || /* Added this line */
>>    (skb->dst->flags & DST_NOPOLICY) ||
>>    __xfrm_policy_check(sk, dir, skb, family);
>>}
> 
> 
> I can confirm that this fixes the problem you described.
> (I'm using the IPSEC+NAT patches I forward-ported for 2.6.11).
> 
> The line you added should be enclosed in an pair of #ifdef
> CONFIG_NETFILTER and #endif.

This is not correct, the reason why the packets are dropped
is most likely a missing forward policy. If this is not the
case, there must be a bug somewhere in nf_nat_decode_session4().

Regards
Patrick

  reply	other threads:[~2005-03-20 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 17:38 NAT behind IPSEC GW working OK - please review patch Robert Borger
2005-03-19 18:27 ` Christophe Saout
2005-03-20 16:12   ` Patrick McHardy [this message]
2005-03-21  2:10     ` Andrew Hall
2005-03-21 19:15     ` Christophe Saout
2005-04-06 15:04       ` Stephen Frost

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=423DA104.7000402@trash.net \
    --to=kaber@trash.net \
    --cc=bborger@navcorp.com \
    --cc=christophe@saout.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=temp02@bluereef.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.