Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

Octothorpe in login banner or config causes router not to be gathered #62

Open
K0HAX opened this issue Jul 13, 2015 · 4 comments
Open

Comments

@K0HAX
Copy link
Contributor

K0HAX commented Jul 13, 2015

If there's an octothorpe (# symbol) in a router's config, or in the login banner the router doesn't get its configuration pulled.

@dotwaffle
Copy link
Owner

I definitely have configurations that have been fetched with # in them, which vendor router is it? I can then hopefully trace it within that specific rancid script.

@K0HAX
Copy link
Contributor Author

K0HAX commented Jul 15, 2015

It's a Cisco router, and it's in the logon banner I believe.

@ghost
Copy link

ghost commented Oct 15, 2015

EDIT: I see this in the FAQ now.

Same behavior seen on a Quagga router running FreeBSD. There was an octothorpe in the default FreeBSD MOTD (/etc/motd) causing Rancid to hang up. We're changing all of our MOTDs.

Simple fix but we were scratching our heads for a few days.

I found this article stating the same:
https://www.packetmischief.ca/2012/03/20/rancid-and-the-octothorpe/

@K0HAX
Copy link
Contributor Author

K0HAX commented Oct 18, 2015

That's not really a fix.. That's restricting what I can have in my configs, rather than fixing RANCID.
Maybe this is something I should open with upstream?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants