Bug 43568 – Define iptables rules via policies

Bug 43568 - Define iptables rules via policies


Summary:	Define iptables rules via policies

Status:	RESOLVED WONTFIX

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

Importance:	P5 normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-17 11:26 CET by Sönke Schwardt-Krummrich
Modified:	2019-01-03 07:19 CET (History)
CC List:	3 users (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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
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 Sönke Schwardt-Krummrich

2017-02-17 11:26:48 CET

A customer wants to define custom iptables rules via policies on several UCS machines. The current ruleset configurable via UCR variables is not sufficient since it is not possible to e.g. filter by source IP addresses.

First idea:
A new policy UDM module that stores iptables rules in LDAP that are written via listener module to e.g. /etc/security/packetfilter.d/40_policy_rules.sh

Comment 1 Sönke Schwardt-Krummrich

2017-02-17 11:28:48 CET

This solution would unburden the admin from copying custom 50_local.sh files to all affected machines.

Comment 2 Florian Best

2017-06-28 14:52:54 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 3 Stefan Gohmann

2019-01-03 07:19:23 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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