public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Missing ARIN data
Date: Mon, 21 Jan 2019 10:31:24 +0000	[thread overview]
Message-ID: <A60F36CC-ED4C-49AC-BDB5-0714EAD933FD@ipfire.org> (raw)
In-Reply-To: <8566d426-391a-46f5-845f-d4c6aa3ee884@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

Hi,

Hmm, partly.

The good news is:

a) We have a parser for this (looks quite similar like LACNIC, but has some differences)

b) It *seems* to have a *little* more data. It starts with 3.0.0.0/9 which is better than the other ARIN feed that we had which started around 23.x.x.x/24. However, where 1.x.x.x? And 2.x.x.x? There is loads of gaps in this and it might be that we have the same in the other data. Roughly.

The bad new is:

a) It is highly incomplete (see above)

b) We completely lost the connection between the subnets and the name of the organisation that is running it. That is quite bad unless we find another source where we get the name to an ASN.

Best,
-Michael

> On 19 Jan 2019, at 17:34, Peter Müller <peter.mueller(a)link38.eu> wrote:
> 
> Hello Michael,
> 
> searching for a way to get all needed data out of ARIN, I stumbled
> across https://ftp.arin.net/pub/stats/arin/delegated-arin-extended-latest .
> 
> Is this information helpful to you?
> 
> Thanks, and best regards,
> Peter Müller
> -- 
> Microsoft DNS service terminates abnormally when it recieves a response
> to a DNS query that was never made.  Fix Information: Run your DNS
> service on a different platform.
> 		-- bugtraq
> 


      reply	other threads:[~2019-01-21 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 17:34 Peter Müller
2019-01-21 10:31 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A60F36CC-ED4C-49AC-BDB5-0714EAD933FD@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=location@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox