From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Core Update 148 (testing) report
Date: Sun, 09 Aug 2020 12:25:06 +0100 [thread overview]
Message-ID: <A8BC83E1-8BBE-457E-9EFE-E76415C2B982@ipfire.org> (raw)
In-Reply-To: <ac196fc4-0fd9-3577-af0b-2bb900b33c97@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
Hey,
> On 9 Aug 2020, at 08:41, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello *,
>
> Core Update 148 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-148-is-available-for-testing)
> is running here for about a week without any major issues so far. Sorry for being
> late this time.
>
> Looking at the ipinfo.cgi, it currently displays the country returned by the location
> database, which should always be a valid one, as we decided not no override them for
> "special" IP addresses such as anonymous proxies, satellite providers, or anycast networks.
>
> However, we do not display this information to the user. While I have no idea about
> how to do that for CGIs such as the DNS settings, or the connection tracking table,
> the ipinfo.cgi should contain such information from my point of view.
>
> (I suspect this raising questions in the community as well.)
>
> It would be nice to have AS information displayed on ipinfo.cgi as well, but since we do
> not process them elsewhere, this is definitively not a show-stopper.
What is stopping you from implementing this?
If it is the perl module, I am sure that Stefan can help. We have been talking about implementation details over the phone this week.
> Thanks to Michael for being the "master of disaster" behind libloc (no offense intended ;-) )
> and providing me with answers to it and testing environment. Thanks to Stefan for
> building the Perl bindings and adjusting CGIs and firewall scripts.
:)
>
> Thanks, and best regards,
> Peter Müller
-Michael
prev parent reply other threads:[~2020-08-09 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 7:41 Peter Müller
2020-08-09 11:25 ` Michael Tremer [this message]
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=A8BC83E1-8BBE-457E-9EFE-E76415C2B982@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@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