Discussion:
[rancid] Also Problem with 'enable'
Carlos Asensio
2011-10-27 09:44:50 UTC
Permalink
Hi there,

I have the same problem with "enable" that Michael Schwartzkopff posted.

I've tried to login with the "clogin" from 2.3.6 version without success, but if I use the "clogin" from 2.3.1 it works!

How can we fix the 2.3.6 clogin version ??

Here you have the example of what I'm saying:

[***@nex-netman01 ~]$ ./bin/clogin-2.3.6 fw.noc.net
fw.noc.net
spawn ssh -c 3des -x -l nex_rancid fw.noc.net
***@fw.noc.net's password:
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit

Logoff

Connection to fw.noc.net closed.
[***@nex-netman01 ~]$ ./bin/clogin-2.3.1 fw.noc.net
fw.noc.net
spawn ssh -c 3des -x -l nex_rancid fw.noc.net
***@fw.noc.net's password:
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC> enable
Password: ************
FW-NOC#
FW-NOC# exit

Logoff

Connection to fw.noc.net closed.
[***@nex-netman01 ~]$


Thanks in advance!
Carlos.
Michael Schwartzkopff
2011-10-27 10:04:02 UTC
Permalink
Post by Carlos Asensio
Hi there,
I have the same problem with "enable" that Michael Schwartzkopff posted.
I've tried to login with the "clogin" from 2.3.6 version without success,
but if I use the "clogin" from 2.3.1 it works!
How can we fix the 2.3.6 clogin version ??
fw.noc.net
spawn ssh -c 3des -x -l nex_rancid fw.noc.net
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit
Logoff
Hi,

please do not use the '#' sign in the banner. This solved our problem.
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13
Carlos Asensio
2011-10-27 10:11:38 UTC
Permalink
Post by Carlos Asensio
Hi there,
I have the same problem with "enable" that Michael Schwartzkopff posted.
I've tried to login with the "clogin" from 2.3.6 version without
success, but if I use the "clogin" from 2.3.1 it works!
How can we fix the 2.3.6 clogin version ??
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit
Logoff
Hi,

please do not use the '#' sign in the banner. This solved our problem.

--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13

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

Hi Michael,

Thanks for your answer.

Unfortunately we have a lot of devices to manage, so it's not so easy to change the banner at all of them.

I was just wondering if the way that clogin--2.3.1 handle the prompt can be implemented/fixed at the cloing--2.3.6.

Best regards,
Carlos.
Michael Schwartzkopff
2011-10-27 10:46:03 UTC
Permalink
Post by Michael Schwartzkopff
Post by Carlos Asensio
Hi there,
I have the same problem with "enable" that Michael Schwartzkopff posted.
I've tried to login with the "clogin" from 2.3.6 version without
success, but if I use the "clogin" from 2.3.1 it works!
How can we fix the 2.3.6 clogin version ??
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit
Logoff
Hi,
please do not use the '#' sign in the banner. This solved our problem.
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München
Tel: (0163) 172 50 98
Fax: (089) 620 304 13
*************************************
Hi Michael,
Thanks for your answer.
Unfortunately we have a lot of devices to manage, so it's not so easy to
change the banner at all of them.
I am thinking about a solution to do config changes on many hosts with
cfengine. See cfengine.com. Software under GPL.

With this solution it should be possible to automate changes on many (!) cisco
devices.

Since nobody sponsors this work I have to do it in my spare time. So it can be
a while until I will finish this work. Sorry.

Greetings,
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13
Carlos Asensio
2011-10-27 11:02:27 UTC
Permalink
Post by Michael Schwartzkopff
Post by Carlos Asensio
Hi there,
I have the same problem with "enable" that Michael Schwartzkopff posted.
I've tried to login with the "clogin" from 2.3.6 version without
success, but if I use the "clogin" from 2.3.1 it works!
How can we fix the 2.3.6 clogin version ??
spawn ssh -c 3des -x -l nex_rancid fw.noc.net
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
####################################################################
# Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit
Logoff
Hi,
please do not use the '#' sign in the banner. This solved our problem.
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München
Tel: (0163) 172 50 98
Fax: (089) 620 304 13
*************************************
Hi Michael,
Thanks for your answer.
Unfortunately we have a lot of devices to manage, so it's not so easy
to change the banner at all of them.
I am thinking about a solution to do config changes on many hosts with cfengine. See cfengine.com. Software under GPL.

With this solution it should be possible to automate changes on many (!) cisco devices.

Since nobody sponsors this work I have to do it in my spare time. So it can be a while until I will finish this work. Sorry.

Greetings,

--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13

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

Thanks for the idea, Michael. We also have others software alternatives to do that, but it's little bit messy.

So I want to know if anybody knows if the way that clogin--2.3.1 handle the prompt/banner can be implemented/fixed at the cloing--2.3.6.

Best regards,
Carlos.
Daniel Schmidt
2011-10-27 15:27:28 UTC
Permalink
You have a list of devices in rancid. Use cut, split on ':' - first
column, pipe and you have list of every device on the network to put in a
textfile. Then, use ciscocmd, or iosrun to change it on all devices. Or,
just write an expect script yourself using autoexpect as a template.
Then, sit back and watch while it does the work for you.

-----Original Message-----
From: rancid-discuss-***@shrubbery.net
[mailto:rancid-discuss-***@shrubbery.net] On Behalf Of Carlos Asensio
Sent: Thursday, October 27, 2011 4:12 AM
To: rancid-***@shrubbery.net
Subject: Re: [rancid] Also Problem with 'enable'
Post by Carlos Asensio
Hi there,
I have the same problem with "enable" that Michael Schwartzkopff posted.
I've tried to login with the "clogin" from 2.3.6 version without
success, but if I use the "clogin" from 2.3.1 it works!
How can we fix the 2.3.6 clogin version ??
#####################################################################
# #
# Todos los accesos estan siendo monitorizados #
# Acceso restringido exclusivamente a personal autorizado #
# Desconecte inmediatamente #
# #
#####################################################################
Type help or '?' for a list of available commands.
FW-NOC>
FW-NOC> exit
Logoff
Hi,

please do not use the '#' sign in the banner. This solved our problem.

--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13

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

Hi Michael,

Thanks for your answer.

Unfortunately we have a lot of devices to manage, so it's not so easy to
change the banner at all of them.

I was just wondering if the way that clogin--2.3.1 handle the prompt can
be implemented/fixed at the cloing--2.3.6.

Best regards,
Carlos.
_______________________________________________
Rancid-discuss mailing list
Rancid-***@shrubbery.net
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
E-Mail to and from me, in connection with the transaction
of public business,is subject to the Wyoming Public Records
Act, and may be disclosed to third parties.
john heasley
2011-10-28 05:55:48 UTC
Permalink
Post by Carlos Asensio
Unfortunately we have a lot of devices to manage, so it's not so easy to change the banner at all of them.
I was just wondering if the way that clogin--2.3.1 handle the prompt can be implemented/fixed at the cloing--2.3.6.
it was changed to be more flexible in matching the prompt and doing so in
a manner that is not confused by information in the output. but, it cant
manage that until it sees the prompt the first time - and it must find it
somehow. hence, dont use [>#] in your banners...or dont have banners at
all.
Carlos Asensio
2011-10-28 10:20:15 UTC
Permalink
Post by Carlos Asensio
Unfortunately we have a lot of devices to manage, so it's not so easy to change the banner at all of them.
I was just wondering if the way that clogin--2.3.1 handle the prompt can be implemented/fixed at the cloing--2.3.6.
it was changed to be more flexible in matching the prompt and doing so in
a manner that is not confused by information in the output. but, it cant
manage that until it sees the prompt the first time - and it must find it
somehow. hence, dont use [>#] in your banners...or dont have banners at
all.

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

Thanks for your answer John.

I'll do that.

Best regards,
Carlos.

Continue reading on narkive:
Loading...