public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: CU201 Testing - No firewall logs displayed although they are in the messages file
Date: Wed, 1 Apr 2026 18:06:56 +0200	[thread overview]
Message-ID: <ad1a7ddd-5c49-48b9-a06e-2dc8e1728b52@ipfire.org> (raw)

Hi All,

There was a forum post about not finding any output in the WUI Firewall Logs with CU201 Testing.

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.

Doing a fresh install of CU200 showed the logs as normal in the WUI.

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

Apr  1 15:54:23 ipfire klogd: DROP_INPUT IN=red0

while for CU200 or a CU201 Testing updated from CU200 it is

Apr  1 16:13:59 ipfire kernel: DROP_INPUT IN=red0

So the process name has changed from kernel: to klogd: but only for the fresh install of CU201 Testing.

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.

So this is to ask if anyone knows why this would be occurring and what should be the expected status?

Regards,

Adolf.



                 reply	other threads:[~2026-04-01 16:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ad1a7ddd-5c49-48b9-a06e-2dc8e1728b52@ipfire.org \
    --to=adolf.belka@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