All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael McCallister <mikemc-netfilter@contactdesigns.com>
To: netfilter@lists.netfilter.org
Cc: devik@cdi.cz, laforge@netfilter.org
Subject: connbytes patch eliminated
Date: Wed, 03 May 2006 11:22:09 -0700	[thread overview]
Message-ID: <4458F4D1.1000503@contactdesigns.com> (raw)

Hello,

First, a warning - I am a newbie to netfilter, so I may ask some stupid 
questions here.  I believe the connbytes patch offers exactly what I am 
looking for - granted it is listed as experimental, but I am willing to 
test it out since if offers the functionality I think I need - mainly 
depriotizing bulk transfers.  I am concerned because it appears it was 
dropped from the main linux kernel, the last kernel I found with it was 
linux-2.6.15.7.  Also, it is not in pom-ng - at least I could not find 
it in pom snapshots or cvs 
(http://svn.netfilter.org/cgi-bin/viewcvs.cgi/trunk/patch-o-matic-ng/).  
So I get the impression there may be plans to get rid of the connbytes 
patch.  The latest iptables still does checks for it though "[ -f 
$KERNEL_DIR/net/ipv4/netfilter/ipt_connbytes.c ] && echo connbytes".  
Was there a decision that it was not suitable anymore and it is being 
eliminated in favor of another approach?  If so, any advice as to the 
new approach is greatly appreciated.  Also, if it was dropped from the 
kernel/pom because it was highly unstable and caused system crashes - 
that would be great information too :-)

Thanks for any help - my apologies if I missed something obvious.
Michael




             reply	other threads:[~2006-05-03 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 18:22 Michael McCallister [this message]
2006-05-04 15:57 ` connbytes patch eliminated Andy Furniss
2006-05-04 16:46   ` Michael McCallister

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=4458F4D1.1000503@contactdesigns.com \
    --to=mikemc-netfilter@contactdesigns.com \
    --cc=devik@cdi.cz \
    --cc=laforge@netfilter.org \
    --cc=netfilter@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.