--- Sergio Basurto Juarez <[EMAIL PROTECTED]> wrote:

> 
> --- "H. S." <[EMAIL PROTECTED]> wrote:
> 
> > Apparently, _Riccardo Tortorici_, on 16/11/04
> > 22:39,typed:
> > > Check your iptables settings...I had this
> problem
> > months ago...
> > 
> > What did you find your problem was? How did you
> > solve it?
> > 
> > ->HS
> > 
> > 
> > > H. S. wrote:
> > > 
> > >> On Debian Testing running 2.6.7,the 'route'
> > command is taking 
> > >> unusually long time to give the table:
> > >> ~# time route
> > >> Kernel IP routing table
> > >> Destination    Gateway     Genmask        
> Flags
> > Metric Ref    Use Iface
> > >> x.y.z.z        *           255.255.255.255 UH  
> 
> > 0      0        0 ppp0
> > >> 192.168.1.0    *           255.255.255.0   U   
> 
> > 0      0        0 eth0
> > >> 192.168.0.0    *           255.255.255.0   U   
> 
> > 0      0        0 eth1
> > >> default        x.y.z.z     0.0.0.0         UG  
> 
> > 0      0        0 ppp0
> > >>
> > >> real    0m20.010s
> > >> user    0m0.002s
> > >> sys     0m0.002s
> > >>
> > >>
> > >> However, 'route -n' command gives the output
> > almost instantly.
> > >>
> > >> Anybody else experiencing this? Any idea why
> this
> > would be so?
> > >>
> > >> ->HS
> > >>
> > >>
> > > 
> 
> When you type the command:
> #route -n
> you are telling to route that does not try to resolv
> names. That's why it returns almost immediatly.
> Nevertheless if your dns server is setup correctly
> it
> does not have to take long time in fact the
> difference
> is tiny:
> 
> # time route
> Kernel IP routing table
> Destination     Gateway         Genmask        
> Flags
> Metric Ref    Use Iface
> 10.0.0.0        *               255.255.255.0   U   
> 
> 0      0        0 eth1
> 192.168.0.0     *               255.255.255.0   U   
> 
> 0      0        0 eth0
> default         10.0.0.1        0.0.0.0         UG  
> 
> 0      0        0 eth1
> 
> real    0m0.005s
> user    0m0.000s
> sys     0m0.000s
> # time route -n
> Kernel IP routing table
> Destination     Gateway         Genmask        
> Flags
> Metric Ref    Use Iface
> 10.0.0.0        0.0.0.0         255.255.255.0   U   
> 
> 0      0        0 eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U   
> 
> 0      0        0 eth0
> 0.0.0.0         10.0.0.1        0.0.0.0         UG  
> 
> 0      0        0 eth1
> 
> real    0m0.003s
> user    0m0.010s
> sys     0m0.000s
> 
> 
> Regards.
> 
> 
> 
> 
;P
Sorry I forgot to mention, for short, the matter is
that route takes too much time when your dns server,
or  servers are missing somenthing or misconfigured.
May be a caching only server would help or lwresd.

Regards.



=====
--
Sergio Basurto J.

If I have seen further it is by standing on the 
shoulders of giants. (Isaac Newton)
--


                
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to