From: ChrisH (chrish@xxxxxxxx)
Date: Thu Jan 11 2001 - 00:32:01 GMT-3
All ethernet ports are treated as s single entity (Ethernet bridge group).
So if you have a router with multiple Ethernet ports they will be treated as
one.
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Atif Awan
Sent: Thursday, January 11, 2001 3:21 AM
To: Simon.Baxter@au.logical.com; rwebber@callisma.com;
ccielab@groupstudy.com
Subject: RE: DLSw
I just did a dlsw port-list 1 ? and it showed ethernet interface ... it even
accepts it so i guess it should work .. but then havent tried it on a router
with both an ethetnet and a token ring ... will do that and let you know.
>From: Simon Baxter <Simon.Baxter@au.logical.com>
>To: Rob Webber <rwebber@callisma.com>, 'Atif Awan' <atifawan@hotmail.com>,
>ccielab@groupstudy.com
>Subject: RE: DLSw
>Date: Thu, 11 Jan 2001 13:12:45 +1100
>
>I thought the port list couldn't work for ethernet?
>
>I thought ethernet must be tied to a bridge group and that bridge group
>tied
>to a dlsw remote peer.
>
>Can anyone clarify this?
>
>-----Original Message-----
>From: Rob Webber [mailto:rwebber@callisma.com]
>Sent: Thursday, January 11, 2001 4:37 AM
>To: 'Atif Awan'; ccielab@groupstudy.com
>Subject: RE: DLSw
>
>
>How about using port-lists? Port lists should limit the ports a remote
>router can reach on the central site (where the list is applied). How
>about:
>
>hostname Router2
>!
>dlsw remote-peer 1 tcp <Router1>
>dlsw remote-peer 3 tcp <Router3>
>!
>dlsw port-list 1 <Router2's ether>
>dlsw port-list 3 <Router2's ring1>
>
>(and also don't create a dlsw peer between router1 and router3)
>
>Rob.
> >
> >Let me try to make this a little clear :
> >
> >Router 1 --------- Router2 ---------- Router 3
> > | | | |
> >ether ether ring1 ring 2
> >
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:27 GMT-3