From: Patrick McHardy <kaber@trash.net>
To: quadong@users.sourceforge.net
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: childlevel's pom comment
Date: Thu, 04 Mar 2004 04:10:08 +0100 [thread overview]
Message-ID: <40469E10.7080100@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0403031947450.8957@dsl093-017-216.msp1.dsl.speakeasy.net>
Hi Mathew,
I'm going to add your updated help-text. But I have doubts about
whether a new match is required at all. A connection can only have
a childlevel of one because only masters have helpers assigned to
them, although in theory the expect-function could register more
expectations. So you can basically match if a connection was
expected or not. The same can also be achieved by a trivial change
to the helper match, just allow zero-string length and use them
as a special value. This should also allow full userspace
compatibility. What do you think ?
Regards
Patrick
quadong@users.sourceforge.net wrote:
> Hi, I noticed that the childlevel patch currently has this to say about
> itself in patch-o-matic:
>
> "This adds CONFIG_IP_NF_MATCH_CHILDLEVEL option, which be used to
> match the childlevel of a connection."
>
> I know _I_ would be confused if I read this. Could it be changed to the
> following?
>
> This patch allows you to match on the childlevel of a connection.
> A master connection, such as the command stream of FTP, has a
> childlevel of zero, its first child, such as the data stream of
> FTP, has a childlevel of one. Usage example:
>
> iptables ... -m childlevel --level 1 ...
>
> Thanks,
> matthew
next prev parent reply other threads:[~2004-03-04 3:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 1:48 childlevel's pom comment quadong
2004-03-04 3:10 ` Patrick McHardy [this message]
2004-03-04 4:44 ` Matthew Strait
2004-03-04 5:33 ` Patrick McHardy
2004-03-04 21:10 ` Matthew Strait
2004-03-04 21:48 ` Patrick McHardy
2004-03-05 1:05 ` [PATCH] matching any helper in ipt_helper.c Matthew Strait
2004-03-05 2:13 ` Patrick McHardy
2004-03-05 9:23 ` Martin Josefsson
2004-03-05 7:14 ` Henrik Nordstrom
2004-03-04 22:47 ` childlevel's pom comment Henrik Nordstrom
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=40469E10.7080100@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=quadong@users.sourceforge.net \
/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.