Force gateway recursive lookup in iBGP routes
Miroslav Kalina
miroslav.kalina at livesport.eu
Wed Mar 4 13:00:43 CET 2020
Wow, perfect. Thank you for clarifying this.
So iBGP sessions are multihop by default and all routes learned from
them are treated as "gateway recursive". As soon as I turned off
multihop feature with "direct" keyword (because there is nothing like
"multihop off") it's receiving routes in same manner as eBGP and it
started working.
Is there any way how to display routes (like "show route all") with
information which routes are treated as direct / recursive?
Thank you very much for your time.
Best regards
On 03. 03. 20 15:04, Ondrej Zajicek wrote:
> On Mon, Mar 02, 2020 at 08:24:19AM +0100, Miroslav Kalina wrote:
>> Thank you for your reply, I just don't understand it well enought.
>>
>> Why is route 10.96.20.0/26 recursive, when it's next hop (10.30.21.19)
>> is in my directly connected network (10.30.20.0/22) ?
> Because it is received by IBGP (okubedev1m1) and all IBGP routes are by
> default recursive, even if they are resolved using a direct route.
>
> If you configure okubedev1m1 as EBGP (or just set it to 'gateway direct'
> mode), it should fix the routes from okubedev1_lb1.
>
--
Miroslav Kalina
Systems development specialist
miroslav.kalina at livesport.eu
+420 773 071 848
Livesport s.r.o.
Aspira Business Centre
Bucharova 2928/14a, 158 00 Praha 5
www.livesport.eu
More information about the Bird-users
mailing list