From: Pekka Savola <pekkas@netcore.fi>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: usagi@linux-ipv6.org, <linux-kernel@vger.kernel.org>,
<netdev@oss.sgi.com>
Subject: Re: [PATCH] IPv6: Sysctl for ICMPv6 Rate Limitation
Date: Thu, 24 Oct 2002 08:59:16 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0210240858060.8872-100000@netcore.fi> (raw)
In-Reply-To: <20021024.145551.130454003.yoshfuji@linux-ipv6.org>
On Thu, 24 Oct 2002, YOSHIFUJI Hideaki / [iso-2022-jp] ^[$B5HF#1QL@^[(B wrote:
> In article <Pine.LNX.4.44.0210240847280.8872-100000@netcore.fi> (at Thu, 24 Oct 2002 08:50:25 +0300 (EEST)), Pekka Savola <pekkas@netcore.fi> says:
>
> > > +icmp/*:
> > > +ratelimit - INTEGER
> > > + Limit the maximal rates for sending ICMPv6 packets.
> > > + 0 to disable any limiting, otherwise the maximal rate in jiffies(1)
> > > + Default: 100
> > > +
> >
> > Does this rate-limit all ICMPv6 packets or just ICMPv6 error messages (as
> > specified in ICMPv6 specifications).
> >
> > If all, I believe the default of rate-limiting everything is unacceptable.
>
> This patch just adds sysctl. It is my documentation error...
> is s/ICMPv6 packets/ICMPv6 error packets/ ok?
>
> (I need to do s/100/HZ/, too; This also lives in ICMP(v4)).
That change fine with me, thanks.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
next prev parent reply other threads:[~2002-10-24 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 4:50 YOSHIFUJI Hideaki / 吉藤英明
2002-10-24 5:50 ` Pekka Savola
2002-10-24 5:55 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-24 5:59 ` Pekka Savola [this message]
2002-10-24 7:23 ` YOSHIFUJI Hideaki / 吉藤英明
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0210240858060.8872-100000@netcore.fi \
--to=pekkas@netcore.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®