| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20140115115115.GD19945@order.stressinduktion.org> Date: Wed, 15 Jan 2014 12:51:15 +0100 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: Simon Schneider <simon-schneider@....net> Cc: netdev@...r.kernel.org Subject: Re: Route exceptions for IPv6 routes? Hi! On Wed, Jan 15, 2014 at 09:01:22AM +0100, Simon Schneider wrote: > I learned that the routing cache was removed from the kernel for several reasons. > > Some functions have been replaced with the route exceptions, e.g. storing the path MTU. > > My question: is this valid for both IPv4 as well as IPv6 routing, i.e. do the route exceptions work in the same way for IPv6 routes as they work for IPv4 routes? No, situation in IPv6 land is not so good. Currently as soon as a destination (or destination + source in case of subtrees are in use) is resolved the routing entry is cloned and stored back into the same trie with RTF_CACHE flag. There are no nh-exceptions and there is no aggressive sharing taking place to try to reduce the number of exceptions. This is especially bad for forwarding setups, but seems to work fine for most people currently. ;) Actually, implementing this is part of the work I am currently doing but this needs still time until I can manage to propose this for upstream. Greetings, Hannes -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists