RE: Concealing Telnet Output...

From: Kristin Balon (kbalon@cisco.com)
Date: Sun May 04 2003 - 19:49:10 GMT-3

your telnet connection didn't fail, in order to see your busy message, do
something to keep the connection from being established in the first place.
Something like shutting down the connection to that router to test it would
work. Just make sure you put it back when you continue on with the test.
;-)

Kristin

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
W. Alan Robertson
Sent: Sunday, May 04, 2003 1:35 PM
To: ccielab@groupstudy.com
Subject: Concealing Telnet Output...

Hi Folks,

I've been through the archives, and found this link:

http://www.groupstudy.com/archives/ccielab/200006/msg00122.html

It states: 

----
Hide Telnet Addresses

You can hide addresses while attempting to establish a Telnet session. To
configure the router to suppress Telnet addresses, perform the following
task in global configuration mode:

Task: Hide addresses while establishing a Telnet session.
Command : service hide-telnet-address

The hide feature suppresses the display of the address and continues to
display all other messages that would normally display during a connection
attempt, such as detailed error messages if the connection was not
successful.

Use the busy-message command with the service hide-telnet-address command
to customize the information displayed during Telnet connection attempts.
If the connection attempt is not successful, the router suppresses the
address and displays the message specified with the busy-message command.
----

Seems straight forward, but alas, it doesn't seem to do much in my
environment, given the following configuration:

----
R2:
version 12.1
service hide-telnet-addresses
!
ip host R4 172.16.4.4
!
busy-message R4 ^
Connection Refused, Reason Unknown...
^
----

When I telnet from R2 to R4, it doesn't show the IP Address to Hostname
translation...  That part works fine...  But when I incorrectly type the
login password three times, instead of getting the message I configured
above ( "Connection Refused, Reason Unknown..."), I just get the standard "%
Bad passwords".

Is there something that I'm missing, or are my expectations incorrect, and
this behavior is as it should be.

My goal is that when I telnet from R2 to R4, I never see R4's IP address,
and that if my connection fails, rather than a standard telnet error
message, I am presented with "Connection Failed, Reason Unknown..."

Thanks,

Alan

This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:37 GMT-3