Does OSPF ABR Route Filtering work like it should?

RouterOS Forwarding Protocols
1

Hello,

according to http://blog.ine.com/2009/08/17/ospf-route-filtering-demystified/ , for OSPF area borders, the ABR should redistribute the routing table (filtered) from the backbone area into the other areas.
On my setup, the ABR would redistribute the whole OSPF Routing Database without filtering into the adjacent non-backbone area.

Flags: X - disabled 
 0   chain=ospf-in prefix=10.0.0.0/20 prefix-length=20-32 invert-match=no 
     action=discard set-bgp-prepend-path="" 

 1   chain=ospf-out prefix=10.0.0.0/20 prefix-length=20-32 invert-match=no 
     action=discard set-bgp-prepend-path="" 

 2   chain=ospf-in prefix=192.168.0.0/16 prefix-length=16-32 invert-match=no 
     action=discard set-bgp-prepend-path="" 

 3   chain=ospf-out prefix=192.168.0.0/16 prefix-length=16-32 invert-match=no 
     action=discard set-bgp-prepend-path=""




 #   NETWORK            AREA                                                     
 0   10.0.5.0/24        internal                                        
 1   172.16.2.0/24      backbone




 #    NAME                                   AREA-ID         TYPE    DEFAULT-COST
 0  * backbone                               0.0.0.0         default
 1    internal                               10.0.0.0         default

My solution was to deploy a second OSPF instance on the internal interface and redistribute other ospf with the same route filter, but I would really like to know what’s up with that.

2

Hello,

I did a similar test based on the multiarea example “http://wiki.mikrotik.com/wiki/Manual:OSPF_Case_Studies#Multi-area_networks” putting the filter on ABR (R1) exatly like you, for the 10.0.1.0/24 networks (ospf-in and ospf-out chains), which LSA is propagating form Backbone to AREA1. However it had not worked too.

I’m thiking that A)I’m doing something wrong or B) not understand the article of http://blog.ine.com/2009/08/17/ospf-route-filtering-demystified/ or C)this feature of filter LSA type 3 it’s not implemented at Mikrotik yet…