All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HOW CAN I PRIORITIZE THE ICMP PACKETS
Date: Thu, 03 May 2001 01:29:30 +0000	[thread overview]
Message-ID: <marc-lartc-98885339530557@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98882360532346@msgid-missing>

I think David is correct. DNS can be the cause of your long delays,
specially with traceroute.

You could also asign a higher periority to your traceroute and ping
packets but then you'll lose the purpose of these tools...

Why do you need ping and traceroute to work fast?

Ramin

On Wed, May 02, 2001 at 08:13:57PM -0500, David A. Bandel wrote:

> Alexandra Alvarado wrote:
> > 
> > Hello, i have a very big problem, i hope somebody solve my problem, when
> > i configure cbq it works fine but when i executed ping it turns to slow,
> > I NEED the PING and TRACEROUTE works so fast, how can i do that?.
> > 
> 
> for traceroute, try: traceroute -n <Target>
> 
> pings will be slow if the pipe is clogged, not much you can do about
> it.  If you just mean it's slow to start, that's the initial DNS
> lookup.  If you mean after the DNS lookup, the normally induced latency
> is a rather direct measure of how clogged the pipe is.
> 
> Ciao,
> 
> David A. Bandel
> -- 
> Focus on the dream, not the competition.
> 		-- Nemesis Racing Team motto

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-05-03  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 12:16 [LARTC] HOW CAN I PRIORITIZE THE ICMP PACKETS Alexandra Alvarado
2001-05-03  1:13 ` David A. Bandel
2001-05-03  1:29 ` Ramin Alidousti [this message]
2001-05-03  3:19 ` Re[2]: " Fabian Gervan
2001-05-03  9:32 ` Alexandra Alvarado
2001-05-03 11:30 ` Alexandra Alvarado
2001-05-03 15:59 ` Wingtung.Leung

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=marc-lartc-98885339530557@msgid-missing \
    --to=ramin@uu.net \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.