Curious filter matches ANY/NOT ANY problem

Mark Prior mrp at
Tue Nov 7 13:03:11 UTC 2017

On 7/11/17 23:05, Nick Hilliard wrote:
> Mark Prior wrote:
>> it seems to think that
>> 	filter "AS45355 AND NOT AS38442" matches ANY/NOT ANY
> this is a long-standing bug which presents when you have an AS object
> with both ipv4 and ipv6 route objects associated with it.

Hi Nick,

That's sad but at least it's a known bug rather than a lack of
understanding on my part :-)

> You can see the problem clearly by comparing the output of:
> % peval -e 'AS38442'
> % peval -e 'NOT AS38442'


> Honestly, you would be better off using bgpq3 and handling the asn /
> prefix set manipulation operations using a scripting language with array
> union / exclusion and other set manipulation functions.  RtConfig and
> peval were a great idea at the time, but it turned out that rpsl was too
> complicated to be able to codify into comprehensible code and too
> restrictive to be able to accurately model modern inter-domain routing
> policy.

Having been responsible for the development of two evil looking RPSL
aut-nums that were driving router configuration via RtConfig it was
convenient leaving the coding in the aut-num object rather than writing
something to manipulate the prefix sets but it would seem that RtConfig
has had some issues (and limitations) moving to two afis.


More information about the irrtoolset mailing list