All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franck LEPRETTE <korta@neuf.fr>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Problem with ip route . VERY SLOW
Date: Mon, 24 Oct 2005 12:39:14 +0000	[thread overview]
Message-ID: <000701c5d897$f17316c0$6500a8c0@NOVIS.COM> (raw)
In-Reply-To: <001901c5d884$aeb61b60$b500a8c0@NOVIS.COM>

* I believe that is the DNS that makes it take longer here, and not source 
* routing.


First of all, tx for your answer.

It's possible but I don't think so because nslookup command answers fast.
More over, when I type ping hostname, before I have to wait for response,
the computer has resolved the hostname to ip address.

But how can I know where is the bottleneck ?

The problem of very slow connection appears for example when I try to ping a
host or when I try to connect to a website with my navigator.

I remember that I have 3 interfaces and I wonder my self if it's possible
that there are too many interfaces on the computer; or there are
restrictions with iproutes2 etc...?







-----Message d'origine-----
De : Bogdan Coman [mailto:cbi@adica.eu.org] 
Envoyé : lundi 24 octobre 2005 13:25
À : Franck LEPRETTE
Cc : lartc@mailman.ds9a.nl
Objet : Re: [LARTC] Problem with ip route . VERY SLOW

Hi,
Franck LEPRETTE wrote:

> Hello everybody
>
> I’m french and ‘im a network administrator.
>
> It the firs time I write on this mailing list ..
>
> I configure a debian distribution (the last one sarge) with iproute2 
> to route packets depending on source ip address
>
> It works fine but it is very very slow .
>
> When I make a ping for example on a windows machine :
>
> /[in French ]/
>
> /$> ping www.Google.Fr/
>
> /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.

> **
>
> *Then it works fine .*
>
> / /
>
> /Réponse de 216.239.59.99 : octets2 tempsv ms TTL$1/
>
> /Réponse de 216.239.59.99 : octets2 tempsv ms TTL$1/
>
> /Réponse de 216.239.59.99 : octets2 tempsw ms TTL$1/
>
> /Réponse de 216.239.59.99 : octets2 tempsv ms TTL$1/
>
> / /
>
> Is there a solution to make the connection faster ?
>
> Is there any problems with routing on multiple interfaces ?
>
> Thanks in advance
>
> / /
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>  
>

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-10-24 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 10:21 [LARTC] Problem with ip route . VERY SLOW Franck LEPRETTE
2005-10-24 12:39 ` Franck LEPRETTE [this message]
2005-10-24 18:14 ` Franck LEPRETTE
2005-10-25  6:59 ` gypsy

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='000701c5d897$f17316c0$6500a8c0@NOVIS.COM' \
    --to=korta@neuf.fr \
    --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.