Mailing List Archive

> Hi,
>
> I'm new to conserver and actually have a little problem with the
> escape-sequence!
>
> I changed the escape-sequence while I was connected to a console via
> telnet, with the comman ^Ece to something I can't remember!
> So how can I restore the default escape-sequence on the telnet conections
> to the consoles?
>
> Directly on the console client ^Ec is working, but if I'm connected via
> Telnet nothing happens if I send ^Ec.
>
> Please help me!
>
> Best Thx
> Andi

On Wed, Jan 17, 2007 at 09:30:08AM +0100, Nagy Andreas wrote:
> I have already tried to reinstall the pkg, but ^Ec is still not working on
> Telnet! (running conserver-con installed via pkg_add on FreeBSD 6.1)

> Sent: Donnerstag, 11. Jänner 2007 11:36
>
> I changed the escape-sequence while I was connected to a console via telnet,
> with the comman ^Ece to something I can't remember!
>
> So how can I restore the default escape-sequence on the telnet conections to
> the consoles?

the escape sequence is not permanent as it's a per-client option. as
soon as you disconnect and/or reconnect, you'll have the default ^Ec
sequence. it sounds like you've got telnet in line mode instead of
character mode (well, it's a guess). my telnet client has a 'mode
character' command to enable that. hopefully that's the problem.

just to reiterate to everyone again - it's my opinion using telnet to
interact with conserver is a "last resort" method. a simple script in
your favorite interpretive language that really deals with the basics of
the protocol would much better. and, of course, using the console
client is the best. i know folks have reasons for doing it, and that's
fine, but please be aware of the dangers. no where does anything
mention compatibility with telnet (just some similarity). but, like
many tcp-based protocols, it kinda works.

Bryan

On Wed, 2007-01-17 at 11:42 -0800, Bryan Stansell wrote:
> the escape sequence is not permanent as it's a per-client option. as
> soon as you disconnect and/or reconnect, you'll have the default ^Ec
> sequence. it sounds like you've got telnet in line mode instead of
> character mode (well, it's a guess). my telnet client has a 'mode
> character' command to enable that. hopefully that's the problem.

By default telnet client will be in line mode. The telnet server sends
an option to turn that off. Conserver does not speak the telnet
protocol so it will do nothing in regards to configuring the client.

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

Best Thx,
It worked for me!

(Note: if you change the mode while you are connected to Conserver --> it
crashes)

What would be the easiest way to start conserver automatically and provide
the standard telnet port to some Win Clients.

So that the clients only have to exec ">>telnet server-ip" then login and
call a specific console?

Security is not important, I'm only using this for trainings.
(many users are watching on the same serial-console (to a router/switch)
while one has rw access!

Thx again,
Andi

-----Original Message-----
From: users-bounces@conserver.com [mailto:users-bounces@conserver.com] On
Behalf Of Christopher Fowler
Sent: Mittwoch, 17. Jänner 2007 20:53
To: Bryan Stansell
Cc: users@conserver.com
Subject: Re: Escape-sequence on telnet connecton

On Wed, 2007-01-17 at 11:42 -0800, Bryan Stansell wrote:
> the escape sequence is not permanent as it's a per-client option. as
> soon as you disconnect and/or reconnect, you'll have the default ^Ec
> sequence. it sounds like you've got telnet in line mode instead of
> character mode (well, it's a guess). my telnet client has a 'mode
> character' command to enable that. hopefully that's the problem.

By default telnet client will be in line mode. The telnet server sends an
option to turn that off. Conserver does not speak the telnet protocol so it
will do nothing in regards to configuring the client.

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

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

On Thu, 2007-01-18 at 10:02 +0100, Nagy Andreas wrote:
> What would be the easiest way to start conserver automatically and
> provide
> the standard telnet port to some Win Clients.
>

Maybe you could change the port conserver listens on to that of telnet?



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

On Thu, Jan 18, 2007 at 10:02:06AM +0100, Nagy Andreas wrote:
> (Note: if you change the mode while you are connected to Conserver --> it
> crashes)

huh...that's unfortunate. it really should be able to cope with that
(ideally), but it's not too surprising wild data on the line would do
it. but, i'll look into fixing that.

> So that the clients only have to exec ">>telnet server-ip" then login and
> call a specific console?

why not use the console binary itself? i can build a cygwin version if
you like (i'm tempted to always provide it as a download for folks) and
all you'd need is the cygwin1.dll file. drop those two in a directory
(in your path) on the box and just run 'console foo'...

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

On Thu, 2007-01-18 at 07:51 -0800, Bryan Stansell wrote:
> why not use the console binary itself? i can build a cygwin version
> if
> you like (i'm tempted to always provide it as a download for folks)
> and
> all you'd need is the cygwin1.dll file. drop those two in a directory
> (in your path) on the box and just run 'console foo'...

I've also written a Java client that use Swing that is based on 7.X.X.
I needs to be updated for the new protocol and the VT100 emulation needs
perfection. Not sure if there are any developers other than Bryan and
me on this list.

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

Best Thx for your work, the exe is working perfectly for me!

But some users will still connect via telnet.
So is it possible to connect directly to a console via telnet (any port) or
do I always have to make connection to "telnet server-ip 782",
login, and provide a port via call or groups?
Or is it possible to configure wich port is provided, so I can make the first
conection to provide the port via script and have then always the same port
to connect to the console?

Greetings,
Andi

On Fri, Jan 19, 2007 at 12:11:01AM +0100, Nagy Andreas wrote:
> Or is it possible to configure wich port is provided, so I can make the first
> conection to provide the port via script and have then always the same port
> to connect to the console?

if you have a relatively small number of consoles you can use the -m and
-b options to make an effort to put consoles on a specific port.

conserver -m 32 -p 782 -b 783

you'd have a server that talked on 782 and the first 32 consoles would
be on port 783 (assuming nothing else was listening there). in other
words, if you did a normal login/call on the port 782 server, it would
always tell you to go talk to the server on 783 for the first 32
consoles.

hope that helps!

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

Nagy> But some users will still connect via telnet.

Why? This just boggles my mind.

Tell them to use the correct client for the connection, and now you
can actually offer it to them.

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

I think, to make the point a bit more persuasive, you could
point out that a direct telnet connection means users give
up some of the functionality they would otherwise enjoy, as
well as risking unexpected behavior when they are trying to
make critical administrative changes to their machines.

Since the console servers are the expensive part of the
equation, they get the additional benefits (from Conserver)
essentially for free. (With only a little extra effort
needed on their part to get all those benefits. :-|

Partly, this may be a "old dogs, new tricks" problem...that's
the way they have always done it. I'm still being asked to make
a "menu" wrapper...i.e. type a command, get an enumerated list
of available ports, and then the user selects a number, and
the console client would be invoked to the indicated port...all
because they are used to the ts_menu feature on the deployed
Cyclades boxes. (So, a request for a lot of programming work
that won't be shared outside the company, to help about 24 folks
who might otherwise have to learn a new trick...but, it's just
another project on the pile, and it keeps getting put on the
back burner by the requester, while folks need to practice
using the new way.. ;-)

If you need to make a hack, you just need to be sure that it
can live and grow with Conserver, without the need for wrenching
On the hack with every upgrade of Conserver, or changes to the
user base, or the names/numbers of the ports cared for by Conserver.

-Z-

-----Original Message-----
From: users-bounces@conserver.com [mailto:users-bounces@conserver.com]
On Behalf Of John Stoffel
Sent: Friday, January 19, 2007 12:46 PM
To: Nagy Andreas
Cc: users@conserver.com
Subject: Re: Escape-sequence on telnet connecton

Nagy> But some users will still connect via telnet.

Why? This just boggles my mind.

Tell them to use the correct client for the connection, and now you
can actually offer it to them.

John
_______________________________________________


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

Thx for your help!

Now everything works fine (the Win Client and the Telnet connection)!

The telnet function is only to connect from every client, also when ther is
actually no client aplicatin aviable.

On the telnet connection I can not switch to another console (^Ec;), always
getting the connected message.
But, this shouldn't be a problem (for me) at this time!


Best Thx for your great work!
Andi


-----Original Message-----
From: Harris, David (SBS US) [mailto:david.k.harris@siemens.com]
Sent: Freitag, 19. Jänner 2007 22:28
To: Nagy Andreas
Cc: users@conserver.com
Subject: RE: Escape-sequence on telnet connecton

I think, to make the point a bit more persuasive, you could point out that
a direct telnet connection means users give up some of the functionality they
would otherwise enjoy, as well as risking unexpected behavior when they are
trying to make critical administrative changes to their machines.

Since the console servers are the expensive part of the equation, they get
the additional benefits (from Conserver) essentially for free. (With only a
little extra effort needed on their part to get all those benefits. :-|

Partly, this may be a "old dogs, new tricks" problem...that's the way they
have always done it. I'm still being asked to make a "menu" wrapper...i.e.
type a command, get an enumerated list of available ports, and then the user
selects a number, and the console client would be invoked to the indicated
port...all because they are used to the ts_menu feature on the deployed
Cyclades boxes. (So, a request for a lot of programming work that won't be
shared outside the company, to help about 24 folks who might otherwise have
to learn a new trick...but, it's just another project on the pile, and it
keeps getting put on the back burner by the requester, while folks need to
practice using the new way.. ;-)

If you need to make a hack, you just need to be sure that it can live and
grow with Conserver, without the need for wrenching On the hack with every
upgrade of Conserver, or changes to the user base, or the names/numbers of
the ports cared for by Conserver.

-Z-

-----Original Message-----
From: users-bounces@conserver.com [mailto:users-bounces@conserver.com]
On Behalf Of John Stoffel
Sent: Friday, January 19, 2007 12:46 PM
To: Nagy Andreas
Cc: users@conserver.com
Subject: Re: Escape-sequence on telnet connecton

Nagy> But some users will still connect via telnet.

Why? This just boggles my mind.

Tell them to use the correct client for the connection, and now you can
actually offer it to them.

John
_______________________________________________


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

On Mon, Jan 22, 2007 at 10:17:43AM +0100, Nagy Andreas wrote:
> On the telnet connection I can not switch to another console (^Ec;), always
> getting the connected message.
> But, this shouldn't be a problem (for me) at this time!

switching consoles really just causes the client to disconnect from the
current console and connect to a new one. so, it's just like shutting
down telnet and starting up a new one. and it's just one example of how
the client/server protocol doesn't "work" with telnet (another is
'^Ec|'...you'd really get in a weird state with that one).

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