Re: [PATCH iproute2] bridge:fdb: Protocol field in bridge fdb

Stephen Hemminger <[email protected]>
Newsgroups gmane.linux.network.bridge,gmane.linux.network
Message-ID <[email protected]>
On Sat, 16 Aug 2025 03:11:45 +0000
Mrinmoy Ghosh <[email protected]> wrote:

> diff --git a/include/uapi/linux/rtnetlink.h b/include/uapi/linux/rtnetlink.h
> index 085bb139..1ff9dbee 100644
> --- a/include/uapi/linux/rtnetlink.h
> +++ b/include/uapi/linux/rtnetlink.h
> @@ -314,6 +314,7 @@ enum {
>  #define RTPROT_OSPF		188	/* OSPF Routes */
>  #define RTPROT_RIP		189	/* RIP Routes */
>  #define RTPROT_EIGRP		192	/* EIGRP Routes */
> +#define RTPROT_HW		193	/* HW Generated Routes */
>  
>  /* rtm_scope
>  
> diff --git a/lib/rt_names.c b/lib/rt_names.c
> index 7dc194b1..b9bc1b50 100644
> --- a/lib/rt_names.c
> +++ b/lib/rt_names.c
> @@ -148,6 +148,7 @@ static char *rtnl_rtprot_tab[256] = {
>  	[RTPROT_OSPF]	    = "ospf",
>  	[RTPROT_RIP]	    = "rip",
>  	[RTPROT_EIGRP]	    = "eigrp",
> +	[RTPROT_HW]	    = "hw",
>  };
>  
>  struct tabhash {

This is iproute2-next material.

Where is the kernel patch for this?
Iproute headers are synced from kernel headers.

If you add new RTPROT entry also need new line into etc/iproute2/rt_protos
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.