RtConfig has limited cache support

Hagen Boehm hboehm at brutus.NIC.DTAG.DE
Tue May 15 16:54:43 UTC 2007


Hi there,

I tried to resolve a route-set from a cache file with RtConfig but the
result was:

$ RtConfig -h whois.radb.net -protocol irrd -f rpsl-data             
RtConfig> @RtConfig access_list filter AS65000:RS-TEST
Warning: filter "AS65000:RS-TEST" matches ANY/NOT ANY

When using whois.ripe.net with protocol ripe however the result is:

$ RtConfig -h whois.ripe.net -protocol ripe -f rpsl-data
RtConfig> @RtConfig access_list filter AS65000:RS-TEST
!
no access-list 100
access-list 100 permit ip 192.168.2.0   0.0.1.0   255.255.255.0   0.0.0.0
access-list 100 permit ip 192.168.4.0   0.0.3.0   255.255.255.0   0.0.0.0
access-list 100 permit ip 192.168.8.0   0.0.0.0   255.255.255.0   0.0.0.0
access-list 100 permit ip 192.168.8.1   0.0.0.0   255.255.255.255   0.0.0.0
access-list 100 deny ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255

When I took a look into the code I found out that cache usage is only
implemented for protocol "ripe" (birdwhoisc). The cache file gets never
accessed to resolve any rpsl reference when the protocol is set to "irrd"!!!
:-(

Is there a reason for this? Has there been cache support for "irrd" in one
of the former IRRToolSet Versions?

Currently I'm working on a fix, but it would be nice to know the reason
for the limited cache support.

Thanks!


    Hagen


More information about the irrtoolset mailing list