> Without reading the kernel routing table code a bit more, I'm not certain
> what that change does, but it looks as if it might be changing the
> connected route for a link local from fe80::/10 to fe80::/64.
Why do you want to use /10 prefix for link-local address ?
RFC2373 defines link-local address format as below.
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
> All link local's are currently supposed to have those top bits
> ('tween 10 and 64) zero'd, however any address within the link local
> prefix _is_ on link / connected and should go to the interface.
If you wan to use /10 prefix for link-local address, you can add the
link-local address with /10 prefix to interfaces and routing table
manually at your own risk, but it should not be a default behavior.
-- Yuji Sekiya
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/