Describe the bug
Saw this on a couple of ASNs when I was doing a generate, despite having bgpq-args: set, if a user has a prefixed AS-SET from peeringdb, it will ignore everything except the source provided by PeeringDB. (and doubling up on the command.)
Environment
ALL
To Reproduce
User have prefixed AS-SET on PeeringDB, while bgpq-args is set.
Expected behavior
Use bgpq-args wherever possible, and if not present, utilize prefixed as found on PDB.
Eg; (sorry Kyle, legit the first ASN I saw, and just changed it) ..
bgpq-args: -S RPKI,AFRINIC,ARIN,APNIC,LACNIC,RADB,RIPE (or any variation of it)
PeeringDB: RIPE::AS-SERVERFORGE
Spawns as bgpq4 -S RPKI,AFRINIC,ARIN,APNIC,LACNIC,RADB,RIPE -h rr.ntt.net -Ab4 -S RIPE AS-SERVERFORGE
which outputs NULL in this case;
Reason for wanting bgpq-args as primary if set.. well... people can.. be not smart sometimes :)
Describe the bug Saw this on a couple of ASNs when I was doing a generate, despite having
bgpq-args:
set, if a user has a prefixed AS-SET from peeringdb, it will ignore everything except the source provided by PeeringDB. (and doubling up on the command.)Environment ALL
To Reproduce User have prefixed AS-SET on PeeringDB, while bgpq-args is set.
Expected behavior Use bgpq-args wherever possible, and if not present, utilize prefixed as found on PDB.
Eg; (sorry Kyle, legit the first ASN I saw, and just changed it) ..
bgpq-args: -S RPKI,AFRINIC,ARIN,APNIC,LACNIC,RADB,RIPE
(or any variation of it)PeeringDB: RIPE::AS-SERVERFORGE
Spawns as
bgpq4 -S RPKI,AFRINIC,ARIN,APNIC,LACNIC,RADB,RIPE -h rr.ntt.net -Ab4 -S RIPE AS-SERVERFORGE
which outputs NULL in this case;Reason for wanting bgpq-args as primary if set.. well... people can.. be not smart sometimes :)