netdev - Re: brctl issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20070308131425.3f31c811@freekitty>
Date:	Thu, 8 Mar 2007 13:14:25 -0800
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	"Hai Wang" <hwang@...epoint.com>
Cc:	<netdev@...r.kernel.org>, <bridge@...ux-foundation.org>
Subject: Re: brctl issue

On Wed, 7 Mar 2007 22:30:09 -0500
"Hai Wang" <hwang@...epoint.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@...ux-foundation.org>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html