That looks different from the output in the first email. There best routes were received not only from ibgp, but from the same peer, so it seems ok that they were not sent back. For this output you have now session with your ibgp peer eatablished, but it still do not see the routes. Localpref should not affect exporting directly, yes. It can alter the best route, which will be considered for exporting. On Fri, May 17, 2024, 18:36 Nico Schottelius <nico.schottelius@ungleich.ch> wrote:
Hello Alexander,
the route is received via eBGP and should be redistributed via iBGP:
bird> show route all 49.14.107.0/24 Table master4: 49.14.107.0/24 unicast [outgoing_server120 16:13:14.594] * (100) [AS45271i] via 2a0a:e5c0:31:4::1 on tun1 Type: BGP univ BGP.origin: IGP BGP.as_path: 209898 15576 3356 55644 45271 BGP.next_hop: 2a0a:e5c0:31:4::1 fe80::2010:be9e:ed5f:ea08 BGP.local_pref: 50 BGP.atomic_aggr: BGP.aggregator: 10.100.230.241 AS65010 BGP.community: (3356,2) (3356,22) (3356,100) (3356,123) (3356,502) (3356,903) (3356,2112) (15576,100) (15576,102) (15576,1000) BGP.otc: 209898 unicast [outgoing_server121 16:13:14.700] (100) [AS45271i] via 2a0a:e5c0:32:4::1 on tun0 Type: BGP univ BGP.origin: IGP BGP.as_path: 209898 15576 3356 55644 45271 BGP.next_hop: 2a0a:e5c0:32:4::1 fe80::5cd3:b71c:f90a:b469 BGP.local_pref: 50 BGP.atomic_aggr: BGP.aggregator: 10.100.230.241 AS65010 BGP.community: (3356,2) (3356,22) (3356,100) (3356,123) (3356,502) (3356,903) (3356,2112) (15576,100) (15576,102) (15576,1000) BGP.otc: 209898
The only difference to other routers is that the bgp local preference is 50, but from my understanding it should still be exported via iBGP.
BR,
Nico
Alexander Zubkov <green@qrator.net> writes:
OK, I see that routes you showed have best from protocol ibgp. So I suppose they received from ibgp peer, and your are sending them to ibgp peer too. That is not allowed by default.
On Fri, May 17, 2024, 17:00 Nico Schottelius < nico.schottelius@ungleich.ch> wrote:
Ciao Alexander,
Alexander Zubkov <green@qrator.net> writes:
Hello,
Just curious. You've done "reload out" to your session after changing the filter, right?
this is a very good point, but in this case the whole bird daemon is restarted, so this should not be an issue.
BR,
Nico
-- Sustainable and modern Infrastructures by ungleich.ch