Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Tue, 16 Dec 2014 15:15:33 -0600 (CST)	[thread overview]
Message-ID: <1414006.345549.1418764533790.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <CAA5aLPhyZnMoMqSYkYA3YHHMs1UX-kLURLZW4UgBHotDVSmCRQ@mail.gmail.com>


----- Original Message -----
> I might not be correct. In my understanding an Interface can be a
> part
> of multiple vlans but it should not be possible to have all those
> vlan
> interfaces (on the same physical interface) in the same bridge.
> 
> Can you share some more details of why do you require such set up?
> What all are the connected devices and what is vlan config of each (I
> understand you cannot change this configuration)?
> 

Greetings-

The use case is a server connected to a switch (provided, not able to manage/configure), where it has access to three subnets, delivered via ethernet on the link untagged, and tagged in VLANs 2/3. I have a need to bridge the untagged parent interface (eth0) and VLAN 3 (eth0.3), while leaving the VLAN 2 interface (eth0.2) untouched.

Believe me, I understand this is an odd situation, but I'm very curious if it is possible using ebtables or some other filtering/manipulation application to make it work.

Thank you,

--Tim

  parent reply	other threads:[~2014-12-16 21:15 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 [this message]
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
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=1414006.345549.1418764533790.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