public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 136 (testing) report
Date: Thu, 19 Sep 2019 09:17:22 -0400	[thread overview]
Message-ID: <1ACD2F9E-E00E-4328-BAA7-2133E6536F51@ipfire.org> (raw)
In-Reply-To: <90a873f0-4fb3-ea6e-f725-58f6716d4c63@ipfire.org>

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

Hi,

> On 17 Sep 2019, at 10:25, peter.mueller(a)ipfire.org wrote:
> 
> Hello list,
> 
> Core Update 136 (testing, https://blog.ipfire.org/post/ipfire-2-23-core-update-136-is-available-for-testing)
> is running here for ~ 20 hours without any known issues so far.
> 
> The following parts of IPFire seem to work correctly:
> - DDNS
> - OpenVPN (RW connections only)
> - IPsec (N2N connections only)
> - Squid proxy (including authentication and upstream proxy)
> - Guardian
> 
> Because of several issues, I have not tested Suricata so far,
> but will do with Stefans ISO later. Tor starts up correctly and
> is able to establish its circuits - there is a strange behaviour
> related to some operation mode, which I will investigate further
> and report back if it is a bug.
> 
> I can confirm the WebUI now shows the correct country for IP
> addresses again. Thanks for this, it makes debugging much easier.
> However, I still think we need libloc some day... :-)

Oh yes, the lovely libloc...

> 
> Thanks, and best regards,
> Peter Müller

Thanks for testing and the feedback though.

I suppose we are leaving this update for testing a little bit longer because the replacement of Perl might cause some rather corner-case problems (see the one that Erik has found).

Best,
-Michael

      reply	other threads:[~2019-09-19 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 14:25 peter.mueller
2019-09-19 13:17 ` 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=1ACD2F9E-E00E-4328-BAA7-2133E6536F51@ipfire.org \
    --to=michael.tremer@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