netdev - Re: ipv6 hitting route max

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 6 Jun 2011 16:15:21 -0700
From:	Simon Kirby <sim@...tway.ca>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: ipv6 hitting route max_size

On Mon, Jun 06, 2011 at 03:01:42PM -0700, David Miller wrote:

> From: Simon Kirby <sim@...tway.ca>
> Date: Mon, 6 Jun 2011 14:37:27 -0700
> 
> > /proc/sys/net/ipv6/route/max_size and a number of similar GC knobs exist,
> > but max_size seems to limit the size of the v6 route table, not the v6
> > route cache.
> 
> There is no v6 route cache.
> 
> Instead of a routing cache, ipv6 route lookups "clone" new routes into
> the same datastructre the route table is stored in.

Ok, makes sense, but the result is now that ipv4 loads a full Internet
table with no adjustments, while ipv6 does not. Would it make sense to
change 4096 to 1048576, or would it be better to count only clones of
the actual route or something along those lines?

Simon-
--
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