From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: ICMP rate limiting in IPv4 but not in IPv6 Date: Fri, 13 Sep 2013 18:44:05 +0200 Message-ID: <20130913164404.GA32431@order.stressinduktion.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: netdev@vger.kernel.org To: Andy Johnson Return-path: Received: from order.stressinduktion.org ([87.106.68.36]:56181 "EHLO order.stressinduktion.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751079Ab3IMQoH (ORCPT ); Fri, 13 Sep 2013 12:44:07 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Sep 13, 2013 at 06:57:56PM +0300, Andy Johnson wrote: > Hello, > After probing into the RFC of ICMPv6, I am even more confused. > > RFC 4443 says: > > 2.4. Message Processing Rules > ... > > (f) Finally, in order to limit the bandwidth and forwarding costs > incurred by originating ICMPv6 error messages, an IPv6 node MUST > limit the rate of ICMPv6 error messages it originates. > ... > The rate-limiting parameters SHOULD be configurable. > ... > > Any ideas? Well, nobody has implemented it because nobody missed the feature yet. I don't believe there is another reason for that. If you come up with a patch, I am sure it can go upstream. Do you want to try to come up with a patch? We need to be a bit careful regarding neighbor discovery but otherwise this should be relativ straightforward. In the meantime you could also implement such ratelimiting with netfilter. Greetings, Hannes