MPLS Support Question

[t a]

An export filter on the kernel table would work, this was just the method we chose to standardize our configurations for policy routing so that we have a standard export policy from the main table and perform filtering and change route attributes within the pipes.

________________________________
From: Bird-users <bird-users-bounces at network.cz> on behalf of Maximilian Wilhelm <max at rfc2324.org>
Sent: Tuesday, March 20, 2018 7:11:19 AM
To: bird-users at network.cz
Subject: Re: MPLS Support Question

Anno domini 2018 t a scripsit:

> Thank you for the quick response.  What we are looking to do is assign a single label to routes when they are placed into a kernel table via a pipe.  For instance:
>
> protocol pipe master_to_kernelTable{
>         table kernelTable;
>         peer table master;
>         import filter{
>         if bgp_next_hop = 192.168.0.15 then {mpls 1000; accept;}
>         reject;
>         };
>         export none;
>         }
>
> We are looking to manually assign the labels according to our internal structure, so no label distribution is required, just the ability to assign a label to a route similar to how they are assigned to static routes.

Silly question: Why are you using a pipe protocol for that purpose?
Wouldn't an export filter within the kernel protocol suffice?

Best
Max
--
The real problem with C++ for kernel modules is:
the language just sucks.
-- Linus Torvalds
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180320/10a73dd0/attachment.html>