public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: location db mismatch
Date: Sat, 29 Jan 2022 11:18:04 +0000	[thread overview]
Message-ID: <84d68277-b771-aae2-1a40-fa74351a9607@ipfire.org> (raw)
In-Reply-To: <a57fb807-3ae6-09c4-3ce7-bf5e5a8152eb@riseup.net>

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

Hello nusenu,

> 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? 

unfortunately, there is no way of telling from the location database itself, since it does not contain
the source (RIR, ISP geofeed, override, etc.) of a dataset due to space reasons.

However, manual overrides are always handed in as patches on this mailing list. If they are accepted,
you will find them in the location-database Git repository (https://git.ipfire.org/?p=location/location-database.git;a=summary).
Also, Patchwork (https://patchwork.ipfire.org/project/location/list/) tracks them, so it should be at
least transparent which overrides were in place in a given timespan.

Today, I am the only person creating them, but would really love to see other people becoming active
in this topic as well. Triggers for overrides are usually abusive or security-related activities I
observe somewhere else, feedback from the IPFire community, or mentions at other mailing lists. As soon
as I suspect such a network to have inaccurate or deliberately false country information set, I take
a mental note of it.

Should an investigation confirm this, I create an override. Unless it is something urgent, I batch
them on a (more or less) weekly basis, and send them to this mailing list.

> 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 given AS, I didn't expect that to be feasible

Indeed, this is probably not feasible at a large scale, and I don't do this preemptively, only if
a network arises my suspicion. To the best of my knowledge, IPFire Location is less inaccurate -
I won't claim we're "more accurate", since defining accuracy is tricky here - than its freely available
competitors. At least that's the decision the Tor project came to.

However, I would love to see other people becoming active in this, especially with knowledge of
parts of the world I lack oversight of. A "best-effort" approach is completely fine to me, and IMHO
better than anything else we've currently got.

Hope to have your question answered.

Thanks, and best regards,
Peter Müller


  reply	other threads:[~2022-01-29 11:18 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
2022-01-29 11:18             ` Peter Müller [this message]
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=84d68277-b771-aae2-1a40-fa74351a9607@ipfire.org \
    --to=peter.mueller@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