[ris-int] Re: Fwd: 220.127.116.11 - 18.104.22.168 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
Fri Feb 4 16:06:44 CET 2005
>>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 22.214.171.124/19 | grep route | wc 32 64 928 i.e. 32 route objects in the DB, starting 126.96.36.199/24 and ending with 188.8.131.52/24 x27$ whois -h riswhois -F -M 184.108.40.206/19 |grep 12654 12654 220.127.116.11/24 49 12654 18.104.22.168/24 54 12654 22.214.171.124/24 49 12654 126.96.36.199/24 54 12654 188.8.131.52/24 45 12654 184.108.40.206/24 1 12654 220.127.116.11/24 64 12654 18.104.22.168/24 60 12654 22.214.171.124/24 10 12654 126.96.36.199/24 52 12654 188.8.131.52/24 72 RISwhois only sees the anchor prefixes, as the beacons are always withdrawn at the times of the bview dumps The anchor prefix 184.108.40.206/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 220.127.116.11/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 18.104.22.168/24 anchor prefix and the anycast simulation 22.214.171.124/24 prefix from rrc01 were in RISwhois before and have now disappeared. -- Rene
[ Ris-int Archive ]