From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing report for Core Update 120
Date: Tue, 24 Apr 2018 12:59:02 +0100 [thread overview]
Message-ID: <1524571142.2246848.53.camel@ipfire.org> (raw)
In-Reply-To: <1da9c33c-c022-ec87-cf16-c3e7d114c3a2@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2410 bytes --]
Thank you for your feedback.
The only thing I had on my list as a blocker was dma segfaulting (https://bugzil
la.ipfire.org/show_bug.cgi?id=11701).
So far I suppose we might release next week.
Best,
-Michael
On Fri, 2018-04-20 at 19:06 +0200, Peter Müller wrote:
> Hello,
>
> I installed Core Update 120 on one machine and performed a reboot. So
> far, I am able to report the following:
>
> Squid works
> IDS works
> IPsec VPN works (except #11688)
> OpenVPN VPN works (no TLS 1.2 tested, yet)
> OpenSSH works
> WebUI works
>
> OpenSSL also uses new default cipher list and provides Chacha/Poly.
>
> However, NRPE does not work anymore, clients are unable to establish a
> SSL connection to the server listening on port 5666:
>
> Apr 20 18:53:09 firewall nrpe[9756]: Error: Could not complete SSL
> handshake. 1
>
> I guess this is related to OpenSSL 1.1, but I am not sure. strace does
> not show anything very helpful:
>
> > [pid 13832] <... close resumed> ) = 0
> > [pid 13831] <... munmap resumed> ) = 0
> > [pid 13832] getpeername(5, {sa_family=AF_INET, sin_port=htons(54200),
> > sin_addr=inet_addr("10.71.204.3")}, [16]) = 0
> > [pid 13832] rt_sigaction(SIGALRM, {0x403350, [ALRM], SA_RESTORER|SA_RESTART,
> > 0x67c135cf22e0}, {SIG_DFL, [], 0}, 8) = 0
> > [pid 13831] exit_group(0) = ?
> > [pid 13832] alarm(300) = 0
> > [pid 13831] +++ exited with 0 +++
> > [pid 13819] <... wait4 resumed> NULL, 0, NULL) = 13831
> > [pid 13819] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13831,
> > si_status=0, si_utime=0, si_stime=0} ---
> > [pid 13819] select(5, [4], NULL, [4], {0, 500000} <unfinished ...>
> > [pid 13832] read(5, "\26\3\1\0r", 5) = 5
> > [pid 13832] read(5, "\1\0\0n\3\3\321C\211\335\36\265\231wV\242\234\7\314Tm|-
> > \367\210\200\310y\233\363?^"..., 114) = 114
> > [pid 13832] getpid() = 13832
> > [pid 13832] write(5, "\25\3\3\0\2\2(", 7) = 7
> > [pid 13832] getpid() = 13832
> > [pid 13832] sendto(3, "<27>Apr 20 18:56:20 nrpe[13832]:"..., 76,
> > MSG_NOSIGNAL, NULL, 0) = 76
> > [pid 13832] close(5) = 0
> > [pid 13832] munmap(0x67c13567b000, 2187664) = 0
> > [pid 13832] exit_group(0) = ?
> > [pid 13832] +++ exited with 0 +++
>
> Any ideas?
>
> Best regards,
> Peter Müller
prev parent reply other threads:[~2018-04-24 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 17:06 Peter Müller
2018-04-24 11:59 ` 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=1524571142.2246848.53.camel@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