Bug 12458 - re-introduce inetnum parsing for RIPE
Summary: re-introduce inetnum parsing for RIPE
Status: CLOSED FIXED
Alias: None
Product: Location Database
Classification: Unclassified
Component: Database (show other bugs)
Version: unspecified
Hardware: all All
: Will affect all users Major Usability
Assignee: Peter Müller
QA Contact: Michael Tremer
URL:
Keywords:
: 12435 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-07-11 13:18 UTC by Peter Müller
Modified: 2020-10-13 19:13 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2020-07-11 13:18:40 UTC 
Especially when it comes to IPv4, the delegated-latest file informations are a pain in the ass: Our database contains big chunks like /20s, which are not announced via BGP, so we cannot show an AS for it, and so on.

IMHO, we should parse the inetnum file again as it is at least less worse.
Comment 1 Michael Tremer 2020-08-04 09:50:05 UTC 
This ticket is not a blocker for the release, but of course should be worked on.

A test environment has been set up for Peter.
Comment 2 Peter Müller 2020-09-04 17:07:35 UTC 
This is currently under active development.
Comment 3 Peter Müller 2020-09-04 17:18:31 UTC 
*** Bug 12435 has been marked as a duplicate of this bug. ***
Comment 6 Peter Müller 2020-10-13 19:13:35 UTC 
This is fixed by now.