Roy Marples
2015-09-10 10:55:03 UTC
In my plan, the next step is to separate L2 nexthop cache from the
routing table that simplifies route lookup operations. For example,
the route cloning mechanism can be eliminated. See the changes
http://www.netbsd.org/~ozaki-r/separate-l2-nexthop.diff
I filed a bug with FreeBSD about removal of RTF_CLONINGrouting table that simplifies route lookup operations. For example,
the route cloning mechanism can be eliminated. See the changes
http://www.netbsd.org/~ozaki-r/separate-l2-nexthop.diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485
Here's the text for those too lazy to click the link:
Userland cannot add IPv6 prefix routes because the kernel assumes it
will always be the one handling prefix routes from Router Advertisements.
Both NetBSD and OpenBSD have added checks to allow for neighbors on
routes marked RTF_CLONING, but FreeBSD dropped this routing flag a while
ago. As such, the only similar check that can be made is against the
absence of RTF_STATIC.
If we can solve this issue and still allow for the removal of
RTF_CLONING then I'm all ears :)
I suppose we could add a new RTF flag in it's place, maybe RTF_NEIGHBOR?
Roy
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de