* WebUI and iptables GeoIP results differ after Core Update 136
@ 2019-11-08 13:30 peter.mueller
0 siblings, 0 replies; only message in thread
From: peter.mueller @ 2019-11-08 13:30 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
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, however,
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-released),
I wonder whether this is a bug in Core Update 137, some dirt left after updating,
or another of these nice little side-effects made just for me. :-)
Can anybody confirm this?
Thanks, and best regards,
Peter Müller
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-11-08 13:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-08 13:30 WebUI and iptables GeoIP results differ after Core Update 136 peter.mueller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox