From mboxrd@z Thu Jan 1 00:00:00 1970 From: Franck LEPRETTE Date: Mon, 24 Oct 2005 12:39:14 +0000 Subject: RE: [LARTC] Problem with ip route . VERY SLOW Message-Id: <000701c5d897$f17316c0$6500a8c0@NOVIS.COM> List-Id: References: <001901c5d884$aeb61b60$b500a8c0@NOVIS.COM> In-Reply-To: <001901c5d884$aeb61b60$b500a8c0@NOVIS.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org * 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=A0: Bogdan Coman [mailto:cbi@adica.eu.org]=20 Envoy=E9=A0: lundi 24 octobre 2005 13:25 =C0=A0: Franck LEPRETTE Cc=A0: lartc@mailman.ds9a.nl Objet=A0: Re: [LARTC] Problem with ip route . VERY SLOW Hi, Franck LEPRETTE wrote: > Hello everybody > > I=92m french and =91im a network administrator. > > It the firs time I write on this mailing list .. > > I configure a debian distribution (the last one sarge) with iproute2=20 > 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=EAte 'ping' sur www.l.google.com [216.239.59.99] avec=20 > 32 octets de donn=E9es :/ > > *It waits for a long time HERE .* > > *I think it=92s the route decision which takes a long time ,* > I believe that is the DNS that makes it take longer here, and not source=20 routing. > ** > > *Then it works fine .* > > / / > > /R=E9ponse de 216.239.59.99 : octets2 tempsv ms TTL$1/ > > /R=E9ponse de 216.239.59.99 : octets2 tempsv ms TTL$1/ > > /R=E9ponse de 216.239.59.99 : octets2 tempsw ms TTL$1/ > > /R=E9ponse 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 > =20 > _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc