From: Muralidhar Devarasetty (dhar_murali@xxxxxxxxxxx)
Date: Thu Feb 17 2000 - 12:10:46 GMT-3
Vijay,
when U are applying on interface using some access-lists or
access-expressions use based on interface.I mean if U are applying in eth
use ethernet style if U are applying on tr use token style.
The problem is when U are using dlsw.
As far as I understand DLSW converts the MAC in to tr form and this happens
wherever U mentioned dlsw bridge group is specified. (I mean this is the box
where translatonal bridging takes place).
So If U want to write dmac-list associate with dlsw remote-peer and the
filtering is for etherenet traffic , convert it ot tr form and then apply
it.
Murali, CCIE#5497
----Original Message Follows----
From: "Vijaykrishna" <vijaykrishna@netzero.net>
Reply-To: "Vijaykrishna" <vijaykrishna@netzero.net>
To: <ccielab@groupstudy.com>
Subject: MAC addr filter
Date: Wed, 16 Feb 2000 21:29:31 -0500
As per my understanding the MAC address is in canonical format on Ethernet
and in non-canonical in TR/FDDI. Also the DLSw carries the MAC in
non-canonical format ( any comments ??? )
Does any one has a rule of thumb to configure the MAC address filter on eth
i/f, TR i/f, on bridge-group and on DLSw remote-peer statement ? What I need
to know is which type of MAC filtering (canonical/ non-canonical) for each
of these scenarios ?
( Also for TR the mask should start with 8000.... I believe to cater for
RII )
thanks,
Vijay
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:53 GMT-3