iproute2 can inconsistently show the name of protocol 0 if a route with a custom protocol is added. For example: dsa@cartman:~$ ip -6 ro ls table all | egrep 'proto none|proto unspec' local ::1 dev lo table local proto none metric 0 pref medium local fe80::225:90ff:fecb:1c18 dev lo table local proto none metric 0 pref medium local fe80::92e2:baff:fe5c:da5d dev lo table local proto none metric 0 pref medium
protocol 0 is pretty printed as "none". Add a route with a custom protocol: dsa@cartman:~$ sudo ip -6 ro add 2001:db8:200::1/128 dev eth0 proto 123 And now display has switched from "none" to "unspec": dsa@cartman:~$ ip -6 ro ls table all | egrep 'proto none|proto unspec' local ::1 dev lo table local proto unspec metric 0 pref medium local fe80::225:90ff:fecb:1c18 dev lo table local proto unspec metric 0 pref medium local fe80::92e2:baff:fe5c:da5d dev lo table local proto unspec metric 0 pref medium The rt_protos file has the id to name mapping as "unspec" while rtnl_rtprot_tab[0] has "none". The presence of a custom protocol id triggers reading the rt_protos file and overwriting the string in rtnl_rtprot_tab. All of this is logic from 2004 and earlier. The simplest change to achieve consistency is to update the rt_protos file to use "none" instead of "unspec". Signed-off-by: David Ahern <d...@cumulusnetworks.com> --- etc/iproute2/rt_protos | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etc/iproute2/rt_protos b/etc/iproute2/rt_protos index 82cf9c46cf6f..21af85b9d7e1 100644 --- a/etc/iproute2/rt_protos +++ b/etc/iproute2/rt_protos @@ -1,7 +1,7 @@ # # Reserved protocols. # -0 unspec +0 none 1 redirect 2 kernel 3 boot -- 2.1.4
