Is it a known design quirk that route filters do not apply to reflected prefixes on a RouterOS route reflector?
We have filters in place to change local preference when processing prefixes from another region so that local preference results in the following preference order:
- Local customers
- Remote customers
- Local peers
- Remote peers
- Local transit
- Remote transit
Sample route filter entries from a RouterOS route reflector:
Code: Select all
add bgp-local-pref=150 chain=peer-rr-regional-in set-bgp-local-pref=130
add bgp-local-pref=149 chain=peer-rr-regional-in set-bgp-local-pref=129
add bgp-local-pref=148 chain=peer-rr-regional-in set-bgp-local-pref=128
add bgp-local-pref=147 chain=peer-rr-regional-in set-bgp-local-pref=127
add bgp-local-pref=146 chain=peer-rr-regional-in set-bgp-local-pref=126
add bgp-local-pref=145 chain=peer-rr-regional-in set-bgp-local-pref=125
Sample router filter entries from a FRRouting route reflector:
Code: Select all
route-map peer-rr-regional-in permit 100
match local-preference 150
on-match goto 1000
set local-preference 130
!
route-map peer-rr-regional-in permit 110
match local-preference 149
on-match goto 1000
set local-preference 129
!
route-map peer-rr-regional-in permit 120
match local-preference 148
on-match goto 1000
set local-preference 128
!
route-map peer-rr-regional-in permit 130
match local-preference 147
on-match goto 1000
set local-preference 127
!
route-map peer-rr-regional-in permit 140
match local-preference 146
on-match goto 1000
set local-preference 126
!
route-map peer-rr-regional-in permit 150
match local-preference 145
on-match goto 1000
set local-preference 125
!
Resulting routing table on a route reflector client:
Code: Select all
[admin@testing] > ip route print detail where dst-address=41.217.247.0/24
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
0 ADb dst-address=41.217.247.0/24 pref-src=10.0.11.1 gateway=10.0.66.1 gateway-status=10.0.66.1 recursive
via 192.0.2.229 vlan3 distance=200 scope=40 target-scope=30 bgp-as-path="37482" bgp-local-pref=150
bgp-origin=igp bgp-communities=64500:1002 received-from=RouterOS_RR1
1 Db dst-address=41.217.247.0/24 pref-src=10.0.11.1 gateway=10.0.66.1 gateway-status=10.0.66.1 recursive
via 192.0.2.229 vlan3 distance=200 scope=40 target-scope=30 bgp-as-path="37482" bgp-local-pref=150
bgp-origin=igp bgp-communities=64500:1002 received-from=RouterOS_RR2
2 Db dst-address=41.217.247.0/24 pref-src=10.0.11.1 gateway=10.0.66.1 gateway-status=10.0.66.1 recursive
via 192.0.2.229 vlan3 distance=200 scope=40 target-scope=30 bgp-as-path="37482" bgp-local-pref=130
bgp-med=0 bgp-origin=igp bgp-communities=64500:1002 received-from=FRR_RR1
3 Db dst-address=41.217.247.0/24 pref-src=10.0.11.1 gateway=10.0.66.1 gateway-status=10.0.66.1 recursive
via 192.0.2.229 vlan3 distance=200 scope=40 target-scope=30 bgp-as-path="37482" bgp-local-pref=130
bgp-med=0 bgp-origin=igp bgp-communities=64500:1002 received-from=FRR_RR2
Regards
David Herselman