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 directory",
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@firewall ~]# location lookup 4.231.239.118
[Errno 2] No such file or directory
[root@firewall ~]# location version
Mon, 14 Aug 2023 05:21:26 GMT
[root@firewall ~]# location --version
location 0.9.16
However, it doesn't look like the entire location database is broken:
[root@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.118;
another IPFire machine running the same Core Update and libloc version, but having
the database generated on Thu, 10 Aug 2023 05:23:53 GMT also exhibits this behavior.
Am I doing something wrong? Should this be filed as a bug?
Thanks, and best regards,
Peter Müller
