netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Bieringer <pb@bieringer.de>
To: netdev@oss.sgi.com
Cc: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@wide.ad.jp>
Subject: Re: ICMPv6 ratelimiting, which /proc-settings related?
Date: Tue, 16 Jul 2002 09:07:46 +0200	[thread overview]
Message-ID: <14790000.1026803266@localhost> (raw)
In-Reply-To: <20020715.024401.17983126.yoshfuji@wide.ad.jp>



--On Monday, July 15, 2002 02:44:01 AM +0900 "YOSHIFUJI Hideaki /
=?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?=" <yoshfuji@wide.ad.jp> wrote:

> In article <17380000.1026547066@localhost> (at Sat, 13 Jul 2002
> 09:57:46 +0200), Peter Bieringer <pb@bieringer.de> says:
> 
>> extending my IPv6-howto with information about the /proc-FS I found
>> that there is no setting for ICMPv6 rate limiting.
> 
> icmpv6_xrlim_allow() controls rate limiting.
> 
> A variable named sysctl_icmpv6_time lives in net/ipv6/icmp.c, but
> sysctl does not exist in fact...

Oh, I found:

# grep icmpv6_time *
icmp.c:int sysctl_icmpv6_time = 1*HZ;
icmp.c:         int tmo = sysctl_icmpv6_time;


> Is introducing /proc/sys/net/ipv6/icmp/all/icmpv6_time reasonable?

Is HZ completly arch independed? Afair, it was CPU depended (like
grep HZ include/asm/param.h) shows.

Mho: Better name:

/proc/sys/net/ipv6/icmp/all/icmpv6_rate

I would suggest use of unit 1/s and run conversion internally.
Therfore
1 -> 1/s
10 -> 10/s
100 -> 100/s
0.1 -> 1/10s

        Peter

  reply	other threads:[~2002-07-16  7:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13  7:57 ICMPv6 ratelimiting, which /proc-settings related? Peter Bieringer
2002-07-13 19:49 ` Harald Welte
2002-07-14 17:49   ` Peter Bieringer
2002-07-14 17:44 ` YOSHIFUJI Hideaki / 吉藤英明
2002-07-16  7:07   ` Peter Bieringer [this message]
2002-07-16  7:30     ` 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=14790000.1026803266@localhost \
    --to=pb@bieringer.de \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@wide.ad.jp \
    /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;
as well as URLs for NNTP newsgroup(s).