From: Patrick McHardy <kaber@trash.net>
To: "Jorge Boncompte [DTI2]" <jorge@dti2.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] xx_nat_proto_gre: gre_key returns wrong pointer
Date: Fri, 27 Apr 2007 13:21:07 +0200 [thread overview]
Message-ID: <4631DCA3.4020701@trash.net> (raw)
In-Reply-To: <101c01c78829$24a70230$061010ac@intranet.dti2.net>
Jorge Boncompte [DTI2] wrote:
> Hi, Patrick take a look at this patch when you have time please. I
> tested it and behaves correctly, I can run one and only one GRE tunnel
> though a NATing box and PPTP still works too, if you try with a second
> tunnel from different host by the fact of not modifying the tuple it does
> not work as the comment in get_unique_tuple says.
> +++ linux-2.6.21/net/ipv4/netfilter/ip_nat_proto_gre.c 2007-04-26
> 19:01:02.000000000 +0200
> @@ -70,6 +70,11 @@
> __be16 *keyptr;
> unsigned int min, i, range_size;
>
> + /* If there is no master conntrack we are not PPTP,
> + do not change tuples */
> + if (!conntrack->master)
> + return 0;
> +
Thats a good idea, I thought it would be more complicated to
determine the kind of connection in get_unique_tuple() since
it doesn't get to see the packet.
Please sign off on the patch so I can apply it.
next prev parent reply other threads:[~2007-04-27 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 16:18 [PATCH] xx_nat_proto_gre: gre_key returns wrong pointer Jorge Boncompte [DTI2]
2007-04-24 12:50 ` Patrick McHardy
2007-04-26 17:34 ` Jorge Boncompte [DTI2]
2007-04-27 11:21 ` Patrick McHardy [this message]
2007-04-27 11:47 ` [PATCH] xx_nat_proto_gre: do not modify/corrupt GREv0 packets thought NAT Jorge Boncompte [DTI2]
2007-05-02 12:25 ` Patrick McHardy
2007-05-02 13:21 ` Jorge Boncompte [DTI2]
2007-05-02 13:23 ` Patrick McHardy
2007-05-02 13:48 ` Jorge Boncompte [DTI2]
2007-05-02 13:52 ` Patrick McHardy
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=4631DCA3.4020701@trash.net \
--to=kaber@trash.net \
--cc=jorge@dti2.net \
--cc=netfilter-devel@lists.netfilter.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 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.