public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a
Date: Mon, 07 Dec 2020 13:16:36 +0100	[thread overview]
Message-ID: <017b52ef9fb99267fcf4cd0c6fbcb0da@ipfire.org> (raw)
In-Reply-To: <F859965D-3511-4B09-BD05-B8B8800E09E5@ipfire.org>

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

Am 2020-12-06 21:01, schrieb Michael Tremer:
> Hi,
> 
> Thank you, Arne, for testing.
> 
> It is good to know that this algorithm finishes on this device.
> 
> However, this is still not really acceptable for an IPFire device in 
> production.
> 
> I would absolutely encourage to upgrade :)
Off course this is not a production system. I had to search it because i 
need it at
work to build a server for a BME280 sensor chip (temperature, humidity 
and pressure).

Arne

> 
> -Michael
> 
>> On 6 Dec 2020, at 13:35, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>> 
>> Now i have done a new test on a first gen RPi1 (256MB) version:
>> 
>> 
>> [root(a)RPi1 ~]# free
>>             total       used       free     shared    buffers     
>> cached
>> Mem:        227244     133060      94184          0       6988      
>> 71416
>> -/+ buffers/cache:      54656     172588
>> Swap:            0          0          0
>> [root(a)RPi1 ~]# uname -a
>> Linux RPi1.localdomain 4.14.210-ipfire-multi #1 SMP Wed Dec 2 23:46:20 
>> GMT 2020 armv6l BCM2835 GNU/Linux
>> [root(a)RPi1 ~]# rm /var/lib/location/database.db
>> rm: remove regular file '/var/lib/location/database.db'? y
>> [root(a)RPi1 ~]# time update-location-database
>> Downloaded new database from Sun, 06 Dec 2020 04:34:29 GMT
>> Reloading firewall                                                     
>> [  OK  ]
>> 
>> real	14m28.682s
>> user	12m45.663s
>> sys	0m17.090s
>> 
>> I think this time and xt_ipv4 output looks ok.
>> Also the bug if the WebIF that firewall rules could not created on 
>> machines with low ram seems to be fixes.
>> 
>> Arne

      parent reply	other threads:[~2020-12-07 12:16 UTC|newest]

Thread overview: 19+ 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-19 17:48   ` Adolf Belka
2020-11-22 20:06     ` Adolf Belka
2020-11-23 11:15       ` Michael Tremer
2020-11-19 18:49   ` Stefan Schantl
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-26  7:51         ` Arne Fitzenreiter
2020-11-26 16:21           ` Michael Tremer
2020-11-27  8:03         ` Stefan Schantl
2020-11-27 16:48           ` Michael Tremer
2020-11-28 14:47         ` libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a (was: Re: Next steps of IPFire Location) Peter Müller
2020-12-06 12:35           ` libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a Arne Fitzenreiter
2020-12-06 20:01             ` Michael Tremer
2020-12-07 10:41               ` Adolf Belka
2020-12-07 12:16               ` Arne Fitzenreiter [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=017b52ef9fb99267fcf4cd0c6fbcb0da@ipfire.org \
    --to=arne_f@ipfire.org \
    --cc=development@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