From: Stephen Hemminger <shemminger@vyatta.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>,
David Miller <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] iptables: new strict host model match
Date: Fri, 27 Feb 2009 18:10:09 -0800 [thread overview]
Message-ID: <20090227181009.5b53f4c8@nehalam> (raw)
In-Reply-To: <alpine.LSU.2.00.0902280253030.20614@fbirervta.pbzchgretzou.qr>
On Sat, 28 Feb 2009 02:53:10 +0100 (CET)
Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Friday 2009-02-27 04:23, Stephen Hemminger wrote:
> >> >+static struct xt_match strict_mt_reg __read_mostly = {
> >> >+ .name = "strict",
> >> >+ .family = NFPROTO_IPV4,
> >> >+ .match = strict_mt,
> >> >+ .matchsize = 0,
> >> >+ .me = THIS_MODULE,
> >> >+};
> >>
> >> The match seems to make the most sense where an input device
> >> is available, so
> >>
> >> .hooks = (1 << NF_INET_PRE_ROUTING) | (1 << NF_INET_LOCAL_IN) |
> >> (1 << NF_INET_FORWARD)
> >>
> >> should probably be added.
> >
> >Then routing wouldn't work...
>
I suppose it could be useful to to different chains for routed vs non-routed
packets on pre-routing chain, but on forward chain it wouldn't really
do anything useful.
next prev parent reply other threads:[~2009-02-28 2:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 1:52 [PATCH] iptables: new strict host model match Stephen Hemminger
2009-02-27 3:16 ` Jan Engelhardt
2009-02-27 3:23 ` Stephen Hemminger
2009-02-27 8:30 ` Jozsef Kadlecsik
2009-02-28 1:53 ` Jan Engelhardt
2009-02-28 2:10 ` Stephen Hemminger [this message]
2009-02-28 8:27 ` Jan Engelhardt
2009-03-02 11:02 ` Patrick McHardy
2009-03-02 13:42 ` Jesper Dangaard Brouer
2009-03-02 13:46 ` Denys Fedoryschenko
2009-03-02 18:53 ` Stephen Hemminger
2009-03-02 22:12 ` 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=20090227181009.5b53f4c8@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).