All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] help needed regarding configuration for bridging
Date: Mon, 13 Sep 2010 11:29:22 -0700	[thread overview]
Message-ID: <4C8E6D82.6020509@superduper.net> (raw)
In-Reply-To: <20100913075419.4d70f1c8@nehalam>

I think you're looking for more vlan capability than the current Linux 
bridging code has. I posted a patch a few years back to add vlan aware 
bridging to the kernel - it would be great if someone updated it to the 
current kernel. Here's a reference:

https://lists.linux-foundation.org/pipermail/bridge/2006-September/005046.html

Simon


On 09/13/2010 07:54 AM, Stephen Hemminger wrote:
> On Mon, 13 Sep 2010 15:11:21 +0530
> debasis das<fordebasis@gmail.com>  wrote:
>
>> Hi all,
>>          I have a Linux box with 3 interfaces eth0,eth1 and eth2.
>>          Could anyone please let me know whether the following configuration
>> would be valid :
>>
>> *#brctl addbr br1
>> #brctl addif br1 eth1
>> #ifconfig br1 up
>> # brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> br1             8000.001000000007       no              eth1
>>
>>
>> # brctl addbr br0
>> # brctl addif br0 eth0
>> # ifconfig br0 up
>> # vconfig add br0 5
>> # brctl addif br1 br0.5
>
> A bridge can not be added to a bridge.
>

      reply	other threads:[~2010-09-13 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  9:41 [Bridge] help needed regarding configuration for bridging debasis das
2010-09-13 14:54 ` Stephen Hemminger
2010-09-13 18:29   ` Simon Barber [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=4C8E6D82.6020509@superduper.net \
    --to=simon@superduper.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.