Direct protocol affects BGP

Fabiano D'Agostino fabiano.dagostino96 at gmail.com
Mon Mar 23 16:01:40 CET 2020


Hi Benedikt,
I am just learning Bird and I didn't want to use the Direct protocol
because using it I have two same routes in the RIB for the directly
connected networks, one coming from the kernel and the second one coming
from the direct protocol.

Il giorno lun 23 mar 2020 alle ore 16:01 Fabiano D'Agostino <
fabiano.dagostino96 at gmail.com> ha scritto:

> Hi Benedikt,
> I am just learning Bird and I didn't want to use the Direct protocol
> because using it I have two same routes in the RIB for the directly
> connected networks, one coming from the kernel and the second one coming
> from the direct protocol.
>
> Il giorno lun 23 mar 2020 alle ore 15:38 Benedikt Neuffer <
> benedikt.neuffer at kit.edu> ha scritto:
>
>> Hi Fabiano,
>>
>> that should be the reason. The TCP connection is done via RIB (kernel
>> routing table). In FIB (birds internal table) the route is currently
>> missing.
>> If you enable the direct protocol a route for  192.168.2.22 will be
>> appear in the FIB and the nexthop resolution will work.
>>
>> Is there a reason why you don't want to use the direct protocol?
>>
>> Regards,
>> Benedikt
>>
>> On 23.03.20 14:46, Fabiano D'Agostino wrote:
>> > Hi,
>> > thanks for helping,
>> > I did show route for 192.168.2.22 (which is my neighbor) table all all
>> > --> I get Network not found.
>> > show protocols: bgp established
>> > show protocol all bgp1: 0 imported, 0 exported
>> >
>> >
>> > Il giorno lun 23 mar 2020 alle ore 14:18 Benedikt Neuffer
>> > <benedikt.neuffer at kit.edu <mailto:benedikt.neuffer at kit.edu>> ha
>> scritto:
>> >
>> >     Hi Fabio,
>> >
>> >     so the routes are in FIB (kernel) but maybe not in RIB (bird).bb
>> >
>> >     Can you provide me the output of "show route for <prefix> table all
>> all"
>> >     where <prefix> should be the prefix configured on the connection or
>> the
>> >     ip address of the neighbor.
>> >
>> >     Regards,
>> >     Bene
>> >
>> >     On 23.03.20 12:43, Fabiano D'Agostino wrote:
>> >     > Hi Benedikt,
>> >     > the nexthop is resolvable, indeed router1 can ping router2'nic in
>> the
>> >     > same network of router1, with direct protocol disabled. The
>> >     scenario is:
>> >     > PCa - R1 - R2 - PCb
>> >     > With direct protocol enabled and bgp working: PCa can ping PCb
>> >     > With direct protocol disabled and bgp working: PCa can't ping PCb
>> >     >
>> >     >
>> >     > Il giorno lun 23 mar 2020 alle ore 12:26 Benedikt Neuffer
>> >     > <benedikt.neuffer at kit.edu <mailto:benedikt.neuffer at kit.edu>
>> >     <mailto:benedikt.neuffer at kit.edu <mailto:benedikt.neuffer at kit.edu
>> >>>
>> >     ha scritto:
>> >     >
>> >     >     Hi Fabio,
>> >     >
>> >     >     the BGP nexthop field must be resolvable. In other words there
>> >     must be a
>> >     >     route to the neighbor in RIB.
>> >     >
>> >     >     Regards,
>> >     >     Bene
>> >     >
>> >     >
>> >     >     On 23.03.20 12:05, Fabiano D'Agostino wrote:
>> >     >     > Hi all,
>> >     >     > why if I disable the direct protocol the BGP routes are not
>> >     >     > imported/exported? If I run show route, it is empty, while
>> >     if I enable
>> >     >     > the direct protocol show route has directly connected
>> routes and
>> >     >     BGP routes.
>> >     >     > My configuration is very easy, two routers make a eBGP
>> >     peering and
>> >     >     they
>> >     >     > import and export all routes. I am using Bird 2.0.7.
>> >     >     >
>> >     >     > Thanks,
>> >     >     >
>> >     >     > Fabiano
>> >     >
>> >     >
>> >     >     --
>> >     >     Karlsruher Institut für Technologie (KIT)
>> >     >     Steinbuch Centre for Computing (SCC)
>> >     >
>> >     >     Benedikt Neuffer
>> >     >     Netze und Telekommunikation (NET)
>> >     >
>> >     >     Hermann-von-Helmholtz-Platz 1
>> >     >     Gebäude 442
>> >     >     Raum 185
>> >     >     76344 Eggenstein-Leopoldshafen
>> >     >
>> >     >     Telefon: +49 721 608-24502
>> >     >     Fax: +49 721 608-47763
>> >     >     E-Mail: benedikt.neuffer at kit.edu
>> >     <mailto:benedikt.neuffer at kit.edu> <mailto:benedikt.neuffer at kit.edu
>> >     <mailto:benedikt.neuffer at kit.edu>>
>> >     >     Web: https://www.scc.kit.edu
>> >     >
>> >     >
>> >     >
>> >     >     Sitz der Körperschaft:
>> >     >     Kaiserstraße 12, 76131 Karlsruhe
>> >     >
>> >     >
>> >     >
>> >     >     KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft
>> >     >
>> >     >
>> >     >
>> >     >     Signaturversion: 19.1.0 beta
>> >     >
>> >
>> >
>> >     --
>> >     Karlsruher Institut für Technologie (KIT)
>> >     Steinbuch Centre for Computing (SCC)
>> >
>> >     Benedikt Neuffer
>> >     Netze und Telekommunikation (NET)
>> >
>> >     Hermann-von-Helmholtz-Platz 1
>> >     Gebäude 442
>> >     Raum 185
>> >     76344 Eggenstein-Leopoldshafen
>> >
>> >     Telefon: +49 721 608-24502
>> >     Fax: +49 721 608-47763
>> >     E-Mail: benedikt.neuffer at kit.edu <mailto:benedikt.neuffer at kit.edu>
>> >     Web: https://www.scc.kit.edu
>> >
>> >
>> >
>> >     Sitz der Körperschaft:
>> >     Kaiserstraße 12, 76131 Karlsruhe
>> >
>> >
>> >
>> >     KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft
>> >
>> >
>> >
>> >     Signaturversion: 19.1.0 beta
>> >
>>
>>
>> --
>> Karlsruher Institut für Technologie (KIT)
>> Steinbuch Centre for Computing (SCC)
>>
>> Benedikt Neuffer
>> Netze und Telekommunikation (NET)
>>
>> Hermann-von-Helmholtz-Platz 1
>> Gebäude 442
>> Raum 185
>> 76344 Eggenstein-Leopoldshafen
>>
>> Telefon: +49 721 608-24502
>> Fax: +49 721 608-47763
>> E-Mail: benedikt.neuffer at kit.edu
>> Web: https://www.scc.kit.edu
>>
>>
>>
>> Sitz der Körperschaft:
>> Kaiserstraße 12, 76131 Karlsruhe
>>
>>
>>
>> KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft
>>
>>
>>
>> Signaturversion: 19.1.0 beta
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20200323/150bea2d/attachment.htm>


More information about the Bird-users mailing list