public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: nusenu <nusenu-lists@riseup.net>
To: location@lists.ipfire.org
Subject: incorporation state of ARIN's asn.txt
Date: Sat, 26 Jun 2021 19:07:00 +0200	[thread overview]
Message-ID: <55a8df26-0559-aedf-4d0f-ba5a15a6927a@riseup.net> (raw)

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

Hi,

I'm an indirect user of ipfire IP -> ASN and ASN -> AS name data
since the torproject recently switched from an outdated maxmind db to ipfire's database
on 2021-06-18.

When the switch from maxmind to ipfire's db occurred I observerd a significant increase
of ASes without AS name.

I did read the recent threads on this mailing list about "Import (technical) AS names from ARIN",
which I assume should improve or entirely solve the situation.

Is my understanding correct that your recent work [1] on adding ARIN's AS name [2] data has been merged?

[1] https://lists.ipfire.org/pipermail/location/2021-June/000394.html
[2] https://ftp.arin.net/info/asn.txt

As a test I manually verified AS14061

> 14061                   DIGITALOCEAN-ASN

and was unable find the AS name when using ipfire's db.

example lookup:
https://location.ipfire.org/lookup/134.209.159.74

Should I already see ARINs asn.txt AS name information or will this be
"visible" in ipfire's db in the near future?

kind regards,
nusenu


-- 
https://nusenu.github.io

             reply	other threads:[~2021-06-26 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 17:07 nusenu [this message]
2021-06-26 19:46 ` Peter Müller
2021-06-27 10:14   ` incorporation state of ARIN's asn.txt / LACNIC AS name data nusenu
2021-06-27 20:13     ` Peter Müller
2021-07-10 20:17       ` Peter Müller
2021-07-10 21:46         ` nusenu
2021-07-14 16:43     ` Michael Tremer
2021-07-14 21:03       ` nusenu
2021-07-15 15:49         ` Michael Tremer

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=55a8df26-0559-aedf-4d0f-ba5a15a6927a@riseup.net \
    --to=nusenu-lists@riseup.net \
    --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