public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: nusenu <nusenu-lists@riseup.net>
To: location@lists.ipfire.org
Subject: Re: location db mismatch
Date: Wed, 26 Jan 2022 00:10:05 +0100	[thread overview]
Message-ID: <a57fb807-3ae6-09c4-3ce7-bf5e5a8152eb@riseup.net> (raw)
In-Reply-To: <c18f93cd-3c31-e61e-a7c6-06bff82bbe8a@ipfire.org>

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

Hi Peter,

Peter Müller:
> Hello Michael,
> hello nusenu,
> hello Martin (???),
> 
> sorry for my late reply.
> 
> Yes, this change is due to an override of mine, committed as f3901759ede298e49cf5c056d0655b97e86cd211,
> affecting all location databases generated after January 9th, 2022.

thanks for your thorough reply.
For me the relevant part was that this is due to a manual override.
Maybe something I'll try to understand further: how can I easily determine if some information
is provided due to a manual override vs. the raw WHOIS information? And if it was a manual override:
What information did trigger that manual override?

I don't have any information on where these prefixes are actually located.

btw: I'm surprised that you read individual provider company websites to determine and manually override the
location of individual ASNs or prefixes of a fiven AS, I didn't expect that to be feasible :)

kind regards,
nusenu




-- 
https://nusenu.github.io

  reply	other threads:[~2022-01-25 23:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 17:15 nusenu
2022-01-21 19:02 ` nusenu
2022-01-24 16:25   ` Michael Tremer
2022-01-24 17:37     ` nusenu
2022-01-25  8:52       ` Michael Tremer
2022-01-25 18:15         ` Peter Müller
2022-01-25 23:10           ` nusenu [this message]
2022-01-29 11:18             ` Peter Müller
2022-01-26  4:17           ` Martin Gebhardt (Die LINKE.)
2022-02-04 13:40             ` Peter Müller
2022-02-06  9:48               ` Martin Gebhardt
2022-02-08 18:32                 ` Peter Müller

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=a57fb807-3ae6-09c4-3ce7-bf5e5a8152eb@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