># core2a:
> flags: * = Valid, > = Selected, I = via IBGP, A = Announced
> origin: i = IGP, e = EGP, ? = Incomplete
>
> flags destination gateway lpref med aspath origin
> AI*> 194.143.152.0/23 0.0.0.0 100 0 21178 i
>
># core2b:
> flags: * = Valid, > = Selected, I = via IBGP, A = Announced
> origin: i = IGP, e = EGP, ? = Incomplete
>
> flags destination gateway lpref med aspath origin
> I*> 194.143.152.0/23 159.148.214.98 100 0 i
>
>
>Yet my upstream still prefers core2a as correct route to our network. I
>noticed, that only core2a networks have "announced" flag, is that right?
>Any other ideas what could be wrong?
I've just upgraded both routers to 4.9, updated filters to 4.9 defaults,
but the problem still remains. Nothing has changed regarding path to
upstream ISP.
Filtering rules now look like this:
match from 159.148.214.101 set { prepend-neighbor 1 }
match to 159.148.214.101 set { prepend-self 1 }
deny from any
deny to any
allow from any inet prefixlen 8 - 24
allow from any inet6 prefixlen 16 - 48
allow to any prefix 194.143.152.0/23
deny from any prefix 0.0.0.0/8 prefixlen >= 8
deny from any prefix 10.0.0.0/8 prefixlen >= 8
deny from any prefix 127.0.0.0/8 prefixlen >= 8
deny from any prefix 169.254.0.0/16 prefixlen >= 16
deny from any prefix 172.16.0.0/12 prefixlen >= 12
deny from any prefix 192.0.2.0/24 prefixlen >= 24
deny from any prefix 192.168.0.0/16 prefixlen >= 16
deny from any prefix 198.18.0.0/15 prefixlen >= 15
deny from any prefix 198.51.100.0/24 prefixlen >= 24
deny from any prefix 203.0.113.0/24 prefixlen >= 24
deny from any prefix 224.0.0.0/4 prefixlen >= 4
deny from any prefix 240.0.0.0/4 prefixlen >= 4
deny from any prefix ::/8 prefixlen >= 8
deny from any prefix 2001:2::/48 prefixlen >= 48
deny from any prefix 2001:10::/28 prefixlen >= 28
deny from any prefix 2001:db8::/32 prefixlen >= 32
deny from any prefix 3ffe::/16 prefixlen >= 16
Peter
