From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: "location lookup 4.231.239.118" results in "[Errno 2] No such file or
 directory"
Date: Mon, 14 Aug 2023 20:06:00 +0000
Message-ID: <a84ac262-6369-495c-9dcc-4d5eef7ee860@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8238933167112464300=="
List-Id: <location.lists.ipfire.org>

--===============8238933167112464300==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Michael,

just something I encountered today while checking on a bunch of IP addresses:
Trying to look up 4.231.239.118 results in "[Errno 2] No such file or directo=
ry",
an error I didn't expect to surface at this point, and I'm not sure what to
make out of it.

Behavior on the system (IPFire running Core Update 177) is as follows:

[root(a)firewall ~]# location lookup 4.231.239.118
[Errno 2] No such file or directory
[root(a)firewall ~]# location version
Mon, 14 Aug 2023 05:21:26 GMT
[root(a)firewall ~]# location --version
location 0.9.16

However, it doesn't look like the entire location database is broken:

[root(a)firewall ~]# location lookup 8.8.8.8
8.8.8.8:
  Network                 : 8.8.8.0/24
  Country                 : United States of America
  Autonomous System       : AS15169 - GOOGLE
  Anycast                 : yes

So far, I have only encountered this behavior in conjunction with 4.231.239.1=
18;
another IPFire machine running the same Core Update and libloc version, but h=
aving
the database generated on Thu, 10 Aug 2023 05:23:53 GMT also exhibits this be=
havior.

Am I doing something wrong? Should this be filed as a bug?

Thanks, and best regards,
Peter M=C3=BCller

--===============8238933167112464300==--