Thanks for your reply. It corrected my mistake :) route -n returns immediately, and route returns after sevel seconds.
then how to make in.telnetd do not do a dns reverse lookup? Regards Liu Tao On Friday 19 October 2001 13:08, Anthony J. Breeds-Taurima wrote: > On Fri, 19 Oct 2001, Liu Tao wrote: > > I am in a local net and I have a default gateway to visit internet. > > And I want to provide telnet service to local net. > > But there is something wrong with the gateway(win2k), > > it returns the route information very slow. > > > > My route looks like > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface localnet * 255.255.255.0 U 0 0 > > 0 eth0 default 192.168.0.1 0.0.0.0 UG 0 0 > > 0 eth0 > > > > Sometimes it cost several seconds to complete the "route" program. > > And it seems that in.telnetd will wait the route information. > > So, the gw affects my telnet service. when telnet to me, login prompt > > will appear after waiting sevel seconds. If I do not set the default > > route, telnet will show login promp immediately. > > > > How to solve the problem, except fix the gateway? > > Try: > time route -n >/dev/null > time route >/dev/null > > If the first is fater than the second then the issue is NOT with the > routeing it is a DNS lookup issue. It just means the your DNS server isn't > providing reverse mappings for your private IP's > > Yours Tony. > > /* > * "The significant problems we face cannot be solved at the > * same level of thinking we were at when we created them." > * --Albert Einstein > */
