BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

[Ondrej Zajicek]

On Tue, Jun 26, 2018 at 08:23:37PM +0000, Thiruvazhiyan Lakshmanan wrote:
> Hi Ondrej,
> Thanks for your advice, with the updated iproute2 package, I can see the mpls routes in the table now.
> I need another help now, I am trying to advertise the loopback interface addresses to the labeled unicast BGP peer with label value of 3 (Implicit null), but unable to do it. I am trying to create a static label route and advertise to the label unicast bgp peer, but I still see the routes received in the unicast table in the peer.
> ...
> protocol static static4 {
>         ipv4;
>         route 10.10.100.10/32 via 10.10.101.38 mpls 3;
> }

Hi

This does not work, because "via IP mpls X" means that labes X is label
assigned by IP. That label is announced when IP is announced as
bgp_next_hop, but when 'next hop self' is used (or when local address is
used as bgp_next_hop for other reasons) then local label (instead of
label of IP) must be used, but BIRD currently does not support local
label assignment, and such route is ignored.

Attached patch fixes it so BIRD will use implicit-NULL automatically
when route is announced with local next hop via MPLS-BGP.

Compile BIRD with it.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mpls.patch
Type: text/x-diff
Size: 962 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180701/a38438a6/attachment.bin>