rtconfig and IPv6
pekkas at netcore.fi
Tue Jul 22 11:26:36 UTC 2008
On Tue, 22 Jul 2008, Tim Streater wrote:
>> @RtConfig printSuperPrefixRanges "%p/%l\n" filter afi ipv6 AS1741
> Thanks for that. At the moment we are making prefix lists by hand, which
> works because there are not too many. However won't doesn't scale in a year
> of two so automatic generation is preferred.
Indeed. We're using this for our peering sessions for some time now,
just to get advertisements (and route-objects) right from the start.
If you'd start much later, it would already be too big a swamp to
The thing you may need to do in addition is to figure out your policy
wrt more specific advertisements. RtConfig generated configuration
isn't going to help with that. We deal this by structuring inbound
policy so that first there is a prefix length etc. sanity check
(disallowing more specifics), then the prefixes are subjected to a
prefix filter (i.e. the prefix list may include e.g. /48 prefixes
which don't get accepted).
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
More information about the irrtoolset