Mailing List Archive

connection to terminal server cli
Hi,

I've just set up 8.0.9 on a RH9 system, and for the most part, all is
going well. The current bogon is that connections to the internal CLI
on some of the terminal servers doesn't echo characters. We have both
cisco 2511s (11.0 and 12.0) and some portmaster 2e's (3.7.2 and .2c4).

The definitions look like:
console cs0 { type host; host cs0.lab.blablalba;
port 23; options ondemand; }

In general, the cisco's work and the PMs don't. If I telnet to the
PMs, I get character echo. If I console to them, I don't.

Any thoughts?

z!
Carl Zwanzig
Re: connection to terminal server cli [ In reply to ]
I've experienced similar issues. I think it may be because conserver
does not support the telnet protocol. It really was not meant to
operate that way. Maybe you should use the command instead then
conserver will spawn telnet when you try to connect to cs0

On Wed, 2004-01-07 at 17:04, Carl Zwanzig wrote:
> Hi,
>
> I've just set up 8.0.9 on a RH9 system, and for the most part, all is
> going well. The current bogon is that connections to the internal CLI
> on some of the terminal servers doesn't echo characters. We have both
> cisco 2511s (11.0 and 12.0) and some portmaster 2e's (3.7.2 and .2c4).
>
> The definitions look like:
> console cs0 { type host; host cs0.lab.blablalba;
> port 23; options ondemand; }
>
> In general, the cisco's work and the PMs don't. If I telnet to the
> PMs, I get character echo. If I console to them, I don't.
>
> Any thoughts?
>
> z!
> Carl Zwanzig
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users
Re: connection to terminal server cli [ In reply to ]
On Wed, Jan 07, 2004 at 02:04:37PM -0800, Carl Zwanzig wrote:
> going well. The current bogon is that connections to the internal CLI
> on some of the terminal servers doesn't echo characters. We have both
> cisco 2511s (11.0 and 12.0) and some portmaster 2e's (3.7.2 and .2c4).

hmm...very interesting. dunno what your telnet can do, but my linux box
allows me to do 'set options' to see the telnet options negotiated. it
would be interesting to see the output of that debug info when you
connect to the portmaster and when you connect to the cisco.

so, run 'telnet', then 'set options' (inside telnet) and 'open
cs0.lab.blahblah'. then again with the other term server. normally,
you don't want either side to auto-echo...the shell should be sending
back whatever is appropriate...but the internal cli must be different
and/or expecting to see some negotiation.

dunno if we can actually find a fix, but as cfowler said, you could
change the console definition to 'type exec; exec telnet
cs0.lab.blahblah;' and avoid the problem all together. ;-) but, i'm
really interested in seeing the telnet negotiation to understand why
it's happening.

Bryan