[From nobody Tue Apr 27 10:28:55 2004 Message-ID: <0A89B09D5909F94A96C5480667C6BE8936A1C4@star_academy.office.mactelecom.com> From: Vincent De Keyzer <vincent@dekeyzer.net> Sender: cisco-nsp-bounces@puck.nether.net To: cisco-nsp@puck.nether.net Subject: RE: [nsp] Bridging? Date: Tue, 27 Apr 2004 10:02:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) List-Help: <mailto:cisco-nsp-request@puck.nether.net?subject=help> List-Subscribe: <https://puck.nether.net/mailman/listinfo/cisco-nsp>, <mailto:cisco-nsp-request@puck.nether.net?subject=subscribe> List-Unsubscribe: <https://puck.nether.net/mailman/listinfo/cisco-nsp>, <mailto:cisco-nsp-request@puck.nether.net?subject=unsubscribe> X-MSMail-Priority: Normal X-Mailer: Normal X-MimeOLE: Normal X-MIME-Autoconverted: Normal X-BeenThere: Normal X-Mailman-Version: Normal Content-Type: text/plain (trying once again to get this working) I am not sure I was clear enough on the first shot. My idea is the following: 1. I currently have Cisco 2621 access routers, with E1 controllers and n x "CSU/DSU + Cisco 1600" at the other end as CPEs. On the ethernet port of the 1600 the customer typically hooks up his firewall (ISP environment). 2. I would like to replace "CSU/DSU + router" by "E1/Eth bridge" to which the customer would connect his FW. So far, all the schemes I have seen are putting the ethernet side of the 2621 (or 3640 in my previous example) into some sort of bridge or bridge group; IMHO this interface should not be modified: it's only the Serial links that would change. So instead of a router that routes between Fa0/0 and Serial0/0:0, Serial0/1:0, Serial1/0:0, etc. I would have a router that routes between Fa0/0 and BVI0, BVI1, BVI2, etc. (or something like that). The "BVI" interfaces having the IP address that was previously on the Ethernet interface of the CPE (/30 for PtP connection disappears). Is this making sense? Is this possible? Any help will be appreciated Thanks Vincent > -----Original Message----- > From: cisco-nsp-bounces@puck.nether.net > [mailto:cisco-nsp-bounces@puck.nether.net] On Behalf Of David Curran > Sent: jeudi 26 fevrier 2004 17:06 > To: cisco-nsp@puck.nether.net > Subject: RE: [nsp] Bridging? > > > If you're doing nothing but bridging (i.e. no routing) you > can do the following > > bridge 1 protocol ieee > bridge 1 irb > > int e0/0 > bridge 1 > > int s0/0:0 > bridge 1 > > If you need to route some other protocol, you'll need to add > > bridge 1 route <protocol> > ! > interface bvi 1 > <protocol options> > ! > > It should work just fine. Look at this link: > > http://tinyurl.com/yvhqh > > -david > > -----Original Message----- > From: cisco-nsp-bounces@puck.nether.net > [mailto:cisco-nsp-bounces@puck.nether.net]On Behalf Of > Vincent De Keyzer > Sent: Thursday, February 26, 2004 8:37 AM > To: cisco-nsp@puck.nether.net > Subject: [nsp] Bridging? > > > Hello guys, > > I am trying to do something without even knowing whether it's > possible or not (all I have is a vague promise of a sales guy > a few months ago :-). > > The set-up is as follows: > Cisco 3640 with VWIC-2MFT-E1 <----E1 link---> E1/Eth Bridge > <----> Ethernet station > > So what I am trying to do is to turn the E1 interface on the > Cisco (or, more exactly, Serial0/0:0) into an ethernet host > on a remote (i.e. beyond the E1 > link) network. > > Possible? > > I see problems already like: what will be the MAC address of > serial0/0:0 on the ethernet network? I have seen a > "mac-address" command in int. configuration mode; but before > jumping in this I thought I would ask the ones who know... > > So: > > 1. Is what I am trying to do completely irrealistic or not? > 2. If no, what commands do I need on the cisco? > > Note: on the bridge I can configure either PPP or HDLC; but > none of them could succeed to bring the line protocol up on > the cisco side (can produce the debugs if that helps). > > Vincent > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco> -nsp > archive at > http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco> -nsp > archive at > http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ]