From: Patrick McHardy <kaber@trash.net>
To: "bdschuym@pandora.be" <bdschuym@telenet.be>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: RFC: Disable defered bridge hooks by default
Date: Fri, 07 Jul 2006 12:24:14 +0200 [thread overview]
Message-ID: <44AE364E.1090704@trash.net> (raw)
In-Reply-To: <W673373073133751152267462@hoboe1bl6.telenet-ops.be>
bdschuym@pandora.be wrote:
>>----- Oorspronkelijk bericht -----
>>Van: Patrick McHardy [mailto:kaber@trash.net]
>>
>>This is the latest version. Fixed the crash and added a
>>runtime warning to the physdev match and on-the-fly activation
>>when needed, so we don't need the sysctls. Works fine in
>>a few simple tests, if there are no further objections
>>I'll submit this version.
>
>
> I'd add something like the code below on top of your patch. That way no false warnings are given if the user specifies she only wants to look at bridged packets.
>
> --- net/netfilter/xt_physdev.c.old 2006-07-07 12:11:44.000000000 +0200
> +++ net/netfilter/xt_physdev.c 2006-07-07 12:14:14.000000000 +0200
> @@ -114,7 +114,9 @@ checkentry(const char *tablename,
> info->bitmask & ~XT_PHYSDEV_OP_MASK)
> return 0;
> if (brnf_deferred_hooks == 0 && info->bitmask & XT_PHYSDEV_OP_OUT &&
> - hook_mask & ((1 << NF_IP_LOCAL_OUT) | (1 << NF_IP_FORWARD))) {
> + hook_mask & ((1 << NF_IP_LOCAL_OUT) | (1 << NF_IP_FORWARD)) &&
> + (!(info->bitmask & XT_PHYSDEV_OP_BRIDGED) ||
> + info->invert & XT_PHYSDEV_OP_BRIDGED)) {
> printk(KERN_WARNING "physdev match: using --physdev-out in the "
> "OUTPUT or FORWARD chain is deprecated and breaks other "
> "things, it will be removed in January 2007. See "
Right, I forgot about that, will add and also update the text.
next prev parent reply other threads:[~2006-07-07 10:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 10:17 RFC: Disable defered bridge hooks by default bdschuym@pandora.be
2006-07-07 10:24 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 12:56 bdschuym@pandora.be
2006-07-13 14:38 ` Patrick McHardy
[not found] <W8195318669268441152182124@nocme1bl6.telenet-ops.be>
2006-07-06 10:49 ` Patrick McHardy
2006-07-07 3:37 ` Patrick McHardy
2006-07-04 9:26 Patrick McHardy
2006-07-04 9:27 ` Patrick McHardy
2006-07-08 0:36 ` Tom Eastep
2006-07-08 3:01 ` Patrick McHardy
2006-07-10 9:56 ` Amin Azez
2006-07-11 8:28 ` Patrick McHardy
2006-07-11 9:33 ` Amin Azez
2006-07-11 20:34 ` Tom Eastep
2006-07-11 21:29 ` Patrick McHardy
2006-07-12 22:41 ` Tom Eastep
2006-07-13 7:35 ` Patrick McHardy
2006-07-13 14:11 ` Tom Eastep
2006-07-13 14:45 ` Patrick McHardy
2006-07-13 15:31 ` Tom Eastep
2006-07-15 14:32 ` Tom Eastep
2006-07-19 14:21 ` Patrick McHardy
2006-07-19 15:50 ` Tom Eastep
2006-07-19 16:02 ` Patrick McHardy
2006-07-13 9:56 ` Amin Azez
2006-07-12 6:16 ` Philip Craig
2006-07-13 0:20 ` Tom Eastep
2006-07-13 0:42 ` David Miller
2006-07-13 0:45 ` Tom Eastep
2006-07-13 9:45 ` Amin Azez
2006-07-13 7:31 ` Patrick McHardy
2006-07-13 7:46 ` Patrick McHardy
2006-07-13 8:12 ` Philip Craig
2006-07-13 8:36 ` Patrick McHardy
2006-07-13 14:11 ` Amin Azez
2006-07-13 14:50 ` Patrick McHardy
2006-07-13 15:29 ` Amin Azez
2006-07-19 16:36 ` Patrick McHardy
[not found] ` <44BE624E.5080307@ufomechanic.net>
2006-07-19 17:15 ` 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=44AE364E.1090704@trash.net \
--to=kaber@trash.net \
--cc=bdschuym@pandora.be \
--cc=bdschuym@telenet.be \
--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.