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: libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a (was: Re: Next steps of IPFire Location)
Date: Sat, 28 Nov 2020 14:47:57 +0000	[thread overview]
Message-ID: <3d484ea9-968d-f474-160f-13af17de558f@ipfire.org> (raw)
In-Reply-To: <B3711D15-E056-4220-8539-CDD04DFA57B1@ipfire.org>

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

Hello Michael, hello *,

after having installed Core Update 153 Development Build: next/e8ecc81a on my testing machine and
rebooting, I am glad to finally confirm the libloc version included into it producing the correct
and desired output for xt_geoip within a reasonable amount of time:

> [root(a)maverick ~]# time location export --directory=tmp --format=xt_geoip
> 
> real	0m48.298s
> user	0m46.938s
> sys	0m0.301s

CPU is an Intel N3150, the system was under constant albeit medium load while executing this.

The generated IPv4 networks for DE look fine as they contain no apparent overlapping entries, while
all of them are ordered ascending. After reloading the updating procedure by running

> bash -x /usr/local/bin/update-location-database

pinging ping.ipfire.org (which is allowed by an outgoing firewall rule for destination country DE)
works again. Yay.

To conclude, libloc now finally seems to be ready for production and the more accurate database version
(which we have to generate and bake into Core Update 153, yet) - at least from my point of view.

Thanks, and best regards,
Peter Müller

      parent reply	other threads:[~2020-11-28 14:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 19:26 Next steps of IPFire Location Michael Tremer
2020-11-19 13:10 ` Michael Tremer
2020-11-20 16:27 ` Peter Müller
2020-11-22 11:59   ` Peter Müller
2020-11-23 11:16     ` Michael Tremer
2020-11-25 20:24       ` Michael Tremer
2020-11-27  8:03         ` Stefan Schantl
2020-11-27 16:48           ` Michael Tremer
2020-11-28 14:47         ` Peter Müller [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=3d484ea9-968d-f474-160f-13af17de558f@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