Mailing List Archive

well, i have two suggestions for you. first, with things shut down, can you
successfully do a 'telnet 10.92.54.13 2022' and get connected to the serial
port? if so, then things *should* be good. if not, either consoleworks is
still managing the port, or there's another problem.

if the telnet works and cranking up conserver shows the port as down, then
try running conserver with the -v option for a little more info. it should
(ideally, it should have said something without the -v) say something about
why the port is still down - like a connection refused or something of that
nature. if the -v doesn't enlighten things, try adding a -D as well. try
a connection (that results in a down message), and send me the entire log.
i might be able to tell you what's going on, if it doesn't jump out at you.

Bryan

Thank you for the quick response.

You were "spot-on" ... Consoleworks was managing the port. As soon as we
deleted the entry in Consoleworks ... conserver was able to do its stuff.

A couple of questions ...

1. All client/server traffic (including root and user passwords) is
passed
``in the clear''. Extreme care should be taken to insure no
one is
``snooping'' this private data. One day the traffic will be
encrypted.

Has anyone got any suggestions to harden the security of conserver?

2. Also, once connected to a console, how do you exit back to your
original Telnet session ... tried ctrl+c ... ctrl+d?

Many thanks
Frank


-----Original Message-----
From: bryan@conserver.com [mailto:bryan@conserver.com]
Sent: 17 September 2002 18:58
To: 'users@conserver.com'
Subject: Re: TRU64 question

well, i have two suggestions for you. first, with things
shut down, can you
successfully do a 'telnet 10.92.54.13 2022' and get
connected to the serial
port? if so, then things *should* be good. if not, either
consoleworks is
still managing the port, or there's another problem.

if the telnet works and cranking up conserver shows the port
as down, then
try running conserver with the -v option for a little more
info. it should
(ideally, it should have said something without the -v) say
something about
why the port is still down - like a connection refused or
something of that
nature. if the -v doesn't enlighten things, try adding a -D
as well. try
a connection (that results in a down message), and send me
the entire log.
i might be able to tell you what's going on, if it doesn't
jump out at you.

Bryan
_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users


*********************************************************************

The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.

On Wed, Sep 18, 2002 at 09:31:25AM +0100, Parkin Frank - fparki wrote:
> A couple of questions ...
>
> 1. All client/server traffic (including root and user passwords) is
> passed
> ``in the clear''. Extreme care should be taken to insure no
> one is
> ``snooping'' this private data. One day the traffic will be
> encrypted.
>
> Has anyone got any suggestions to harden the security of conserver?

i've mentioned a couple ideas on the users mailing list. you can do a
search on the main page to find stuff. dedicated, protected, networks
are your best bet at the moment, i believe.

> 2. Also, once connected to a console, how do you exit back to your
> original Telnet session ... tried ctrl+c ... ctrl+d?

'ctrl-e', 'c', '.' is the default sequence. the console.man page
should fill in all the details about what a client can do - everything is
accessed via 'ctrl-e', 'c' by default.

Bryan

Bryan Stansell wrote:

> On Wed, Sep 18, 2002 at 09:31:25AM +0100, Parkin Frank - fparki wrote:
> > Has anyone got any suggestions to harden the security of conserver?

> i've mentioned a couple ideas on the users mailing list. you can do a
> search on the main page to find stuff. dedicated, protected, networks
> are your best bet at the moment, i believe.

FWIW, the large show network at Networld+Interop (remember that?) always
included a unrouted (flat) network to connect all of the terminals
servers & device management ports. You could only get to it from the NOC
network via NOC routers (aggressively filtered). We would also sometimes
play games with not setting default routes on some equipment to keep
them from talking to unknown sources.

z!
Carl Zwanzig