headers
john heasley | 9 Aug 2002 20:40

rancid 2.2.2

i've made rancid-2.2.2 available for ftp from ftp.shrubbery.net:/pub/rancid

*** if you make use of the looking glass (lg) scripts that come with rancid,
    PLEASE upgrade.  previous versions did not check the query target properly,
    allowing someone with access to the looking glass to query any device
    which can be logged into.

possible bug: a user to whom we supplied an EFT copy of flogin told us that
it did not work with certain devices, but became silent when we asked for
more information.

2.2.2
        *login: fix handling of userprompt et al so that {}'s are used in
        .cloginrc as they are with every other .cloginrc directive.

        f10rancid: Fix to pick up new info in show version output.

        jrancid: Ignore Timecounter "TSC" in show system boot-messages output.

        rancid: filter tty line speed when configured for auto-configure

        flogin: bring login() and do_enable() in-line with [cj]login.  also
        match "telnet server disabled" - from brad volz.

        control_rancid: report devices added to router.db - from Fredrik Thulin
        also eliminate empty up/down lists.

        rancid/jrancid: filter isis passwords - partial from Janos Mohacsi

        lg: make o/p from the lg stream (unbuffered), so one doesnt have
(Continue reading)

Permalink | Reply | 0 comments |
headers
rancid | 25 Aug 2002 00:53

customize commands

Forgive the newbie. Implementation and general satisfaction meets expectations.... However, I would
like to know how to customize the commmands set used by do-diffs. (I attempted to sort through archives,
but ugh.)
--

-- 
sig=$header
Permalink | Reply | 3 comments |
headers
john heasley | 25 Aug 2002 21:26

Re: customize commands

Sat, Aug 24, 2002 at 05:53:49PM -0500, rancid:
> Forgive the newbie. Implementation and general satisfaction meets expectations.... However, I would
like to know how to customize the commmands set used by do-diffs. (I attempted to sort through archives,
but ugh.)
> -- 
> sig=$header

there isnt such a facility built-in at the moment.  we have been discussing
how to add this though.  so, its coming at some point.
Permalink | Reply | 2 comments |
headers
Jay Borkenhagen | 29 Aug 2002 17:42
Favicon

Re: customize commands

>> Forgive the newbie. Implementation and general satisfaction meets
>> expectations.... However, I would like to know how to customize the
>> commmands set used by do-diffs. (I attempted to sort through
>> archives, but ugh.) 

heas> there isnt such a facility built-in at the moment.  we have been
heas> discussing how to add this though.  so, its coming at some
heas> point.

As someone who just upgraded to rancid-2.2.2 thereby unintentionally
clobbering my modifications to bin/rancid's list of router commands of
interest, let me voice my support for such a facility.  I see that
"make install" preserved my modified bin/env file with the new one
ending up in bin/env.new -- it would be terrific if the command set
was in a file which would be similarly preserved across an upgrade.

Thanks.
						Jay B.

--

-- 
  Jay Borkenhagen     jayb <at> braeburn.org
Permalink | Reply | 1 comment |
headers
john heasley | 29 Aug 2002 18:07

Re: customize commands

Thu, Aug 29, 2002 at 11:42:08AM -0400, Jay Borkenhagen:
> >> Forgive the newbie. Implementation and general satisfaction meets
> >> expectations.... However, I would like to know how to customize the
> >> commmands set used by do-diffs. (I attempted to sort through
> >> archives, but ugh.) 
> 
> heas> there isnt such a facility built-in at the moment.  we have been
> heas> discussing how to add this though.  so, its coming at some
> heas> point.
> 
> As someone who just upgraded to rancid-2.2.2 thereby unintentionally
> clobbering my modifications to bin/rancid's list of router commands of
> interest, let me voice my support for such a facility.  I see that
> "make install" preserved my modified bin/env file with the new one
> ending up in bin/env.new -- it would be terrific if the command set
> was in a file which would be similarly preserved across an upgrade.
> 

the idea we've been kicking around is to have a file (a default file
included with the dist and perhaps a "file.local") which defines a
device "type".

for a given type, you could set which commands you wanted collected and
what function (including home-grown external scripts) to use to filter
the output.  this "type" is then used as the type in the router.db file,
eg: cisco or cisco_osr, where cisco_sla might have additional (or
fewer) commands for your OSRs.
Permalink | Reply | 0 comments |

Gmane