mmc at mmc.com.au
Tue May 12 10:56:51 UTC 2009
I'll concur with Mark.
We use RtConfig to build our EBGP from an internal aut-num object. We
mirror various RRs to build filters for peers etc.
It's working well for us, except that RtConfig ain't that fast.
The lack of having to hand craft things is great. One "make" command
builds and deploys EBGP across our network. We also use it to generate
filters to prevent stray packets leaving the network etc.
Mark Prior wrote:
> Marco d'Itri wrote:
>> On May 12, Shane Kerr <shane_kerr at isc.org> wrote:
>>> Our intuition tells us that most users want to specify a simple set of
>>> tools to do a bit of set expansion (mostly from "as-set:" objects), but
>>> mostly to pull peering data from "route:" or "aut-num:" objects. We are
>>> not really sure however.
>> Actually I doubt that many people use aut-num objects, because they are
>> at the same time quite complex to parse beyond the trivial cases and
>> often not expressive enough.
> In my previous two network architect roles I used RtConfig which
> operated on massive autnum objects (AS2764 and AS7575). AS2764 was
> generated by a perl script. RtConfig mostly worked for Cisco
> configurations but it's JUNOS code wasn't as great.
> irrtoolset mailing list
> irrtoolset at lists.isc.org
More information about the irrtoolset