[ris-int] RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20]
Arife Vural arife at ripe.net
Wed May 25 12:15:29 CEST 2005
When I looked at the config files, it looks we do not announce those old Beacon prefixes, but still they are allowed in access-list for outgoing traffic. I will clean-up old Beacon prefixes from access-list, but I'm not sure that will help or not. I will check it out with James if problem still stays. Arife On Fri, May 20, 2005 at 02:03:11PM +0200, Rene Wilhelm wrote: > Hi Mike, > > > You returned 195.80.224/20 in February so we wanted to start using the range > > for our customers now. > > > > However for some reasons you started using it again for RIS. > > > > whois -h riswhois -M 195.80.224/20 > > > > route: 195.80.239.0/24 > > origin: AS12654 > > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > > lastupd-frst: 2005-05-19 11:33Z 80.81.192.30 at rrc12 > > lastupd-last: 2005-05-19 12:33Z 80.81.192.126 at rrc12 > > seen-at: rrc12 > > num-rispeers: 2 > > source: RISWHOIS > > > > > > So, what are you plans now? > > I think this announcement somehow came back by mistake. RIS is not > allowed to use the address range as it has been returned to you officially. > > The RIS operators should be able to find out what exactly is happening, > I'm cc-ing them (as well as the internal ris-int list) on this mail. > > RIS folk: > > Though querying the RIS DB for this range via the risearch.html > CGI yields zero results, the looking-glass pages do see 195.80.239.0/24 > being announced to rrc12 by 2 peers at the DE-CIX. > > http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC121&query=1&arg=195.80.239.0%2F24 > > > Regards, > > -- Rene
[ Ris-int Archives ]