[28077] in North American Network Operators' Group
Re: peering tools
daemon@ATHENA.MIT.EDU (Alex Rubenstein)
Sat Apr 8 11:07:58 2000
Date: Sat, 8 Apr 2000 11:05:51 -0400 (EDT)
From: Alex Rubenstein <alex@nac.net>
To: Scott Call <scall@devolution.com>
Cc: "nanog@merit.edu" <nanog@merit.edu>
In-Reply-To: <38EE2D9F.FAF5B9E8@devolution.com>
Message-ID: <Pine.BSF.4.10.10004081103580.98825-100000@iago.nac.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> So, my question to you all is:
>
> Do you?
>
> a> Use RtConfig
We don't. IMHO, it's bloated and way more that I need. NAC has written
some tools, but they are part of our entire billing package, and it will
read the RA for routing updates.
> b> Use other publicly available code
See a>.
> c> Use "in-house" code that's not public
See a>.
> d> Do it by hand.
We used to, and it will scale somewhat if you use peer-groups extensively.
However, once you start to do 'special cases' more and more, it does get
cumbersome.
