Routes received from another AS marked as IGP

[Marcio]

Benghozi,

Thanks for the answer. You clarified the question.

2018-09-13 12:52 GMT-03:00 Olivier Benghozi <olivier.benghozi at wifirst.fr>:

> This is the (now completely useless) mandatory ORIGIN attribute in BGP. It
> can be either IGP, EGP, or INCOMPLETE. It was used in prehistoric times to
> allow proper transition from EGP to BGP.
> Actually it has nothing to do with IGP today. BGP implementations can mark
> redistributed routes as IGP (BIRD, Juniper) or as INCOMPLETE (Cisco,
> Quagga, and others).
>
> See https://tools.ietf.org/html/rfc4271#section-4.3
> and https://bird.network.cz/pipermail/bird-users/2018-June/012380.html
>
> A best practice is most probably to mark/left everything as Origin=IGP in
> order to completely ignore this (now useless) attribute in the BGP path
> selection algo.
>
> Le 13 sept. 2018 à 16:49, Marcio <marciovinicius.santos at uniriotec.br> a
> écrit :
>
> Dear,
>
> I have a topology where each AS is represented by a BIRD router. But in
> the BIRD table of the routers. The announcements received are marked as IGP
> but all the BGP sessions are done between different ASes. Do you know why
> it occur? Follow an example about a prefix announced by two different ASes
> and marked as IGP origin in a third one.
>
> 10.3.1.0/24          unicast [SDNRTR 13:18:10.201] * (100) [AS65507i]
>         via 192.168.1.1 on eth0
>         Type: BGP univ
>         BGP.origin: *IGP*
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180913/fec4aa80/attachment.html>