I have thousands of switches where the company banner proudly flies in ASCII art made exclusively of #-marks.
This, according to the rancid FAQ, is a show stopper:
Q. Are there any characters in the banner that rancid has problems with OR
I changed the device's command prompt and now collection is failing?
A. The trickiest part about clogin (et al) is recognizing the prompt
correctly. clogin looks for '>' and '#' to figure out if it is logged
in or in enable mode. So if you have a '>' or '#' in your login banner
(or other motd), then clogin gets confused and will not be able to log
in correctly, and thus rancid will fail.
Don't use '>' or '#', or whatever the termination character of the given
device's prompt is, in your prompt or in your banner or other motd.
Obviously, I can't change all of the banners. Even if I could, I'd have used clogin
, soooo...
Has anyone hacked together a workaround for this?
If it helps, in my case there banner lines all start with at least three spaces.
'#'
or'>'
. Create a regex or similar that looks for'*#$'
(which is pseudo regex by the way!). I'm trying to suggest there'anything before a # then end of line'
.