From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [Fwd: Re: [LARTC] Problem with ip route . VERY SLOW]
Date: Mon, 24 Oct 2005 12:18:58 +0000 [thread overview]
Message-ID: <435CD132.8020605@netshadow.at> (raw)
In-Reply-To: <435CD091.2070105@vipnet.ro>
Bogdan Coman wrote:
>> /Envoi d'une requête 'ping' sur www.l.google.com [216.239.59.99] avec
>> 32 octets de données :/
>>
>> *It waits for a long time HERE .*
>>
>> *I think it’s the route decision which takes a long time ,*
>>
> I believe that is the DNS that makes it take longer here, and not
> source routing.
>
I don't belive that, because it's already resolved. Do you checked with
tcpdump
where your packets are flowing?
Cheers,
Andreas
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-24 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 12:16 [Fwd: Re: [LARTC] Problem with ip route . VERY SLOW] Bogdan Coman
2005-10-24 12:18 ` Andreas Unterkircher [this message]
2005-10-24 18:22 ` Franck LEPRETTE
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=435CD132.8020605@netshadow.at \
--to=unki@netshadow.at \
--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.