All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Josh Samuelson <josamue1@wsc.edu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] new match extension `flow'
Date: Sat, 06 Nov 2004 16:19:22 +0100	[thread overview]
Message-ID: <418CEB7A.9080505@eurodev.net> (raw)
In-Reply-To: <20041104022039.GA25749@wsc.edu>

Hi Josh,

Josh Samuelson wrote:

>You'll have to excuse my newness to the netfilter-devel scene and the
>list in general.  Thank you for pointing out the thread on the connection
>tracking events patch.  I had no idea work was being done there.
>Initial impression: Slick!
>
>I took your recommendations and changed the patch to use the connection
>tracking events API.  I also altered the flow match module to track
>the number of connections based on a network/mask option if one is
>specified.
>
>The kernel patch can only be applied after your CTE patch.  It should
>patch fine on 2.6.9, but 2.6.10-rc1 will reject a hunk for
>net/ipv4/netfilter/Kconfig because I added the lines necessary for
>IP_NF_CONNTRACK_EVENTS; easy enough to fix by hand though.
>
>The iptables patch should apply fine to vanilla iptables-1.2.11.
>  
>

nice work!

>I've only done some initial testing with this thus far: one machine
>routing through a patched machine.  Hopefully here in the next
>few days I can put this on a machine that routes a few hundred
>nodes to put some more load on it for testing purposes.
>  
>

please, don't forget that we are still discussing the event API. As this 
new match goes on top of it, we can hold this patch until the event API 
is pushed forward. Then we'll go back this point.

Some comments:

>diff -Pru linux-2.6.9/include/linux/netfilter_ipv4/ip_cte_flow.h linux-2.6.9-flow/include/linux/netfilter_ipv4/ip_cte_flow.h
>--- linux-2.6.9/include/linux/netfilter_ipv4/ip_cte_flow.h	1969-12-31 18:00:00.000000000 -0600
>+++ linux-2.6.9-flow/include/linux/netfilter_ipv4/ip_cte_flow.h	2004-11-03 19:10:13.000000000 -0600
>  
>

I see two possibilities here:

a) move ip_cte_flow.[h|c] to ipt_flow.[h|c], matches always fit in a file.
b) rename ip_cte_flow to ip_conntrack_flow_stats, this could be a module 
which generates stats about current connections going through the firewall.

I need to give more spins to this issue.

Any comments?

Pablo

  reply	other threads:[~2004-11-06 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28  2:05 [PATCH] new match extension `flow' Josh Samuelson
2004-10-28 20:15 ` Josh Samuelson
2004-10-29 19:32 ` Pablo Neira
2004-10-31  6:38   ` Josh Samuelson
2004-10-31 14:41     ` Pablo Neira
2004-11-04  2:20       ` Josh Samuelson
2004-11-06 15:19         ` Pablo Neira [this message]
2004-11-08  2:52           ` Josh Samuelson
2004-11-10 18:12             ` Pablo Neira
2004-11-13 22:12         ` Pablo Neira

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=418CEB7A.9080505@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=josamue1@wsc.edu \
    --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.