This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
route object check-up
- Previous message (by thread): route object check-up
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Engin Gunduz
engin at ripe.net
Fri Dec 28 17:21:58 CET 2001
Hi Oleg, all, On Fri, 28 Dec 2001, Oleg N. Bondarev wrote: > On Fri, 28 Dec 2001, Wilfried Woeber, UniVie/ACOnet wrote: > > > When the starting address is not properly aligned on a power of 2 for > > the block-size. > > > > The hint you are receiving, as attached below, is an indication for > > this, i.e. > > - 80.82.178.0 is only properly aligned for 2 consecutive Class Cs, > > 80.82.178.0 and 80.82.179.0), > > - whereas for a /20 (16 consecutive Class Cs) the proper alignment would > > be 80.82.176.0 > > but we've faced with ripe db impossibility of checking this > inconsistency since notification attached below was formed by our robot > wich does not allow to create object 80.82.178.0/20 and notifies > us that something wrong in ripe db > > > > > Btw, the same issue might eventually arise when someone tries to do an > > aggregated announcement on the routing layer for this block. > > > > Possible solutions: > > - move the address block to the proper alignment > > - partiton the block into a set of smaller, consecutive, aligned chunks > > - try to register the address as a range (although this might trigger > > the same error message, depending on implementation of checks...) > > > > I guess the older versions of the software were less picky than the new > > implementation is... > > > > it seems to be vise virsa - new implementation of the software is less picky You are right here, the current software accepts this kind of incorrect route objects. We are in the process of rewriting the syntax checker part of the software, which will solve this and some other similar problems, and also improve the consistency of the code itself. We expect it to be in production in a month, probably before the next RIPE meeting. Regards, Engin Gunduz RIPE NCC Database Group > > > > > > >Update [FAILED] > > > > > >dbupdate: > > >80.82.178.0/20 is an invalid net and prefix combination:- > > >length 20 (mask 255.255.240.0) is outside the range of 80.82.178.0 > > >Possible values with these combinates are: > > >based on length 80.82.176.0/20 > > >based on prefix 80.82.178.0/23 > > > > Regards, > > _________________________________:_____________________________________ > > Wilfried Woeber : e-mail: Woeber at CC.UniVie.ac.at > > UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 > > Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 > > A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > With respect, > --- > RIPN Registry center > ----- >
- Previous message (by thread): route object check-up
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]