From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 133 (testing) report
Date: Sun, 16 Jun 2019 14:47:00 +0000 [thread overview]
Message-ID: <0a239f0a-2989-61b3-8eb8-528147a9618d@ipfire.org> (raw)
In-Reply-To: <2a5ccb4c-c62d-a4ec-357e-d220f5109356@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Hello *,
just some minor corrections and additions...
> Hello *,
>
> this is just a quick testing report for upcoming Core Update 133
> (see: https://blog.ipfire.org/post/ipfire-2-23-core-update-133-ready-for-testing).
>
> The following parts of IPFire seem to work correctly:
> - DDNS
> - Squid proxy (including upstream proxy)
> - OpenVPN (RW connections only)
> - Suricata
By the way: I am currently observing a ton of scans coming from 92.118.37.0/24 .
Just in case anyone is interested in. :-/
> [...]
>
> /var/log/bootlog however, states current microcodes have been loaded:
>> [ 0.000000] microcode: microcode updated early to revision 0x368, date = 2019-04-23
>> [ 0.000000] Linux version 4.14.121-ipfire (root(a)helena.ipfire.org.ipfire.org) (gcc version 7.3.0 (GCC)) #1 SMP Wed May 22 13:45:15 GMT 2019
>
> (Two glitches here: "helena.ipfire.org.ipfire.org" and GCC 7.3.0 .
> I thought the toolchain now uses GCC 8.0?!)Since we did not ship an updated Linux kernel, I guess this cannot
say "GCC 8.x" yet. Sorry.
> [...]
Thanks, and best regards,
Peter Müller
--
The road to Hades is easy to travel.
-- Bion of Borysthenes
next prev parent reply other threads:[~2019-06-16 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 14:26 Peter Müller
2019-06-16 14:47 ` Peter Müller [this message]
2019-06-17 7:22 ` Arne Fitzenreiter
2019-06-17 13:45 ` Peter Müller
2019-06-17 15:57 ` Michael Tremer
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=0a239f0a-2989-61b3-8eb8-528147a9618d@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