Bug 44188 - Firewall blocks all incoming connections after upgrade 4.1->4.2
Firewall blocks all incoming connections after upgrade 4.1->4.2
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Firewall (univention-firewall)
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.2
Assigned To: Daniel Tröder
Stefan Gohmann
: interim-4
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-31 11:49 CEST by Daniel Tröder
Modified: 2017-04-04 18:28 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.143
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2017-03-31 11:49:28 CEST
Sometimes (not easily reproducible) after an upgrade UCS 4.1->4.2, all new incoming connections - incl SSH and HTTP(S) ! - are blocked. A restart of the univention-firewall fixes that then (as does a server reboot).

Add "systemctl restart univention-firewall.service" to postup.sh to make sure the system is accessible after an upgrade.
Comment 1 Daniel Tröder univentionstaff 2017-03-31 12:08:33 CEST
r78542: recreate and reload packetfilter rules to make sure the system is accessible

Package: univention-updater
Version: 12.0.6-4A~4.2.0.201703311207
Branch: ucs_4.2-0
Scope:
Comment 2 Stefan Gohmann univentionstaff 2017-04-01 18:02:57 CEST
OK, works.
Comment 3 Stefan Gohmann univentionstaff 2017-04-04 18:28:24 CEST
UCS 4.2 has been released:
 https://docs.software-univention.de/release-notes-4.2-0-en.html
 https://docs.software-univention.de/release-notes-4.2-0-de.html

If this error occurs again, please use "Clone This Bug".