netdev - Re: [bug report or not] ping6 will lost packets when ping6 lots of ipv6 address

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]

Message-ID: <20151013161145.GE88112@canlin-mbp1.DHCP.thefacebook.com>
Date:	Tue, 13 Oct 2015 09:11:45 -0700
From:	Martin KaFai Lau <kafai@...com>
To:	Li RongQing <roy.qing.li@...il.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: [bug report or not] ping6 will lost packets when ping6 lots of
 ipv6 address

On Tue, Oct 13, 2015 at 08:46:49PM +0800, Li RongQing wrote:
> 1. in a machine, configure 3000 ipv6 address in one interface
>
> for i in {1..3000}; do ip -6 addr add 4001:5013::$i/0 dev eth0; done
>
>
> 2. in other machine, ping6 the upper configured ipv6 address, then
> lots of lost packets
>
> ip -6 addr add 4001:5013::0/64 dev eth0
> for i in {1..2000}; do ping6 -q -c1 4001:5013::$i; done;
>
> 3. increasing the gc thresh can handles these lost
>
> sysctl -w  net.ipv6.neigh.default.gc_thresh1=2000
> sysctl -w  net.ipv6.neigh.default.gc_thresh2=3000
> sysctl -w  net.ipv6.neigh.default.gc_thresh3=4000
> sysctl -w net.ipv6.route.gc_thresh=3000
> sysctl -w net.ipv6.route.max_size =3000
Which kernel is used in this test?
--
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