From: Patrick McHardy <kaber@trash.net>
To: Philip Craig <philipc@snapgear.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@lists.netfilter.org>
Subject: Re: [RFC][PATCH] optimise iptables interface matching
Date: Sat, 26 May 2007 10:47:56 +0200 [thread overview]
Message-ID: <4657F43C.2000306@trash.net> (raw)
In-Reply-To: <46561A9F.2010800@snapgear.com>
Philip Craig wrote:
> Patrick McHardy wrote:
>
>>I don't like the kernel-internal fiddling with the flags too
>>much, but I don't see a way around it.
>
>
> The other idea I had was moving the interface matching into
> an internal match that would be checked by IPT_MATCH_ITERATE().
> Not sure if this is feasible yet.
Mhh .. probably not since you would have to put it somewhere
in the blob.
>>userspace should just ignore unknown flags.
>
>
> I was trying to completely hide them from userspace so that we
> still have the option to use them for something else later on.
> If we ever send them to userspace, then they are taken forever,
> otherwise a newer iptables userspace may not work with an older
> kernel.
We could do that, but we would need some other place to store them
since once we want to use them for something new we can't put them
in ->flags anymore.
next prev parent reply other threads:[~2007-05-26 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 5:55 [RFC][PATCH] optimise iptables interface matching Philip Craig
2007-05-24 17:43 ` Patrick McHardy
2007-05-24 23:07 ` Philip Craig
2007-05-26 8:47 ` Patrick McHardy [this message]
2007-05-25 0:44 ` Yasuyuki KOZAKAI
2007-05-25 0:56 ` Philip Craig
2007-05-25 4:11 ` Yasuyuki KOZAKAI
2007-05-26 9:20 ` Patrick McHardy
2007-05-28 19:53 ` Henrik Nordstrom
2007-05-29 0:24 ` Philip Craig
2007-05-30 1:34 ` Henrik Nordstrom
2007-06-06 5:49 ` Philip Craig
2007-06-06 6:13 ` Eric Dumazet
2007-05-29 9:54 ` 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=4657F43C.2000306@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=philipc@snapgear.com \
/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.