From: Atif Awan (atifawan@xxxxxxxxxxx)
Date: Thu Jan 11 2001 - 06:09:02 GMT-3
Now this is confusing me. The documentation says that it only works for
token ring and serial interfaces. But when you do a ? it shows ethernet too.
I have a router with two ethernet interfaces and it allows me to add each of
them separately to two different port lists. Can you explain this ? will it
work ?
Thanks
Atif
>From: "Michelle T" <mtruman@mn.mediaone.net>
>To: "Atif Awan" <atifawan@hotmail.com>, <chrish@bjen.com>,
><Simon.Baxter@au.logical.com>, <rwebber@callisma.com>,
><ccielab@groupstudy.com>
>Subject: Re: DLSw
>Date: Thu, 11 Jan 2001 00:06:04 -0600
>
>It does allow the ethernet, but if you have multiple ethernets, it allows
>all of them. The ethernet is one big logical port to DLSW known as the
>bridge group. So you can't deny one ethernet and permit another.
>----- Original Message -----
>From: "Atif Awan" <atifawan@hotmail.com>
>To: <mtruman@mn.mediaone.net>; <chrish@bjen.com>;
><Simon.Baxter@au.logical.com>; <rwebber@callisma.com>;
><ccielab@groupstudy.com>
>Sent: Thursday, January 11, 2001 5:00 AM
>Subject: Re: DLSw
>
>
> >
> > well i read that too but then when i did a ? on the options i could see
>the
> > ethernet interface listed there. Maybe it accepts ethernet but does not
> > implement the port list functionality to it ... cannot say anything
>without
> > testing it though.
> >
> > regards
> > atif
> >
> > >From: "Michelle T" <mtruman@mn.mediaone.net>
> > >To: "Atif Awan" <atifawan@hotmail.com>, <chrish@bjen.com>,
> > ><Simon.Baxter@au.logical.com>, <rwebber@callisma.com>,
> > ><ccielab@groupstudy.com>
> > >Subject: Re: DLSw
> > >Date: Wed, 10 Jan 2001 22:54:19 -0600
> > >
> > >Straight from the doc CD:
> > >
> > >DLSw+ port lists map traffic on a local interface (either Token Ring or
> > >serial) to remote peers. Port lists do not work with Ethernet
>interfaces,
> > >or
> > >any other interface types connected to DLSw+ by means of a bridge
>group.
> > >You
> > >can create a port list of local ports and apply the list to remote peer
> > >definitions. Traffic received from a remote peer is only forwarded to
>peers
> > >if the input port number appears in the port list applied to the remote
> > >peer
> > >definition. The port list command provides a single command to specify
>both
> > >serial and Token Ring interfaces. Figure 99 shows how port lists are
>used
> > >to
> > >map traffic.
> > >
> >
> >http://cio.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/ibm_
>c
> > >/bcprt2/bcdlsw.htm#xtocid75214
> > >----- Original Message -----
> > >From: "Atif Awan" <atifawan@hotmail.com>
> > >To: <chrish@bjen.com>; <Simon.Baxter@au.logical.com>;
> > ><rwebber@callisma.com>; <ccielab@groupstudy.com>
> > >Sent: Thursday, January 11, 2001 3:52 AM
> > >Subject: RE: DLSw
> > >
> > >
> > > >
> > > > I disagree with this. Using the port-list command you can restrict
> > > > individual ethenet ports too.
> > > >
> > > > >From: "ChrisH" <chrish@bjen.com>
> > > > >Reply-To: <chrish@bjen.com>
> > > > >To: "Atif Awan" <atifawan@hotmail.com>,
><Simon.Baxter@au.logical.com>,
> > > > ><rwebber@callisma.com>, <ccielab@groupstudy.com>
> > > > >Subject: RE: DLSw
> > > > >Date: Wed, 10 Jan 2001 22:32:01 -0500
> > > > >
> > > > >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