All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOVACS Krisztian <hidden@sch.bme.hu>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Patrick McHardy <kaber@trash.net>,
	netfilter-devel@vger.kernel.org,
	Balazs Scheidler <bazsi@balabit.hu>,
	Toth Laszlo Attila <panther@balabit.hu>
Subject: Re: [PATCH 08/13] Split Netfilter IPv4 defragmentation into a separate module
Date: Tue, 23 Oct 2007 20:26:32 +0200	[thread overview]
Message-ID: <200710232026.32866@nessa> (raw)
In-Reply-To: <Pine.LNX.4.64.0710172108180.8216@bizon.gios.gov.pl>

Hi Krzysztof,

On Wednesday 17 October 2007, Krzysztof Oledzki wrote:
> On Tue, 2 Oct 2007, KOVACS Krisztian wrote:
> > Netfilter connection tracking requires all IPv4 packets to be
> > defragmented. Both the socket match and the TPROXY target depend on
> > this functionality, so this patch separates the Netfilter IPv4 defrag
> > hooks into a separate module.
>
> With this patch taken from:
>  
> http://people.netfilter.org/hidden/tproxy/tproxy4-2.6.23-200710090922.t
>ar.bz2 with:
> # CONFIG_NF_CONNTRACK_ENABLED is not set
> # CONFIG_NF_CONNTRACK is not set
>
> I get:
>
> net/ipv4/netfilter/nf_defrag_ipv4.c: In function
> 'ipv4_conntrack_defrag': net/ipv4/netfilter/nf_defrag_ipv4.c:44: error:
> 'struct sk_buff' has no member named 'nfct' make[3]: ***
> [net/ipv4/netfilter/nf_defrag_ipv4.o] Error 1
> make[2]: *** [net/ipv4/netfilter] Error 2
> make[1]: *** [net/ipv4] Error 2
>
> This is not a surprise since:
> --- cut here ---
> #if defined(CONFIG_NF_CONNTRACK) || defined(CONFIG_NF_CONNTRACK_MODULE)
>          struct nf_conntrack     *nfct;
>          struct sk_buff          *nfct_reasm;
> #endif
> --- cut here ---

Thanks for spotting this, indeed, this was an oversight from my part... 
The latest tree at http://people.netfilter.org/hidden/tproxy/ should fix 
this compilation problem.

-- 
KOVACS Krisztian

  reply	other threads:[~2007-10-23 18:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 20:39 [PATCH 00/13] Transparent Proxying Patches, Take 4 KOVACS Krisztian
2007-10-02 20:40 ` [PATCH 01/13] Loosen source address check on IPv4 output KOVACS Krisztian
2007-10-02 20:40 ` [PATCH 02/13] Implement IP_TRANSPARENT socket option KOVACS Krisztian
2007-10-02 20:41 ` [PATCH 03/13] Allow binding to non-local addresses if IP_TRANSPARENT is set KOVACS Krisztian
2007-10-02 20:41 ` [PATCH 04/13] Conditionally enable transparent flow flag when connecting KOVACS Krisztian
2007-10-02 20:42 ` [PATCH 05/13] Handle TCP SYN+ACK/ACK/RST transparency KOVACS Krisztian
2007-10-02 20:42 ` [PATCH 06/13] Port redirection support for TCP KOVACS Krisztian
2007-10-02 20:43 ` [PATCH 07/13] Export UDP socket lookup function KOVACS Krisztian
2007-10-02 20:43 ` [PATCH 08/13] Split Netfilter IPv4 defragmentation into a separate module KOVACS Krisztian
2007-10-08  8:30   ` Patrick McHardy
2007-10-17 19:11   ` Krzysztof Oledzki
2007-10-23 18:26     ` KOVACS Krisztian [this message]
2007-10-02 20:44 ` [PATCH 09/13] iptables tproxy core KOVACS Krisztian
2007-10-02 20:44 ` [PATCH 10/13] iptables socket match KOVACS Krisztian
2007-10-08  8:32   ` Patrick McHardy
2007-10-02 20:45 ` [PATCH 11/13] iptables TPROXY target KOVACS Krisztian
2007-10-08  8:34   ` Patrick McHardy
2007-10-02 20:45 ` [PATCH 12/13] Don't lookup the socket if there's a socket attached to the skb KOVACS Krisztian
2007-10-02 20:46 ` [PATCH 13/13] " KOVACS Krisztian
  -- strict thread matches above, loose matches on Subject: below --
2007-09-30 20:51 [PATCH 00/13] Transparent Proxying Patches, Take 3 KOVACS Krisztian
2007-09-30 20:53 ` [PATCH 08/13] Split Netfilter IPv4 defragmentation into a separate module KOVACS Krisztian
2007-09-30 22:35   ` 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=200710232026.32866@nessa \
    --to=hidden@sch.bme.hu \
    --cc=bazsi@balabit.hu \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ole@ans.pl \
    --cc=panther@balabit.hu \
    /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.