netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Problem with new --physdev-out style
Date: Wed, 24 Oct 2007 16:11:25 +0200	[thread overview]
Message-ID: <471F528D.8000501@plouf.fr.eu.org> (raw)
In-Reply-To: <20071024120622.GB27593@volker-sauer.de>

Volker Sauer a écrit :
> 
> In case someone is using physdev in OUTPUT, display the message like it
> is now: "using --physdev-out in the OUTPUT chains for non-bridged traffic
> is not supported anymore".

Ok.

> In case it is used inside FORWARD, check if all physdev interfaces are
> members of the same bridge.

As Patrick said, that condition may change over time. I like to have all 
my ruleset loaded before the network is configured, even before some 
interfaces exist. Your proposed change would prevent it. Besides, my 
opinion is that it is not the job of iptables to do such checks.

> If yes, accept the rule, because then it is
> allowed to use it!!!  (Which is the case all the thousands of rules in
> my firewalls except the 5 that I sent to this list :-().
> If no, display a message like this:
> 
> "physdev match: using --physdev-out in the FORWARD chains is only 
> allowed if all physical interfaces are members of the same bridge."

This is wrong and inacurate. Using --physdev-out in the FORWARD and 
POSTROUTING chains is supported for *bridged* traffic only, period. All 
physical interfaces being members of the same bridge is not a sufficient 
condition to make sure that only bridged traffic will be matched. 
Traffic can still be routed from a bridge to itself.

  parent reply	other threads:[~2007-10-24 14:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071024071854.GA18581@volker-sauer.de>
2007-10-24  7:38 ` Problem with new --physdev-out style Patrick McHardy
2007-10-24  8:22   ` Philip Craig
2007-10-24  8:34     ` Patrick McHardy
2007-10-24  8:43       ` Pascal Hambourg
2007-10-24  9:15         ` Philip Craig
2007-10-24  9:22           ` Pascal Hambourg
2007-10-24  9:39             ` Philip Craig
2007-10-24  9:46               ` Pascal Hambourg
2007-10-24  9:05       ` Philip Craig
2007-10-24  9:42         ` Patrick McHardy
2007-10-24 12:06           ` Volker Sauer
2007-10-24 12:49             ` Patrick McHardy
2007-10-24 12:57               ` Volker Sauer
2007-10-24 14:11             ` Pascal Hambourg [this message]
2007-10-24 15:18               ` Volker Sauer
2007-10-24  9:28     ` Philip Craig

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=471F528D.8000501@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@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).