From: Pablo Neira Ayuso <pablo@netfilter.org>
To: BORBELY Zoltan <bozo@andrews.hu>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: Support NAT-ed expect entries from user space
Date: Mon, 16 Jun 2008 22:10:46 +0200 [thread overview]
Message-ID: <4856C8C6.3070309@netfilter.org> (raw)
In-Reply-To: <20080616092148.GB2860@phoenix.home>
BORBELY Zoltan wrote:
> Hi,
>
> I'm developing a transparent user space ftp proxy, and I'm using expect
> entries to accept incoming data connections. It works quite well, but I
> had to patch the kernel to get it work. It's quite small, so I put it
> inline:
Just a wild thought. What if you create a new conntrack (instead of an
expectation) using a small timeout in state TCP SYN_SENT that represents
the new flow that it is expected to arrive? The first packet would seen
as a resent by the connection tracking so it would accept it. However,
the TCP sequence tracking may complain about it. Nevertheles, we can
also access to the internal TCP flags to enable IP_CT_TCP_FLAG_BE_LIBERAL.
> --- nf_conntrack_netlink-orig-2.6.22.9.c 2007-09-26 20:03:01.000000000 +0
> +++ nf_conntrack_netlink-new-2.6.22.9.c 2008-06-13 17:14:17.000000000 +0200
> @@ -39,6 +39,7 @@
> #ifdef CONFIG_NF_NAT_NEEDED
> #include <net/netfilter/nf_nat_core.h>
> #include <net/netfilter/nf_nat_protocol.h>
> +#include <net/netfilter/nf_nat_helper.h>
> #endif
>
> #include <linux/netfilter/nfnetlink.h>
> @@ -1439,7 +1440,11 @@
> goto out;
> }
>
> - exp->expectfn = NULL;
> + exp->expectfn = nf_nat_follow_master;
> +#ifdef CONFIG_NF_NAT_NEEDED
> + exp->saved_proto.tcp.port = tuple.dst.u.tcp.port; //!!!FIXME
> + exp->dir = IP_CT_DIR_ORIGINAL;
> +#endif
> exp->flags = 0;
> exp->master = ct;
> exp->helper = NULL;
>
> It's ugly as hell in the current form, but I have some ideas how to
> improve it to integrate it into the main kernel tree. Maybe we can add a
> new CTA_EXPECT_SAVED_PROTO attribute and get it from user space. What
> is your opinion?
Would this change be generic enough for userspace transparent proxies or
only for FTP?
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next parent reply other threads:[~2008-06-16 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080616092148.GB2860@phoenix.home>
2008-06-16 20:10 ` Pablo Neira Ayuso [this message]
2008-06-16 20:52 ` Support NAT-ed expect entries from user space Patrick McHardy
2008-06-16 22:17 ` BORBELY Zoltan
2008-06-16 22:43 ` Patrick McHardy
2008-06-17 15:05 ` Patrick McHardy
2008-06-23 15:31 ` BORBELY Zoltan
2008-06-23 15:56 ` Patrick McHardy
2008-06-16 21:29 ` BORBELY Zoltan
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=4856C8C6.3070309@netfilter.org \
--to=pablo@netfilter.org \
--cc=bozo@andrews.hu \
--cc=netfilter-devel@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 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.