From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 133 (testing) report
Date: Mon, 17 Jun 2019 09:22:01 +0200
Message-ID: <24f222ac545d41a4aaf62b33738973c3@ipfire.org>
In-Reply-To: <0a239f0a-2989-61b3-8eb8-528147a9618d@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2741086963678014511=="
List-Id: <development.lists.ipfire.org>

--===============2741086963678014511==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On 2019-06-16 16:47, Peter M=C3=BCller wrote:
> Hello *,
>=20
> just some minor corrections and additions...
>=20
>> Hello *,
>>=20
>> this is just a quick testing report for upcoming Core Update 133
>> (see:=20
>> https://blog.ipfire.org/post/ipfire-2-23-core-update-133-ready-for-testing=
).
>>=20
>> 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=20
> 92.118.37.0/24 .
> Just in case anyone is interested in. :-/
>> [...]
>>=20
>> /var/log/bootlog however, states current microcodes have been loaded:
>>> [    0.000000] microcode: microcode updated early to revision 0x368,=20
>>> date =3D 2019-04-23
>>> [    0.000000] Linux version 4.14.121-ipfire=20
>>> (root(a)helena.ipfire.org.ipfire.org) (gcc version 7.3.0 (GCC)) #1 SMP=20
>>> Wed May 22 13:45:15 GMT 2019
>>=20
>> (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=20
>> updated Linux kernel, I guess this cannot
> say "GCC 8.x" yet. Sorry.
If you are using the 32bit PAE Kerel this is still compiled with 7.3.0=20
(core131).

Arne

--===============2741086963678014511==--