mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Pekka Savola <pekkas@netcore.fi>
Cc: kuznet@ms2.inr.ac.ru, therapy@endorphin.org, netdev@oss.sgi.com,
	linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: missing icmp errors for udp packets
Date: Wed, 1 Aug 2001 08:53:36 +1200	[thread overview]
Message-ID: <20010801085336.C8400@weta.f00f.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0107312249230.20772-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.33.0107312249230.20772-100000@netcore.fi>

On Tue, Jul 31, 2001 at 10:59:39PM +0300, Pekka Savola wrote:

    bad ping responder == bad PR ;-)

    And anyway, who is anyone to judge what the system should be used
    for?

    I want a system to respond to ping without limitations; it's good
    for debugging, diagnostics, etc.  If I want, I can just filter the
    requests out, or rate-limit the responses.

People who want to do strange stuff can tweak via sysctl.

    However, ICMP error messages cannot be effectively filtered; they
    may happen due to TTL=0 when forwarding, legit or illegit UDP
    connection etc.; only way to effectively limit them is by
    rate-limiting.  If rate-limiting with informational and error
    types are the same, we have an inflexible situation here.

Networks are lossy, you can spill the odd packet anyhow.

It was just a suggestion that we merge all ICMP rate-limiting for
simplicity, I don't see it being an issue for the majority of users.

Perhaps I am wrong, in which case DaveM and Alexey will ignore me :)

I really don't see the need to continue to discuss this further on the
list, but by all means flame me in private!





  --cw

  reply	other threads:[~2001-07-31 20:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0107290739370.2081-100000@netcore.fi>
2001-07-29 15:59 ` kuznet
2001-07-30 13:03   ` Pekka Savola
2001-07-31 18:33     ` kuznet
2001-07-31 18:47       ` Pekka Savola
2001-07-31 18:51       ` clemens
2001-07-31 19:04         ` kuznet
2001-07-31 19:23           ` Chris Wedgwood
2001-07-31 19:25             ` kuznet
2001-07-31 19:34               ` Chris Wedgwood
2001-07-31 19:37                 ` kuznet
2001-07-31 19:41                   ` Chris Wedgwood
2001-07-31 19:59                     ` Pekka Savola
2001-07-31 20:53                       ` Chris Wedgwood [this message]
2001-07-31 20:57                         ` Pekka Savola
2001-08-02 19:31     ` Pekka Savola
2001-08-03  8:58     ` David S. Miller
     [not found] <200107311857.WAA10162@ms2.inr.ac.ru>
2001-07-31 20:16 ` clemens

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=20010801085336.C8400@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=pekkas@netcore.fi \
    --cc=therapy@endorphin.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®