From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Wed, 17 Dec 2014 10:56:36 -0600 (CST) [thread overview]
Message-ID: <6072563.350672.1418835396663.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <CAA5aLPi--5H-+SVDvv9tDc7SNSnYtxpW1rAStAhQrgr0qpwHOw@mail.gmail.com>
----- Original Message -----
> Its not about finding a workaround or something.
>
> If we bridge two vlans on the same interface, then what should be the
> VLAN-tag on the packets moving out of the box? As it might not be
> possible to decide this, thats why we cannot bridge two vlans on the
> same interface.
>
My assumption (wrongful?) would be some sort of state tracking wherein the kernel notes the interface the traffic is sourced from, and return traffic goes back via the same path (including layer 2 characteristics including VLAN ID).
--Tim
next prev parent reply other threads:[~2014-12-17 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4829673.301498.1418414563731.JavaMail.root@rockbochs.com>
2014-12-12 20:03 ` Bridging / VLANs / ebtables Tim Nelson
2014-12-16 1:20 ` Tim Nelson
2014-12-16 9:01 ` Akshat Kakkar
2014-12-16 14:56 ` Paul Robert Marino
2014-12-16 21:16 ` Tim Nelson
2014-12-16 21:15 ` Tim Nelson
2014-12-16 21:34 ` Jason Cooper
2014-12-16 21:46 ` Tim Nelson
2014-12-17 2:41 ` Jason Cooper
2014-12-17 16:40 ` Tim Nelson
2014-12-22 3:37 ` Tim Nelson
2014-12-17 2:55 ` Jason Cooper
2014-12-17 4:41 ` Akshat Kakkar
2014-12-17 16:56 ` Tim Nelson [this message]
2014-12-17 16:51 ` Tim Nelson
[not found] <549119ce.ca25e00a.053d.1a62@mx.google.com>
2014-12-17 17:30 ` Tim Nelson
[not found] <CAPJdpdD+Ziiy_keV=Re92-v53PtMA8N7XK6rKXYHvzj3QJcOQg@mail.gmail.com>
2014-12-22 15:24 ` Tim Nelson
2014-12-22 21:15 ` Paul Robert Marino
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=6072563.350672.1418835396663.JavaMail.root@rockbochs.com \
--to=tnelson@rockbochs.com \
--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