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 11:46:48 +0200 [thread overview]
Message-ID: <471F1488.3000200@plouf.fr.eu.org> (raw)
In-Reply-To: <471F12DC.8050508@snapgear.com>
Philip Craig a écrit :
> Pascal Hambourg wrote:
>
>>Sure, but what about packets that enter a bridged interface and then are
>>routed ?
>
> It's not set for them either, they are still just routed packets.
> Not sure I understand your question. My original comment was that
> because the packets are routed (even though they arrived on a bridge),
> the bridged flag is not set, and so the --physdev-is-bridged option
> would never match for that particular rule, and it simply isn't
> possible to fix that rule to get the --physdev-out to work.
I misunderstood your original comment. I thought you meant that
--physdev-is-bridged would not help distinguish between routed and
bridged packets when the input and output interfaces are bridges. Thanks
for taking the time to clarify.
next prev parent reply other threads:[~2007-10-24 9:46 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 [this message]
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
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=471F1488.3000200@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).