Bug 39773 - External IP routing does not work for docker guests if univention-firewall is stopped
External IP routing does not work for docker guests if univention-firewall is...
Status: CLOSED DUPLICATE of bug 39686
Product: UCS
Classification: Unclassified
Component: Docker
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-0-errata
Assigned To: Bugzilla Mailingliste
Stefan Gohmann
: interim-2
Depends on: 38307
Blocks: 39686
  Show dependency treegraph
 
Reported: 2015-11-04 09:38 CET by Daniel Tröder
Modified: 2015-11-18 07:12 CET (History)
5 users (show)

See Also:
What kind of report is it?: ---
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):
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 2015-11-04 09:38:38 CET
+++ This bug was initially created as a clone of Bug #38307 +++

If "univention-firewall" is stopped, all containers will loose connectivity until "docker" is restarted or the system is rebooted (if univention-firewall is deactivated permanently via security/packetfilter/disabled=yes).

---

The connectivity of the Docker containers should continue after shutting down the firewall of the host.

Simplest solution (with short connectivity outage) would be to call /etc/security/packetfilter.d/20_docker.sh at the end of stop() in the init script. More complex would be to remove rules in stop() very carefully.
Comment 1 Daniel Tröder univentionstaff 2015-11-04 09:40:44 CET
oops

*** This bug has been marked as a duplicate of bug 39686 ***
Comment 2 Stefan Gohmann univentionstaff 2015-11-18 07:12:04 CET
OK, duplicate.
Comment 3 Stefan Gohmann univentionstaff 2015-11-18 07:12:19 CET
Nothing to release.