From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4fnJfQ4ywmz32jC for ; Fri, 03 Apr 2026 12:57:34 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4fnJfF0HX4z2xMP for ; Fri, 03 Apr 2026 12:57:25 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4fnJfC5QBVz3wP; Fri, 03 Apr 2026 12:57:23 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1775221044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0SGUJ/vFGDBmYfK2alsjwQwGvViddyKgbOVGxgAGmB4=; b=FaNuxgZ3NY+1yATAK624+mLl3L72tHZxTMEVDSmQSz5bYqXR9tuPSJVM7aNPNE0U2zB1jC hdsi5aDAHPt209Bw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1775221044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0SGUJ/vFGDBmYfK2alsjwQwGvViddyKgbOVGxgAGmB4=; b=EDaDG0y6RItJ5yTmPLbkw2yayQ4ECY+nkMcgP/d9GlWUnxOpiJyzmeIVNmTKnj+ovorK9P I/if7sv6lJKwajHjwus/dEpc9hYbPsMKWDQo4LDvvDsROrlFYLIh1MvsdQ6qWFgvSUOSCQ s+h7T2nT27+nWCJi1JeywK5lFqE85nCieXwMdQiEKU88WXx5k1ttx6fic6Y46nDwJdkuPb V0P04aXuk/7hPzPUH+AMV2vPSt31wTYDTX1vAFd9NXG5u8IinydhNenR4QRtEguxXAb4Rv KnLB1jDK/yK2TLgiYsNwTssB6EnZQ6iTtC7AywnrJroFqjCCS9p1U7YE3GWcyw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: CU201 Testing - No firewall logs displayed although they are in the messages file From: Michael Tremer In-Reply-To: Date: Fri, 3 Apr 2026 13:57:22 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <2B659A71-89C8-4BBA-BADC-1AE6A62E5CD4@ipfire.org> References: To: Adolf Belka Hello Adolf, Thanks for raising this. This is probably a regression that would block = the release. However, it is not a difficult problem to solve. What introduced the change? My first guess was an update of klogd, but = that has not been updated since May 2025. Looking through the changes in the update, the only explanation is glibc = which implements the syslog() function. Since we cannot really do much = about that, I have decided to upgrade to sysklogd 2.x where syslogd and = klogd have been combined into one. It is a fresh rewrite and entirely = compatible with our configuration - so basically a drop-in replacement. = https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D3b32430a4d16= d9d5f2334b3acbc94f1f88fad7c8 With this, the messages appear as =E2=80=9Ckernel:=E2=80=9D again. Please let me know if this solves the problem for you, too. All the best, -Michael > On 1 Apr 2026, at 17:06, Adolf Belka wrote: >=20 > Hi All, >=20 > There was a forum post about not finding any output in the WUI = Firewall Logs with CU201 Testing. >=20 > I did some testing and found that the logs were displayed in the WUI = if I was working with an IPFire that had been updated from CU200 to = CU201 Testing but when I did a fresh install of CU201 Testing then the = logs were not displayed. >=20 > Doing a fresh install of CU200 showed the logs as normal in the WUI. >=20 > I checked the /var/log/messages file with the fresh install of CU201 = Testing and found that there were firewall logging messages in there but = the problem is that the starting section of the log lines with a fresh = install of CU201 Testing is >=20 > Apr 1 15:54:23 ipfire klogd: DROP_INPUT IN=3Dred0 >=20 > while for CU200 or a CU201 Testing updated from CU200 it is >=20 > Apr 1 16:13:59 ipfire kernel: DROP_INPUT IN=3Dred0 >=20 > So the process name has changed from kernel: to klogd: but only for = the fresh install of CU201 Testing. >=20 > I have been unable to identify if this was intended to be changed or = not and if intended why it is not in the upgraded version. >=20 > So this is to ask if anyone knows why this would be occurring and what = should be the expected status? >=20 > Regards, >=20 > Adolf. >=20 >=20