North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: AS 54271

  • From: Joel Jaeggli
  • Date: Sun Jul 13 16:10:52 2008
Scott Morris wrote: 
Wouldn't it be better to ask the folks in Hungary (AS20922) who are peering
with this site?

These are or appear to be all 20922's prefixes...

54271 is a stub from my vantage points that only appears from behind 20992.

One side, I'd buy the typo.  Both sides, mutual typos are a little  more
difficult.

looks more like a lack of clue. off-hand I'd hazard that only one party is involved.

Not that conspiracy theories are all that much fun, but I'm finding the
one-sided mistake hard to believe.  Either that or the folks at AS20922
haven't figured out that an open bgp peer isn't a great idea!  :)

Scott

-----Original Message-----
From: Joel Jaeggli [mailto:[email protected]] Sent: Sunday, July 13, 2008 1:36 PM
To: Marshall Eubanks
Cc: NANOG list
Subject: Re: AS 54271

those prefixes all have ripe route object with origin AS 20922

all the routes I see for a given prefix look like the following:

   2914 1299 12301 8696 20922 54271
     129.250.0.171 from 129.250.0.171 (129.250.0.12)
       Origin IGP, metric 1, localpref 100, valid, external
       Community: 2914:420 2914:2000 2914:3000 65504:1299

   2497 3257 12301 8696 20922 54271
     202.232.0.2 from 202.232.0.2 (202.232.0.2)
       Origin IGP, localpref 100, valid, external

   7660 2516 3257 12301 8696 20922 54271
     203.181.248.168 from 203.181.248.168 (203.181.248.168)
       Origin IGP, localpref 100, valid, external
       Community: 2516:1030

etc...

Marshall Eubanks wrote:
As of this morning, I am seeing BGP from AS 54271

*> 62.77.196.0/22 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 62.77.254.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 81.17.184.0/22 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 81.17.190.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 82.131.196.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 82.131.198.0/24 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 82.131.248.0/21 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.64.0/22 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.70.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.72.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.78.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.82.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.96.0/23 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i
*> 89.148.99.0/24 38.101.161.116 6991 0 174 3549 3549 3549 12301 8696 20922 54271 i

This ASN has not been assigned to any RIR. Is this a bogon, or does anyone know of a legitimate reason for this ?

Regards
Marshall