Open K0HAX opened 9 years ago
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.
It's a Cisco router, and it's in the logon banner I believe.
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/
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?
If there's an octothorpe (# symbol) in a router's config, or in the login banner the router doesn't get its configuration pulled.