RE: DLSw

From: Atif Awan (atifawan@xxxxxxxxxxx)
Date: Thu Jan 11 2001 - 00:00:38 GMT-3

• Next message: James Wilson: "Re: Trouble shooting"
• Previous message: McKenzie, Barry: "RE: Catalyst content on the lab."
• Maybe in reply to: Atif Awan: "DLSw"
• Next in thread: Atif Awan: "RE: DLSw"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

thanks ... this seems to be a better solution.

Regards
Atif

>From: "Rob Webber" <rwebber@callisma.com>
>Reply-To: <rwebber@callisma.com>
>To: "'Atif Awan'" <atifawan@hotmail.com>, <ccielab@groupstudy.com>
>Subject: RE: DLSw
>Date: Wed, 10 Jan 2001 13:37:15 -0500
>
>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
> >
>

• Next message: James Wilson: "Re: Trouble shooting"
• Previous message: McKenzie, Barry: "RE: Catalyst content on the lab."
• Maybe in reply to: Atif Awan: "DLSw"
• Next in thread: Atif Awan: "RE: DLSw"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:27 GMT-3