Re: IPv6 routing table max_size badly dimensioned compared to IPv4
From: bert hubert <hidden>
Date: 2014-02-28 11:07:40
On Thu, Feb 27, 2014 at 05:47:55PM -0500, David Miller wrote:
quoted
If we need to perform 10000 inserts per second, and gc timeout is 60 seconds, tree contains 600.000 entries, gc takes forever...The only long term solution is to align ipv6 to be more like ipv4.
Yes please. There appears to be a lingering assumption IPv6 is small scale. T-Mobile USA is now providing IPv6 only service via DNA64/NAT64, creating (dozens of) millions of IPv6 only clients. (More on this 'hack' on http://blog.powerdns.com/2013/05/17/ripe-66-powerdns-and-dns64nat64/ ) So aligning IPv6 scalability with IPv4 scalability would be grand, thanks! Bert