| Summary: | shorewall6 was not working anymore, one file unpopulated | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jybz <j.biernacki+mga> |
| Component: | RPM Packages | Assignee: | José Jorge <lists.jjorge> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | lists.jjorge, luigiwalser, mageia, marja11, smelror |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | shorewall | CVE: | |
| Status comment: | |||
|
Description
Jybz
2019-02-08 16:17:09 CET
Where is the shorewall6 or shorewall-ipv6 package ? https://svnweb.mageia.org/packages/cauldron/?dir_pagestart=14000 (In reply to J-B B from comment #1) > Where is the shorewall6 or shorewall-ipv6 package ? > https://svnweb.mageia.org/packages/cauldron/?dir_pagestart=14000 /usr/sbin/shorewall6 comes from the shorewall-ipv6 package, which comes from the shorewall SRPM. There is no registered maintainer, so assigning to all packagers collectively and CC'ing some committers. Assignee:
bugsquad =>
pkg-bugs As for bug 22778, I'll try to enable shorewall 6 to mcc. Patches welcome of course. CC:
(none) =>
lists.jjorge (In reply to José Jorge from comment #3) > As for bug 22778, I'll try to enable shorewall 6 to mcc. Patches welcome of > course. In fact, looks like this code is just too old. The better solution is to deprecate firewall config in MCC, and redirect users to firewall-config which is maintained. I have tried to use it, and managed very easily to get both Ipv4 and Ipv6 firewall tuned. (In reply to José Jorge from comment #4) > I have tried to use it, and managed very easily to get both Ipv4 and Ipv6 > firewall tuned. Using it more, there were too much problems with firewalld. So I went the way of enabling shorewall6 in mcc. See bug 22778 for details. Resolution:
(none) =>
FIXED |