/routing filter ?Cisco, Juniper, Huawei, Alcatel, etc... all have the option to create a "prefix-list" for filters. I'm surprised Mikrotik doesn't offer this option...
No option for prefix-list filters/routing filter ?Cisco, Juniper, Huawei, Alcatel, etc... all have the option to create a "prefix-list" for filters. I'm surprised Mikrotik doesn't offer this option...
what's your problem?
Similar feature is currently in development.
/routing filter add action=accept chain=Upstream-OUT prefix-list=MyPrefix /routing filter prefix-list add prefix=184.108.40.206/24 list=MyPrefix add prefix=220.127.116.11/24 list=MyPrefix add prefix=18.104.22.168/24 list=MyPrefix add prefix=22.214.171.124/24 list=MyPrefix
/routing filter add action=accept chain=as-65000-prefixes prefix=203.0.113.0/29 prefix-length=29-32 add action=accept chain=as-65000-prefixes prefix=203.0.113.8/29 prefix-length=29-32 add action=accept chain=as-65000-prefixes prefix=203.0.113.16/29 prefix-length=29-32 add action=accept chain=as-65000-prefixes prefix=203.0.113.24/29 prefix-length=29-32 add action=accept chain=as-65000-prefixes prefix=203.0.113.32/29 prefix-length=29-32
/routing filter add action=accept chain=peering-to-r2-out match-chain=as-65000-prefixes add action=discard chain=peering-to-r2-out
/routing bgp peer add name=R2 out-filter=peering-to-r2-out remote-address=100.126.0.2 remote-as=65001
[admin@R1] > routing bgp advertisements print PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF R2 203.0.113.32/29 100.126.0.1 incomplete R2 203.0.113.24/29 100.126.0.1 incomplete R2 203.0.113.16/29 100.126.0.1 incomplete R2 203.0.113.8/29 100.126.0.1 incomplete R2 203.0.113.0/29 100.126.0.1 incomplete [admin@R1] >
Thanks a lot, I do it and is working very fine.The option to do this is there, you just have to build more than one filter.