On Wed, Sep 23, 2026 at 09:36:55AM +0900, Yuya Kusakabe wrote: > "ip route save" stores a route dump and "ip route restore" sends it > back to the kernel unchanged. The kernel dumps RTA_ENCAP, and some of > the attributes nested in it, without NLA_F_NESTED, but rpl, ioam6, > xfrm and the geneve, vxlan and erspan options of the ip and ip6 encaps > require the flag when parsing them. Restoring such a route fails with > "NLA_F_NESTED is missing", and none of them has been restorable in any > release.
If this never worked, then why target these patches at net and blaming up to 7 years old commits? I try to follow [1] when deciding between net and net-next. Also, did you hit this in practice or was this flagged by AI? If nobody is using save/restore and hitting this in practice, then maybe it's not worth to loosen the validation performed by the kernel. Note that nowadays many deployments program routes using nexthop objects and ip-nexthop completely lacks save/restore functionality. [1] https://lkml.org/lkml/2018/6/24/113
