search

rfc1036 / rpsltool

A multi-target BGP configurations generator
48 stars 4 forks source link

invalid data in RIPE Database #1

Open mc opened 11 years ago

mc commented 11 years ago

Hi,

i'm trying to use rpsltool to generate a bird config. Upon IPv6 i however stumble over a prefix which is documented in the RIPE Database with out-of-boundary data.

The specific error message when running rpsltool is: error - Not an valid IP/subnet: 2404:3D00:0401::/40 at /opt/rpsltool/lib/RPSLToolTemplate.pm line 63

The valid subnet would be 2404:3D00:0400::/40 - i tried contacting the admin-c, who came back via RIPE IPRA - both of them didnt understand the issue, hence i claim i tried the political way. ;)-

Anyway: there's a need to run the tool even when encountering invalid data, i know the problem actually comes from Net::IP who declares the prefix as being wrong (and it is right there), i hence propose (my perl's a bit too rusty for this task):

  1. fix out-of-boundary errors by writing out the correct prefix
  2. add an parameter to rpsltool which just drops the prefix out of the generated list when this error is enountered - and possibly write a Warning to STDERR
  3. add an configuration item which makes it possible to match and substitute prefixes BEFORE the list is handed to Net::IP, so that one can manually fix the problem ("--substitute +2404:3D00:0401::/40+2404:3D00:0400::/40+")

Of course i'll take other suggestions which may workaround this, too.

THANKS! -mc

rfc1036 commented 11 years ago

IIRC you can work around this by unimporting the ASN announcing the broken prefix in the neighbour definition. 1 I fear would be way too slow, 2 I do dot like silently losing information, 3 is just too ugly.