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

[Thiruvazhiyan Lakshmanan]

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.

Below are my loopback interfaces,
root at ubuntu4-4-VM1:/usr/local/etc# ifconfig lo:1
lo:1      Link encap:Local Loopback
          inet addr:10.10.100.1  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:65536  Metric:1

root at ubuntu4-4-VM1:/usr/local/etc# ifconfig lo:10
lo:10     Link encap:Local Loopback
          inet addr:10.10.100.10  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:65536  Metric:1

root at ubuntu4-4-VM1:/usr/local/etc#

and below is my bird.conf file,

root at ubuntu4-4-VM1:/usr/local/etc# more bird.conf
router id 135.21.13.165;

ipv4 table master4;
ipv6 table master6;

#ipv4 table mtab4;
#ipv6 table mtab6;

protocol kernel {
        persist;
        scan time 10;
        ipv4 {
                export all;
                import all;
        };
}
protocol direct {
        ipv4 {
                export all;
                import all;
        };
        interface "-eth*", "*";
}

protocol device {
        scan time 10;           # Scan interfaces every 10 seconds
}
protocol static static4 {
        ipv4;
        route 10.10.100.10/32 via 10.10.101.38 mpls 3;
}

protocol bgp label_unicast{
        local 10.10.101.38 as 7018;        # Use a private AS number
        neighbor 10.10.101.37 as 7018;    # Our neighbor ...
        # IPv4 with MPLS labels (1/4)
        ipv4 mpls {
                import all;
                export where proto = "static4";
                next hop self; # advertise this router as next hop
        };
}
protocol bgp unicast{
        local 10.10.101.42 as 7018;        # Use a private AS number
        neighbor 10.10.101.41 as 7018;    # Our neighbor ...
        ipv4 {
                import all;
                export all;
                next hop self; # advertise this router as next hop
        };
}

root at ubuntu4-4-VM1:/usr/local/etc# ifconfig lo:1
lo:1      Link encap:Local Loopback
          inet addr:10.10.100.1  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:65536  Metric:1

root at ubuntu4-4-VM1:/usr/local/etc#

Regards, 
Thiruvazhiyan L

-----Original Message-----
From: Bird-users [mailto:bird-users-bounces at network.cz] On Behalf Of Ondrej Zajicek
Sent: Friday, June 15, 2018 7:46 PM
To: Thiruvazhiyan Lakshmanan
Cc: bird-users at network.cz
Subject: Re: BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

On Fri, Jun 15, 2018 at 02:27:52PM +0000, Thiruvazhiyan Lakshmanan wrote:
> Thanks for your reply.
> 
> When I tried to add " ip route add 192.168.1.0/24 encap mpls 100 via inet 10.10.101.1" I get "Error: either "to" is duplicate, or "encap" is a garbage."
> 
> root at ubuntu4-4-VM1:/proc/sys/net# ip route add 192.168.1.0/24 encap mpls 100 via inet 10.10.101.1
> Error: either "to" is duplicate, or "encap" is a garbage.
> root at ubuntu4-4-VM1:/proc/sys/net#

In that case you likely have too old iproute2 tools, so you would not see
mpls labels in 'ip route show'. You should get:

# ip route add 192.168.1.0/24 encap mpls 100 via inet 192.168.81.2
# ip route list
default via 192.168.81.1 dev eth0 
192.168.1.0/24  encap mpls  100 via 192.168.81.2 dev eth0 

-- 
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."
============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra.

============================================================================================================================