mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: kuznet@ms2.inr.ac.ru
Cc: therapy@endorphin.org, pekkas@netcore.fi, 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 07:34:41 +1200	[thread overview]
Message-ID: <20010801073441.E8228@weta.f00f.org> (raw)
In-Reply-To: <200107311925.XAA11038@ms2.inr.ac.ru>
In-Reply-To: <200107311925.XAA11038@ms2.inr.ac.ru>

On Tue, Jul 31, 2001 at 11:25:50PM +0400, kuznet@ms2.inr.ac.ru wrote:

    Anyway, it is clear that echos are to be limited differently of
    errors.

Even then I wonder if it is worth the code.  If you are rate-limiting,
who cares if drop the odd echo/reply?

ICMP echo/reply is a useful diagnostic tool --- but on the internet as
we have it today, its limitations need to be understood by the user :)



  --cw

  reply	other threads:[~2001-07-31 19:34 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 [this message]
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
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=20010801073441.E8228@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®