Core Update 148 (testing) report

Core Update 148 (testing) report

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

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.

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

Re: Core Update 148 (testing) report

[Michael Tremer]

[-- 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