From mboxrd@z Thu Jan  1 00:00:00 1970
From: peter.mueller@ipfire.org
To: development@lists.ipfire.org
Subject: WebUI and iptables GeoIP results differ after Core Update 136
Date: Fri, 08 Nov 2019 13:30:00 +0000
Message-ID: <4f5cfe1b-1c6f-4e0b-0df5-729948e58328@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5365140510372392431=="
List-Id: <development.lists.ipfire.org>

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

Hello *,

I stumbled across 147.75.101.1 (ams1.edge.kernel.org) the other day when
downloading an ISO file. The ipinfo.cgi shows US flag as GeoIP result, howeve=
r,
an iptables rule works for NL only - which is the more correct result as
far as I can tell (physical location vs. jurisdiction).

Since the machine is running on Core Update 137, and Core Update 136 fixes
this issue (see: https://blog.ipfire.org/post/ipfire-2-23-core-update-136-rel=
eased),
I wonder whether this is a bug in Core Update 137, some dirt left after updat=
ing,
or another of these nice little side-effects made just for me. :-)

Can anybody confirm this?

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

--===============5365140510372392431==--