[ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"

>>The guy seems to be asking for *adding* objects for the *old*
>>beacon prefixes to the RIPE DB:

> OK, let me rephrase this :-)  Can we check if we have the correct route
> objects for what is currently announced _and_ that nothing of the old
> beacons is announced anymore?


(ris)whois is your friend :)


  x27$ whois -T route -M 84.205.64.0/19 | grep route | wc
     32      64     928

i.e. 32 route objects in the DB, starting 84.205.64.0/24
and ending with 84.205.95.0/24

   x27$  whois -h riswhois -F -M 84.205.64.0/19 |grep 12654
   12654  84.205.72.0/24   49
   12654  84.205.80.0/24   54
   12654  84.205.81.0/24   49
   12654  84.205.82.0/24   54
   12654  84.205.83.0/24   45
   12654  84.205.84.0/24   1
   12654  84.205.85.0/24   64
   12654  84.205.87.0/24   60
   12654  84.205.90.0/24   10
   12654  84.205.91.0/24   52
   12654  84.205.92.0/24   72


RISwhois only sees the anchor prefixes, as the beacons
are always withdrawn at the times of the bview dumps

The anchor prefix 84.205.86.0/24 from rrc06, japan, 
is not seen by any other RRC; probably does not
get transit from any of the DIX-IE peers


   x27$  whois -h riswhois -M 195.80.224.0/20
   % This is RIPE NCC's Routing Information Service
   % whois gateway to collected BGP Routing Tables
   % IPv4 or IPv6 address to origin prefix match
   %
   % For more information visit http://www.ripe.net/ris/riswhois.html

   % No entries found


The true ON/OFF Beacons were never seen, so their absence from riswhois
doesn't say much on the status of these, but the 195.80.239.0/24
anchor prefix and the anycast simulation 195.80.233.0/24 prefix
from rrc01 were in RISwhois before and have now disappeared.

-- Rene