Hi Nigel,
Firstly, thanks for your help on this question. But I think if using
dmac-output-list, it should be done on R2 to control only the
specified mac on Ring 1 it talking to hosts on Ring 2.
Just curious (and been picky), it there any way of just configuring on
R1 to achieve this?
On 3 Apr 2001 09:40:49 -0400, [EMAIL PROTECTED] ("Nigel
Taylor") wrote:
>Clueless,
> You should be able to do this using the dmac-ouput-list option
>defined with
>your "dlsw remote-peer" statement with R2. This would identify the MAC's
>you'd like
>to filter by ACL 700-799.. ie..
>
>R1:
>
>dlsw local-peer peer-id 1.1.1.1 <--- local token ring interface
>dlsw remote-peer 0 tcp 2.2.2.2 dmac-output-list 701 <--- Peer statement
>for R2's token ring interface.
>
>access 701 permit 3000.3000.0000 0000.0000.FFFF
>
>HTH
>
>Nigel..
>----- Original Message -----
>From: Clue Less <[EMAIL PROTECTED]>
>Newsgroups: groupstudy.cisco
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, April 03, 2001 7:47 AM
>Subject: DLSW filtering
>
>
>> Hi all,
>>
>> Got a question on DLSW filtering. Say all interfaces below are
>> configured for DLSW (ie e0 and tok 0 of R1, e0 and tok 0 of R2).
>>
>> How to configure on R1 so that only hosts on Ring 1 with mac address
>> 3000.3000.XXXX can talk to hosts on Ring 2?
>>
>> Hosts on Ring 1 with other Mac address should still be able to talk to
>> hosts on e0 of R2.
>>
>> |-----------e0 R1 tok0-----------Ring 1
>> |
>> |
>> IP cloud
>> |
>> |
>> |-----------e0 R2 tok0-----------Ring 2
>>
>> Clue Less.
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
