Re: [gentoo-user] telnet into embedded devices

2005-06-29 Thread Iain Buchanan
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

2005-06-29 Thread Paul Varner
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