snar / bgpq3

bgpq3
BSD 2-Clause "Simplified" License
362 stars 53 forks source link

Inconsistent results for RIPE-NONAUTH prefixes #42

Closed afics closed 5 years ago

afics commented 5 years ago

bgpq3 results are inconsistent for routes with SOURCE: RIPE-NONAUTH.

Observed behaviour (note that only the first output is correct):

$ bgpq3 -J AS-Z-IX
policy-options {
replace:
 prefix-list NN {
    44.190.1.0/24;
    44.190.20.0/24;
 }
}

$ bgpq3 -S RIPE -J AS-Z-IX
policy-options {
replace:
 prefix-list NN {
 }
}

$ bgpq3 -S RADB,RIPE -J AS-Z-IX
policy-options {
replace:
 prefix-list NN {
    44.190.1.0/24;
 }
}

WHOIS information for said routes:

$ whois -T route 44.190.1.0/24
route:          44.190.1.0/24
descr:          approved by Brian Kantor on 2017-12-03
origin:         AS202928
mnt-by:         Z-IX-MNT
created:        2017-12-03T20:32:47Z
last-modified:  2018-09-04T19:03:15Z
source:         RIPE-NONAUTH

$ whois -T route 44.190.20.0/24
route:          44.190.20.0/24
descr:          approved by Brian Kantor on 2018-08-23
origin:         AS202928
mnt-by:         Z-IX-MNT
created:        2018-08-24T18:08:10Z
last-modified:  2018-09-04T19:39:48Z
source:         RIPE-NONAUTH

$ whois AS-Z-IX
as-set:         AS-Z-IX
descr:          Z-IX AS-SET
members:        AS202928
tech-c:         ZNR2-RIPE
admin-c:        ZNR2-RIPE
mnt-by:         Z-IX-MNT
created:        2016-05-05T18:55:19Z
last-modified:  2016-05-05T18:55:19Z
source:         RIPE

role:           Z-IX NCC Role
org:            ORG-AF83-RIPE
address:        AUSTRIA
nic-hdl:        ZNR2-RIPE
mnt-by:         Z-IX-MNT
created:        2016-04-28T18:45:27Z
last-modified:  2016-04-28T18:51:24Z
source:         RIPE # Filtered
snar commented 5 years ago

On Tue, Oct 02, 2018 at 10:22:50AM +0000, Armin Fisslthaler wrote:

bgpq3 results are inconsistent for routes with SOURCE: RIPE-NONAUTH.

bgpq3 results are consistent. -S RIPE means exactly that: include only those routes have route-object with RIPE source, routes with ARIN/APNIC/..../LEVEL3/RIPE-NONAUTH sources shall not be included. If you want to include routes with RIPE-NONAUTH source, feel free to use -S RIPE,RIPE-NONAUTH.

Observed behaviour (note that only the first output is correct):

$ bgpq3 -J AS-Z-IX policy-options { replace: prefix-list NN { 44.190.1.0/24; 44.190.20.0/24; } }

$ bgpq3 -S RIPE -J AS-Z-IX policy-options { replace: prefix-list NN { } }

$ bgpq3 -S RADB,RIPE -J AS-Z-IX policy-options { replace: prefix-list NN { 44.190.1.0/24; } }

WHOIS information for said routes:

$ whois -T route 44.190.1.0/24 route: 44.190.1.0/24 descr: approved by Brian Kantor on 2017-12-03 origin: AS202928 mnt-by: Z-IX-MNT created: 2017-12-03T20:32:47Z last-modified: 2018-09-04T19:03:15Z source: RIPE-NONAUTH

$ whois -T route 44.190.20.0/24 route: 44.190.20.0/24 descr: approved by Brian Kantor on 2018-08-23 origin: AS202928 mnt-by: Z-IX-MNT created: 2018-08-24T18:08:10Z last-modified: 2018-09-04T19:39:48Z source: RIPE-NONAUTH

$ whois AS-Z-IX as-set: AS-Z-IX descr: Z-IX AS-SET members: AS202928 tech-c: ZNR2-RIPE admin-c: ZNR2-RIPE mnt-by: Z-IX-MNT created: 2016-05-05T18:55:19Z last-modified: 2016-05-05T18:55:19Z source: RIPE

role: Z-IX NCC Role org: ORG-AF83-RIPE address: AUSTRIA nic-hdl: ZNR2-RIPE mnt-by: Z-IX-MNT created: 2016-04-28T18:45:27Z last-modified: 2016-04-28T18:51:24Z source: RIPE # Filtered

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.*

afics commented 5 years ago

I tried bgpq3 -S RIPE-NONAUTH but I didn't think about adding the actual source first. Thank you!