Bug 52129 - adress parameter in packetfilter rules only used as destination address
Summary: adress parameter in packetfilter rules only used as destination address
Status: RESOLVED DUPLICATE of bug 25632
Alias: None
Product: UCS
Classification: Unclassified
Component: Firewall (univention-firewall)
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-23 14:05 CEST by Christian Völker
Modified: 2020-09-23 14:30 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2020092221000562
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2020-09-23 14:05:14 CEST
According to the documentation (https://docs.software-univention.de/developer-reference-4.4.html#misc:nacl) we can set an address parameter:

ucr set security/packetfilter/tcp/4545/192.168.90.99=ACCEPT
Create security/packetfilter/tcp/4545/192.168.90.99
File: /etc/security/packetfilter.d/10_univention-firewall_start.sh
File: /etc/security/packetfilter.d/80_univention-firewall_policy.sh


This address appears to be used always as destination address with the parameter "-d":

root@lenaedu:/etc/security/packetfilter.d# tail -2  10_univention-firewall_start.sh 
iptables --wait -A INPUT -p "tcp" -d 192.168.90.99 --dport 4545 -j ACCEPT


This makes partially sense in case the UCS server has multiple IPs and the rules should take place only on specific IP address.

But what can not be done here is to limit access FROM a specific host or network.

This should be possible, too.

At least the documentation should state it clear about the destination only address.
Comment 1 Philipp Hahn univentionstaff 2020-09-23 14:30:20 CEST

*** This bug has been marked as a duplicate of bug 25632 ***