Hello everybody Im 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 its the route decision which takes a long time , Then it works fine . Réponse de 216.239.59.99 : octets=32 temps=76 ms TTL=241 Réponse de 216.239.59.99 : octets=32 temps=76 ms TTL=241 Réponse de 216.239.59.99 : octets=32 temps=77 ms TTL=241 Réponse de 216.239.59.99 : octets=32 temps=76 ms TTL=241 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
* 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 > > Im 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 its 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 : octets=32 temps=76 ms TTL=241/ > > /Réponse de 216.239.59.99 : octets=32 temps=76 ms TTL=241/ > > /Réponse de 216.239.59.99 : octets=32 temps=77 ms TTL=241/ > > /Réponse de 216.239.59.99 : octets=32 temps=76 ms TTL=241/ > > / / > > 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 > >
(i speak in english) Tx for your answer No, if i ping a local host , it works fine and fast. I use two route tables with iproutes2 , : 1) table T1 2) table T2 And If I enter> ip route ls table T1default via 192.168.0.100 dev eth3> ip route ls table T2default via 192.168.1.100 dev eth2> routedefault 192.168.0.100 UG .. so , i think there are two default gateways ? Do you think it''s the matter ? if yes , how can I modify it ? -----Message d''origine----- De : Guillaume Beaudoin [mailto:guillaume.beaudoin@bdeb.qc.ca] Envoyé : lundi 24 octobre 2005 20:01 À : Franck LEPRETTE Cc : lartc@mailman.ds9a.nl Objet : Re: [LARTC] Problem with ip route . VERY SLOW Bonjour Franck, Hi Franck, Est-ce que la même chose se produit si tu ping une adresse sur ton réseau local? Est-ce que tu aurais deux passerelles par défault? Does the same thing happens if you ping an address on your local area network? Do you have two default gateway? Feel free to message me off list in french, I don''t want to bothers our english collegues with french too much. Regards,> * 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 pinga> 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...? > >-- Guillaume Beaudoin "À la hauteur de mon avenir." Service Informatique Une tradition d''excellence Collège de Bois-de-Boulogne depuis plus de 40 ans.
Franck LEPRETTE wrote:> 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...?No, there are not too many interfaces. I have run 4 all at once. Three were ethernet (DSL) and 1 ppp (Modem). Yes, there are iproute2 issues. 1) The LARTC HOWTO is wrong. 2) Your routing tables seem to have only 2 entries; you probably need 3. 3) Similar IP addresses can be a problem. 192.168.0.0/24 is too similar to 192.168.100.0/24. Worse, private IPs are a pain. (All that is my opinion, not necessarily fact.) 4) There shouldn''t be a default route. Instead, there should be a default route for each external interface such that packets received on one get replied on the same one. This link is apparently dead http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking so read this instead http://yesican.chsoft.biz/lartc/MultihomedLinuxNetworking.html Post your configuration files. Do not just describe them. Give us an explanation of the setup, possibly including some "ASCII art". Here''s a link where you will find other''s successes: http://yesican.chsoft.biz/lartc/index.html Read EXAMPLES and MULTIPATH and follow the links. -- gypsy