From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Core Update 133 (testing) report Date: Sun, 16 Jun 2019 14:47:00 +0000 Message-ID: <0a239f0a-2989-61b3-8eb8-528147a9618d@ipfire.org> In-Reply-To: <2a5ccb4c-c62d-a4ec-357e-d220f5109356@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5317370791240968709==" List-Id: --===============5317370791240968709== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, just some minor corrections and additions... > Hello *, >=20 > 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-te= sting). >=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 92.118.37.0/2= 4 . 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, date = =3D 2019-04-23 >> [ 0.000000] Linux version 4.14.121-ipfire (root(a)helena.ipfire.org.ipf= ire.org) (gcc version 7.3.0 (GCC)) #1 SMP 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 updated= Linux kernel, I guess this cannot say "GCC 8.x" yet. Sorry. > [...] Thanks, and best regards, Peter M=C3=BCller --=20 The road to Hades is easy to travel. -- Bion of Borysthenes --===============5317370791240968709==--