Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Hai Wang" <hwang@finepoint.com>
Cc: <netdev@vger.kernel.org>, <bridge@linux-foundation.org>
Subject: Re: brctl issue
Date: Thu, 8 Mar 2007 13:14:25 -0800	[thread overview]
Message-ID: <20070308131425.3f31c811@freekitty> (raw)
In-Reply-To: <DE026503646E7F40AF97BAB98334333B267A1B@uss-republic.finepoint.com>

On Wed, 7 Mar 2007 22:30:09 -0500
"Hai Wang" <hwang@finepoint.com> wrote:

> Hello,
>  
>      I have a question regarding brctl and br2684, I have a network scenrio where I have to add br2684-rt into a bridge. but I could not do so with brctl, please let me if you have any suggestion on the issue.
>  
> My scenario :
>  
>                                        (vpi/vci) 
>       192.168.2.16             0/32               nas0
>     DSLAM1 (BR2684-rt)  --------------|-----------------
>        192.168.3.26            0/33                |                         |                                    192.168.1.18
>     DSLAM 2(BR2684-rt)  --------------| nas1 (LINUX)  Eth0     -----------------PC1 (OAM)
>         192.168.4.36            0/34               |                         |
>     DSLAM 3(BR2684-rt)  --------------|nas2------------
>  
>  
>     I want to put nas0, nas1, nas2 and eth0 on a bridge so that PC1 is able to communicate with DSLAMS.
>  
>  
>   Note that we do not want to assign any IP on nas0, nas1 and nas2.
>  
>  
> Please help with your suggestion.
>  

There is support for ATM bridging but never tried it (don't have ATM)
Did you look at?

	http://home.regit.org/?page_id=8
-- 
Stephen Hemminger <shemminger@linux-foundation.org>

      reply	other threads:[~2007-03-08 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  0:03 [PATCH] bridge: adding new device to bridge should enable if up Stephen Hemminger
2007-03-08  0:12 ` David Miller
2007-03-08  3:30 ` brctl issue Hai Wang
2007-03-08 21:14   ` Stephen Hemminger [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=20070308131425.3f31c811@freekitty \
    --to=shemminger@linux-foundation.org \
    --cc=bridge@linux-foundation.org \
    --cc=hwang@finepoint.com \
    --cc=netdev@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