>while updating our database we've noticed some
>inconsistency in ripe-db route object: 80.82.178.0/20
>so does anybody know why net and prefix combination for
>route object could be invalid ?
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
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...
>With respect,
>---
>RIPN Registry center
>-----
>
>--------------------------------------------------------------------
>
>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(a)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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
