Ethernet Bridge development
 help / color / mirror / Atom feed
From: Jonathan Thibault <jonathan@navigue.com>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] ebtables/iptables ambiguity
Date: Tue, 22 Dec 2009 16:08:29 -0500	[thread overview]
Message-ID: <4B31354D.3080805@navigue.com> (raw)

I am trying to use connmark based on the bridge output port.

Normally, I would:

...
iptables -t mangle -A VMARK -i out -m physdev --physdev-out in.15 -j MARK --or-mark 0x00F
...
iptables -t mangle -A VMARK -j CONNMARK --save-mark

(VMARK is called in -t mangle POSTROUTING)

But since this traffic is routed and not bridged, I get the expected:

"physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore."

Now I could use ebtables to perform the mark in, say, filter FORWARD, but would it know which member interface the packets are going if the traffic is not being bridged?  And if so, would the mark appear in time for me to -j CONNMARK --save-mark in POSTROUTING/VMARK?

I obviously could try it to see if it works, but I'd rather *understand* what I'm doing first ;)

Jonathan

             reply	other threads:[~2009-12-22 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 21:08 Jonathan Thibault [this message]
2009-12-22 21:32 ` [Bridge] ebtables/iptables ambiguity richardvoigt
2009-12-22 21:43 ` Nicolas de Pesloüan

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=4B31354D.3080805@navigue.com \
    --to=jonathan@navigue.com \
    --cc=bridge@lists.linux-foundation.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