From: Patrick McHardy <kaber@trash.net>
To: Mohammad Mohsenzadeh <mmohsenz@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: 2.6.20 support for other 'features'
Date: Wed, 11 Apr 2007 19:49:30 +0200 [thread overview]
Message-ID: <461D1FAA.1080100@trash.net> (raw)
In-Reply-To: <e6af3bc80704111039x322e55e5qe1ea1568b59214b0@mail.gmail.com>
Mohammad Mohsenzadeh wrote:
> I have been developing extension for netfilter to allow stateful
> firewall and filtering. I was looking at the new api in 2.6.20 and I
> was wondering why the number of 'features' allowed is maxed to 4.
>
> I was thinking of configuration number of features and maybe some way
> of setting a default feature to use instead of NF_CT_F_BASIC. This way
> the netfilter can easily be extended. I can provide a patch if you
> think the above is a good idea.
Lets see the patch to decide whether this is a good idea :)
But the feature stuff needs to be reworked in the not too distant
future, its impossible to properly determine what features might
be used in the future at allocation time, which is why we always
allocate for the worst case anyway and still can't properly deal
with the NAT module being loaded late.
next prev parent reply other threads:[~2007-04-11 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 17:39 2.6.20 support for other 'features' Mohammad Mohsenzadeh
2007-04-11 17:41 ` Jan Engelhardt
2007-04-11 17:46 ` Mohammad Mohsenzadeh
2007-04-11 17:49 ` Patrick McHardy [this message]
2007-04-11 17:51 ` Patrick McHardy
2007-04-11 18:14 ` Mohammad Mohsenzadeh
2007-04-11 18:22 ` Patrick McHardy
2007-04-12 22:49 ` Mohammad Mohsenzadeh
2007-04-13 4:22 ` Patrick McHardy
[not found] ` <200704161302.l3GD27Ft021389@toshiba.co.jp>
2007-04-16 13:10 ` Patrick McHardy
2007-04-16 13:02 ` Yasuyuki KOZAKAI
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=461D1FAA.1080100@trash.net \
--to=kaber@trash.net \
--cc=mmohsenz@gmail.com \
--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.