Re: [gentoo-user] telnet into embedded devices
On Thu, 2005-06-30 at 13:39 +1200, Nick Rout wrote: > On Thu, 30 Jun 2005 00:59:17 + (UTC) > James wrote: > > 1. If this is not what's happening, what is to cause telnet to react so > > slowly? > > probably dns - most servers do a reverse dns lookup when a client > connects, and if the lookup does not work the timeout can be quite > noticeably long. > Based on my experience, I concur with Nick's analysis that it is a DNS lookup timeout. Regards, Paul -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] telnet into embedded devices
On Thu, 2005-06-30 at 00:59 +, James wrote: > Hello, > > I often use telnet to connect to (embedded) devices on a local network, > devices which do not support ssh. On both Debian and Gentoo systems I > just delete the default route out and set a second (sub)interface on > the ethernet port like this: [snip] > My actual question may or may not be related to the use of a sub interface. > When I telnet into the devices from a similarly setup Debian system, I get > a very fast response. When I telnet into the devices from a gentoo system, > it takes 30-50s (estimate) for the login prompt response. It's almost as > those telnet is set up to use ssh, but times out and then defaults to > real telnet? Before I start, I know nothing about differences between telnet on debian and telne on gentoo. You may look there first to see if one does weird things, like you say. there are a couple of things I would to to see what's happening. Firstly, make sure your gentoo and debian box are either exactly the same box, or are on exactly the same switch. You never know just what your sysadmin has done (even if you think you know, you could be surprised!) Then try traceroute or something similar and see if the path to your embedded device is the same from each box. If not, there's your answer. If it is the same, then I'd probably try ethereal and capture the output to each box and compare it. That's how I found out ftp was trying ssl first with an embedded device that didn't support it, before trying normal ftp. HTH, -- Iain Buchanan <[EMAIL PROTECTED]> -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] telnet into embedded devices
On Thu, 30 Jun 2005 00:59:17 + (UTC) James wrote: > Hello, > > I often use telnet to connect to (embedded) devices on a local network, > devices which do not support ssh. On both Debian and Gentoo systems I > just delete the default route out and set a second (sub)interface on > the ethernet port like this: > > The default setting is obtained from the /etc/conf.d/netfile: > iface_eth0="192.168.2.23 broadcast 192.168.2.255 netmask 255.255.255.0" > > So I use these commands to set up an additional interface that > matches the defauld class C (/24) network that the device manufacturer > sets as a default. For example a device might be given 192.168.15.1: > > route delete default > ifconfig eth0:0 inet 192.168.15.23 netmask 255.255.255.0 broadcast > 192.168.15.255 > > ifconfig yeilds: > eth0 Link encap:Ethernet HWaddr 00:90:F5:2B:CB:13 > inet addr:192.168.2.23 Bcast:192.168.2.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:590024 errors:0 dropped:0 overruns:0 frame:0 > TX packets:80894 errors:0 dropped:0 overruns:0 carrier:0 > collisions:4089 txqueuelen:1000 > RX bytes:153811888 (146.6 Mb) TX bytes:5882603 (5.6 Mb) > Interrupt:11 Base address:0x2000 > > eth0:0Link encap:Ethernet HWaddr 00:90:F5:2B:CB:13 > inet addr:192.168.15.23 Bcast:192.168.15.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:590024 errors:0 dropped:0 overruns:0 frame:0 > TX packets:80894 errors:0 dropped:0 overruns:0 carrier:0 > collisions:4089 txqueuelen:1000 > RX bytes:153811888 (146.6 Mb) TX bytes:5882603 (5.6 Mb) > Interrupt:11 Base address:0x2000 > > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:2673 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2673 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:269579 (263.2 Kb) TX bytes:269579 (263.2 Kb) > > My actual question may or may not be related to the use of a sub interface. > When I telnet into the devices from a similarly setup Debian system, I get > a very fast response. When I telnet into the devices from a gentoo system, > it takes 30-50s (estimate) for the login prompt response. It's almost as > those telnet is set up to use ssh, but times out and then defaults to > real telnet? > > 1. If this is not what's happening, what is to cause telnet to react so > slowly? probably dns - most servers do a reverse dns lookup when a client connects, and if the lookup does not work the timeout can be quite noticeably long. > > 2. Regardless of what's happening, how to I fix? When I use telnet, I > want telnet, nice and fast, not ssh or any other protocol. > > Ideas on how to fix telnet on Gentoo? you don't need to if i am right. > > James > > > > -- > gentoo-user@gentoo.org mailing list -- Nick Rout -- gentoo-user@gentoo.org mailing list
