Univention Bugzilla – Bug 30908
univention-firewall cannot be restarted in the UMC system service module
Last modified: 2020-06-22 15:40:30 CEST
univention-firewall doesn't have a service definition for the UMC system services module.
Unfortunately the fix is to big for an errata. The init script for univention-firewall uses the UCRV security/packetfilter/disabled to check if it should be started or not. The system services module however does set this value to 'yes' if a service should be started. The inverse logic needed for this UCRV is not possible in the system services module. A fix should change the UCRV to security/packetfilter/autostart. Additional logic is probably needed to determine if 'the iptables service is running'
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2. As such, this bug is moved to the new target milestone.
(In reply to Erik Damrose from comment #1) > Additional logic is probably needed to determine if 'the iptables service is running' -> Bug 30599
Moved target milestone, as bug 30599 is not fixed yet
Maybe easier with UCS 4.2 now?
Use case still relevant. Searched for it together with a school customer lately.
There is a Customer ID set so I set the flag "Enterprise Customer affected".