bgpq3 overflow for large as numbers and accepts private as numbers about bgpq3 HOT 2 CLOSED

I created an example as-set for easy testing after hurricane fixes their set:

Vurt:~ job$ whois -h rr.ntt.net AS15562:AS-PRIV32BITASN | grep -v remarks
as-set:         AS15562:AS-PRIV32BITASN
descr:          test for bgpq3
members:        AS4200052101
members:        AS4200053111
tech-c:         DUMY-RIPE
admin-c:        DUMY-RIPE
mnt-by:         SNIJDERS-MNT
changed:        [email protected] 20000101
created:        2015-06-16T08:46:36Z
last-modified:  2015-06-16T08:46:36Z
source:         RIPE

Vurt:~ job$ bgpq3 -h rr.ntt.net -j3f1 AS15562:AS-PRIV32BITASN
{"NN": [
  -94915195,-94914185
]}
Vurt:~ job$

from bgpq3.

On Tue, Jun 16, 2015 at 01:33:46AM -0700, Henrik Thostrup Jensen wrote:

$ bgpq3 -3f1 AS-HURRICANE |tail -n 3
ip as-path access-list NN permit ^1([0-9]+)(525620|553259|559371|1973394)$
ip as-path access-list NN permit ^1([0-9]+)(2629023|-94915195|-94914185)$

Thanks for noticing, fixed and uploaded to github.

The set of private/special as number should probably be filtered out.
http://www.iana.org/assignments/iana-as-numbers-special-registry/
iana-as-numbers-special-registry.xhtml

as23456 were already in exclusion list, now all other asns in private
and reserved space are excluded by default too.

I guess that a signed int/long is used for as numbers. It should probably
be an unsigned long.

AS numbers storead as a bitmap, problem was with %i format character
that interpreted numbers > 2^31 as negative integers :( Thanks again.

from bgpq3.