Re: [PATCH] rtnetlink: Add more well known protocol values

[Stephen Hemminger <stephen@networkplumber.org>]

On Wed, 30 May 2018 08:27:32 -0400
Donald Sharp <sharpd@cumulusnetworks.com> wrote:

> FRRouting installs routes into the kernel associated with
> the originating protocol.  Add these values to the well
> known values in rtnetlink.h.
> 
> Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
> ---
> v2: Fixed whitespace issues
>  include/uapi/linux/rtnetlink.h | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/include/uapi/linux/rtnetlink.h b/include/uapi/linux/rtnetlink.h
> index cabb210c93af..7d8502313c99 100644
> --- a/include/uapi/linux/rtnetlink.h
> +++ b/include/uapi/linux/rtnetlink.h
> @@ -254,6 +254,11 @@ enum {
>  #define RTPROT_DHCP	16      /* DHCP client */
>  #define RTPROT_MROUTED	17      /* Multicast daemon */
>  #define RTPROT_BABEL	42      /* Babel daemon */
> +#define RTPROT_BGP	186     /* BGP Routes */
> +#define RTPROT_ISIS	187     /* ISIS Routes */
> +#define RTPROT_OSPF	188     /* OSPF Routes */
> +#define RTPROT_RIP	189     /* RIP Routes */
> +#define RTPROT_EIGRP	192     /* EIGRP Routes */
>  
>  /* rtm_scope
>  

There is a matching table in iproute2 which should also be updated.
See etc/iproute/rt_protos

There also seems to be some leftover gated garbage there as well...