[ixpmanager] IRRDB PREFIX FILTERED - possible to see reason?

[Barry O'Donovan]

Tim,

looks like you're getting tripping up by: https://git.io/JTuT4

Have you regenerated your route server config since you updated the 
irrdb database? Have you also ran irrdb:update-asn-db ?

If this doesn't help, could you pull out the relevant section of the 
Bird config for this peer and post to https://pastebin.ibn.ie/ ?

  - Barry


Tim Densmore wrote on 21/10/2020 03:57:
> Hi Folks,
> 
> I'm working on getting my AS added to a 5.7.0 installation, and for some 
> reason every prefix I advertise is being filtered.  I'm having trouble 
> determining why.
> Other members are able to advertise prefixes, and I'm receiving those 
> prefixes so it seems like it's something specific to my member info.
> I have tried both my AS-SET macro and my ASN and both produce the same 
> result.  For simplicity I'm using my ASN in these examples.
> 
> mysql> select id,maxprefixes from cust where autsys like '14818';
> +----+-------------+
> | id | maxprefixes |
> +----+-------------+
> |  8 |         100 |
> +----+-------------+
> 1 row in set (0.01 sec)
> 
> 
> mysql> SELECT @IRRDBID := irrdb FROM cust WHERE id = 8;
> +-------------------+
> | @IRRDBID := irrdb |
> +-------------------+
> |                23 |
> +-------------------+
> 1 row in set, 1 warning (0.00 sec)
> 
> 
> mysql> SELECT * FROM irrdbconfig WHERE id = @IRRDBID;
> +----+----------------+----------+--------+--------------------------------+
> | id | host           | protocol | source | notes                          |
> +----+----------------+----------+--------+--------------------------------+
> | 23 | whois.radb.net | irrd     | ALTDB  | ALTDB Query from RADB Database |
> +----+----------------+----------+--------+--------------------------------+
> 1 row in set (0.00 sec)
> 
> 
> $ bgpq3 -Al test AS14818 -S ALTDB
> no ip prefix-list test
> ip prefix-list test permit 8.10.176.0/23
> ip prefix-list test permit 63.229.162.0/24
> ip prefix-list test permit 63.233.220.0/23
> ip prefix-list test permit 65.19.0.0/18
> ip prefix-list test permit 65.19.0.0/18 ge 24 le 24
> ip prefix-list test permit 192.12.12.0/24
> ip prefix-list test permit 207.225.52.0/24
> 
> $ bgpq3 -S ALTDB -Al pl -j AS14818
> { "pl": [
>      { "prefix": "8.10.176.0\/23", "exact": true },
>      { "prefix": "63.229.162.0\/24", "exact": true },
>      { "prefix": "63.233.220.0\/23", "exact": true },
>      { "prefix": "65.19.0.0\/18", "exact": true },
>      { "prefix": "65.19.0.0\/18", "exact": false,
>        "greater-equal": 24, "less-equal": 24 },
>      { "prefix": "192.12.12.0\/24", "exact": true },
>      { "prefix": "207.225.52.0\/24", "exact": true }
> ] }
> 
> 
> 
> $ sudo php artisan irrdb:update-prefix-db 14818
> Cyber Mesa: [IPv4: 70 total; 0 stale; 0 new; DB updated] [IPv6: 1 total; 
> 0 stale; 0 new; DB updated]
> 
> 
> I'm advertising 65.19.0.0/18 and 65.19.10.0/24 to the route servers 
> currently.  Both prefixes are being filtered, with for following 
> communities applied:
> 
> 14129:1000:3RPKI NOT CHECKED
> 14129:1101:9IRRDB PREFIX FILTERED
> 14129:1001:1002IRRDB PREFIX EMPTY
> 
> Is there a way to interact directly with irrdb to verify the query it is 
> doing as well as what it returns?
> 
> Thanks,
> 
> Tim Densmore
> 
> 
> _______________________________________________
> 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