Usually, I use to avoid some well-know destination mac frames could will be processed by DLSW process on ethernet routers using bridge group x input-pattern-list (1100-1199):
dlsw local-peer peer-id xxx.xxx.xxx.xxx
dlsw remote-peer 0 tcp yyy.yyy.yyy.yyy
dlsw bridge-group 5
interface Ethernet0/0
bridge-group 5
bridge-group 5 input-pattern-list 1100
access-list 1100 deny 0000.0000.0000 ffff.ffff.ffff 0300.8000.0000 0000.0000.00ff
access-list 1100 deny 0000.0000.0000 ffff.ffff.ffff 0300.4000.0000 0000.0000.0000
access-list 1100 deny 0000.0000.0000 ffff.ffff.ffff 0300.2000.0000 0000.0000.0000
access-list 1100 deny 0000.0000.0000 ffff.ffff.ffff 0300.0200.0000 0000.0000.0000
access-list 1100 deny 0000.0000.0000 ffff.ffff.ffff 0300.0800.0000 0000.0000.0000
access-list 1100 permit 0000.0000.0000 ffff.ffff.ffff 0000.0000.0000 ffff.ffff.ffff
My doubt is how can I this with token ring interfaces, or how can I use extended access-list to filter incoming frames?
This is a sample configuration with Token Ring:
source-bridge ring-group z
dlsw local-peer peer-id xxx.xxx.xxx.xxx
dlsw remote-peer 0 tcp yyy.yyy.yyy.yyy
interface TokenRing0/0
ip address ....
ring-speed 16
multiring all
source-bridge 26 12 2000
source-bridge spanning