[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090227181009.5b53f4c8@nehalam>
Date: Fri, 27 Feb 2009 18:10:09 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: Patrick McHardy <kaber@...sh.net>,
David Miller <davem@...emloft.net>,
netfilter-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] iptables: new strict host model match
On Sat, 28 Feb 2009 02:53:10 +0100 (CET)
Jan Engelhardt <jengelh@...ozas.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists