From: "Franck LEPRETTE" Date: Mon, 24 Oct 2005 10:21:22 +0000 Subject: [LARTC] Problem with ip route . VERY SLOW Message-Id: <001901c5d884$aeb61b60$b500a8c0@NOVIS.COM> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1726057698==" List-Id: To: lartc@vger.kernel.org This is a multi-part message in MIME format. --===============1726057698== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01C5D895.723EEB60" This is a multi-part message in MIME format. ------=_NextPart_000_001A_01C5D895.723EEB60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello everybody =20 I=92m french and =91im a network administrator.=20 It the firs time I write on this mailing list .. =20 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 . =20 When I make a ping for example on a windows machine : =20 [in French ] $> ping www.Google.Fr Envoi d'une requ=EAte 'ping' sur www.l.google.com [216.239.59.99] avec = 32 octets de donn=E9es : It waits for a long time HERE . I think it=92s the route decision which takes a long time , Then it works fine . =20 R=E9ponse de 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241 R=E9ponse de 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241 R=E9ponse de 216.239.59.99 : octets=3D32 temps=3D77 ms TTL=3D241 R=E9ponse de 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241 =20 Is there a solution to make the connection faster ? Is there any problems with routing on multiple interfaces ? =20 Thanks in advance =20 =20 ------=_NextPart_000_001A_01C5D895.723EEB60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

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 = ,

Then it = works fine .

&nbs= p;

Réponse de = 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241

Réponse de = 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241

Réponse de = 216.239.59.99 : octets=3D32 temps=3D77 ms TTL=3D241

Réponse de = 216.239.59.99 : octets=3D32 temps=3D76 ms TTL=3D241

&nbs= p;

Is there a solution to make the connection = faster ?

Is there any problems with routing on = multiple interfaces ?

 

Thanks  in = advance

 

&nbs= p;

------=_NextPart_000_001A_01C5D895.723EEB60-- --===============1726057698== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1726057698==--