netdev - Re: Problem with ICMP rate limiting and redirects

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] [day] [month] [year] [list]

Message-ID: <1443732782.32531.52.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Thu, 01 Oct 2015 13:53:02 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Hugo Vasconcelos Saldanha <hugovs@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Problem with ICMP rate limiting and redirects

On Thu, 2015-10-01 at 15:38 -0300, Hugo Vasconcelos Saldanha wrote:

> Thanks for pointing that out.
> 
> But how should all the sysctl's that control ICMP messages sent to
> specific targets (icmp_ratelimit, redirect_load, redirect_number,
> redirect_silence, error_cost and error_burst) be treated without
> relying on inetpeer? Entries in ip_idents hash don't represent
> specific targets. Am I missing something?


You could still rely on inetpeer if its size is controlled and capped.

And then fallback to ip_idents hash if inetpeer tree gets too big.

Best effort would be enough.


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