[ixpmanager] IRR updating issue with BGPQ3

Barry O'Donovan (INEX) barry.odonovan at inex.ie
Mon Jul 3 22:43:57 IST 2023


Hi Paul,

we can't remove the -S flag as IXP administrators would then have no 
control over that IRR databases are being queried. Some databases 
contain good quality data and others not so much.

However, you can control this yourself via the IRRDB Configuration 
option in the left hand side admin menu and then setting the is each 
customer's profile as appropriate. E.g. some networks are RIPE only, 
others may be global and require multiple sources.

IXP Manager installs a bunch of options by default:

https://github.com/inex/IXP-Manager/blob/master/database/seeders/IRRDBs.php

bgpq3 also has some useful notes on this:

https://github.com/snar/bgpq3/tree/master#notes-on-database-sources--s-flag

  - Barry


> Paul Emmons via ixpmanager <mailto:ixpmanager at inex.ie>
> 3 July 2023 at 22:22
> Hello Team,
>
> Can we remove the -S flag that the IRR update is invoking??
>
> I had some time to track down some issues regarding IRR issues with 
> BGPQ3 querying RADB that seems to affect mostly North American IXPs.  
> I ran this off a test box.  We have a member AS14237 - IXPManager sees 
> the following prefixes in the IRR listing:
>
> root at ixp:/home/pemmons# /usr/bin/bgpq3 -S 'RADB' -h 'whois.radb.net' 
> -l pl -j -m 24 'AS14237'
> { "pl": [
>     { "prefix": "38.126.240.0\/22", "exact": true },
>     { "prefix": "38.126.248.0\/21", "exact": true },
>     { "prefix": "68.64.234.0\/24", "exact": true },
>     { "prefix": "192.198.233.0\/24", "exact": true },
>     { "prefix": "204.48.136.0\/21", "exact": true },
>     { "prefix": "206.72.88.0\/22", "exact": true }
> ] }
>
> They are short a bunch of prefixes.
>
> root at ixp:/home/pemmons# /usr/bin/bgpq3  -h 'whois.radb.net' -l pl -j 
> -m 24 'AS14237'
> { "pl": [
>     { "prefix": "38.123.224.0\/23", "exact": true },
>     { "prefix": "38.126.234.0\/23", "exact": true },
>     { "prefix": "38.126.236.0\/23", "exact": true },
>     { "prefix": "38.126.240.0\/22", "exact": true },
>     { "prefix": "38.126.248.0\/21", "exact": true },
>     { "prefix": "45.41.164.0\/22", "exact": true },
>     { "prefix": "45.61.64.0\/22", "exact": true },
>     { "prefix": "68.64.234.0\/24", "exact": true },
>     { "prefix": "192.198.233.0\/24", "exact": true },
>     { "prefix": "204.48.136.0\/21", "exact": true },
>     { "prefix": "206.72.88.0\/22", "exact": true },
>     { "prefix": "216.152.248.0\/21", "exact": true }
> ] }
>
> In short RADB doesn't mirror any other datasets this member uses. They 
> don't have an account with RADB; the entries listed there are proxy 
> entries from providers.
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: 
> https://www.inex.ie/mailman/listinfo/ixpmanager

-- 

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20230703/baa201bd/attachment.htm>


More information about the ixpmanager mailing list