From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Next steps of IPFire Location Date: Sun, 22 Nov 2020 11:59:02 +0000 Message-ID: <6b09eecd-f928-a760-d9fa-f2fc368e5fc9@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9186189050099386304==" List-Id: --===============9186189050099386304== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello *, I just stumbled across a strange issue on my testing machine strongly reminding me of a problem with the xt_geoip module if we printed the location database contents non-planar: For debugging and monitoring reasons, a NRPE job pinging ping.ipfire.org (which resolves to 81.3.27.38) is executed periodically. Since a few hours, this job fails due to ICMP packets to this IP address being dropped by the outgoing firewall engine. Its policy is set to "drop", with a rule allowing ICMP traffic to DE. While "location lookup 81.3.27.38" correctly returns DE for the prefix 31.8.0.0/18, it seems as the xt_geoip module did not get that and misclassifies this IP address. Is somebody able to verify or falsify this issue on Core Development Build 153? Thanks, and best regards, Peter Müller --===============9186189050099386304==--