Hi forum,

I have a router that gets a connected route via ppp which is pretty standard. The issue is its redistributing that route (as connected route so lower cost) to other peers - its just a router ID so it does not affect customer traffic but causes weird issues and traceroutes when we monitor by that IP.

The obvious solution is to try and block it redistributing that route in filters but for the life of me I can't get it to stop advertising it. This is the 2 filters im trying to use (one more specific than the other) but neither seem to be working to filter this route out:
The instance definitely showing using the custom out filter (using standard ospf-out didn't work either, but this forces it to show in the config export):
I'm just at a loss on how to have this router NOT redistribute the PPP connected route.

Thanks.

is that on backbone area?
As far as i know filters doesn't work on that area

is that on backbone area?
As far as i know filters doesn't work on that area

Yes it all runs on a single area.

Why wouldn't filters work on backbone thats weird - i use ospf-in extensibly to re-write the pref-source without issue - do you have source on this? I can't find it in the wiki.

that is from my experience,
maye Guru will say something different than i did above

Not enough information. What type of LSAs you are trying to filter? RouterOS allows filtering only external

OSPF has many frustrating issues, this is one of them. All routers in an area need to agree on the routing table, this means you can't filter rules to another router in the same area. The rule is there for a reason but unfortunately it's just not suitable in many modern dynamically expanding networks. The only real IGP protocol MikroTik supports is OSPF so we're stuck with it until they implement IS-IS, EIGRP or another routing protocol gets developed and adopted

Your only solution is either BGP, or if viable and your network design permits, then put those routers into another area. The latter solution boxes you in and often creates issues down the track. However you at least don't need to have unique area numbers. You can have as many 'area1' routers as you want, they don't need to be joined to each other and they'll still be able to route as expected (you just can't expand beyond that area, as all area's need to connect to the backbone, so you can't do an Area0->Area1->Area2 design)

read above what mrz said, he gave you the answer.
He pointed out on backbone are.
If you want to filter other LSAs , than you need to use none-backbone area