Bug 38435 – univention-firewall should provide a logfile

Bug 38435 - univention-firewall should provide a logfile


Summary:	univention-firewall should provide a logfile

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Firewall (univention-firewall)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-05-04 21:36 CEST by Michael Grandjean
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback, Troubleshooting
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Grandjean

2015-05-04 21:36:12 CEST

Feedback during customer workshop:

AFAIS we have no easy possibility to enable logging of univention-firewall / iptables. This should be available via UCR. I think a good default might be to log all dropped / rejected packets, just to make troubleshooting easier.
Additionally, a rsyslog rule to separate iptables logs from syslog would be great.

Comment 1 Daniel Tröder

2015-05-05 09:36:48 CEST

Maybe use the chance to introduce ULOG?

It can be configured to log by default to a syslog-style logfile. The configuration could later easily be expanded to enable logging to MySQL if the user wishes it.

Comment 2 Ingo Steuwer

2020-07-03 20:54:54 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.