Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Problem with new --physdev-out style
Date: Wed, 24 Oct 2007 10:36:31 +0200	[thread overview]
Message-ID: <471F040F.7040607@plouf.fr.eu.org> (raw)
In-Reply-To: <20071024071854.GA18581@volker-sauer.de>

Hello,

Volker Sauer a écrit :
> 
> with recent kernels, I have this problem:
> 
> kernel: physdev match: using --physdev-out in the OUTPUT, FORWARD and
> POSTROUTING chains for non-bridged traffic is not supported anymore.
> 
> What does "non-bridged" in this context mean??

It means packets leaving the IP stack, I guess you could say "routed" as 
opposed to "bridged". A packet can traverse iptables chains either when 
it is routed or when it is bridged. At the time a routed packet 
traverses the iptables chains, the "bridging decision" (i.e. chosing the 
output port when the output interface is a bridge) has not been made 
yet, so the output port is unknown and --physdev-out is irrelevant.

      parent reply	other threads:[~2007-10-24  8:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  7:18 Problem with new --physdev-out style Volker Sauer
2007-10-24  7:38 ` 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
2007-10-24 15:18               ` Volker Sauer
2007-10-24  9:28     ` Philip Craig
2007-10-24  8:36 ` Pascal Hambourg [this message]

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=471F040F.7040607@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.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