From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Next steps of IPFire Location
Date: Sun, 22 Nov 2020 11:59:02 +0000 [thread overview]
Message-ID: <6b09eecd-f928-a760-d9fa-f2fc368e5fc9@ipfire.org> (raw)
In-Reply-To: <ea336ef8-d768-2870-083c-c8c7a4f21a20@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
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
next prev parent reply other threads:[~2020-11-22 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 19:26 Michael Tremer
2020-11-19 13:10 ` Michael Tremer
2020-11-19 17:48 ` Adolf Belka
2020-11-22 20:06 ` Adolf Belka
2020-11-23 11:15 ` Michael Tremer
2020-11-19 18:49 ` Stefan Schantl
2020-11-20 16:27 ` Peter Müller
2020-11-22 11:59 ` Peter Müller [this message]
2020-11-23 11:16 ` Michael Tremer
2020-11-25 20:24 ` Michael Tremer
2020-11-26 7:51 ` Arne Fitzenreiter
2020-11-26 16:21 ` Michael Tremer
2020-11-27 8:03 ` Stefan Schantl
2020-11-27 16:48 ` Michael Tremer
2020-11-28 14:47 ` libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a (was: Re: Next steps of IPFire Location) Peter Müller
2020-12-06 12:35 ` libloc output for xt_geoip is fine on Core Update 153 Development Build: next/e8ecc81a Arne Fitzenreiter
2020-12-06 20:01 ` Michael Tremer
2020-12-07 10:41 ` Adolf Belka
2020-12-07 12:16 ` Arne Fitzenreiter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b09eecd-f928-a760-d9fa-f2fc368e5fc9@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox