From: Colin Barber (Colin.Barber@xxxxxxxxxxxxxx)
Date: Wed Jul 24 2002 - 19:11:22 GMT-3
Would you not need to specify mac-exclusive? Otherwise R1 will send
explorers to R2 for any mac addresses not listed in the icanreach.
How about not restricting within DLSW and just using a input-address-list
filter on the lan interface?
Colin
-----Original Message-----
From: Jaspreet Bhatia [mailto:jasbhati@cisco.com]
Sent: 24 July 2002 18:53
To: atul pawar
Cc: ccielab@groupstudy.com
Subject: Re: dmac-output-list question
Hi Atul,
This concept is a bit confusing . This is how I
interpret it . R2 wants all other hosts to only reach a certain range of
MAC addresses on its network. If you use dmac output list on R1 it would
affect only R1 whereas if you put the icanreach mac-address with a mask on
R2 , then R2 will advertise this to all other peers in its capabilities
exchange so all other peers will only send packets destined for those
range of MAC addresses to R@ .
HTH
Jaspreet
At 05:26 PM 7/24/2002 +0000, atul pawar wrote:
>HI Guyes,
>I saw this example on the group earlier. I seem to confuse myself with
>this one. Please Consider the following
>
>r1-------peer---------r2
>and r2 has a specific mac address range which should be allowed to
>communicate with outside world and all other mac should be filtered.
>
>now if I put this dmac-output-list allowing this range in the remote peer
>statement of r1 it will only pass those explorers which are for this mac
>address range.
>Or it should be on r2 so that it allows only these mac addresses out?
>Other way I can think of is dlsw icanreach mac-address on r2 and
mac-exclusive.
>can someone please clarify how to use 'dmac-output-list' as I'm not sure
>if my understanding is right .
>Many thanks For Your help
>Atul
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Atul
>
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:42 GMT-3