Bug 21417 - shorewall6 blocks all ports when stopped
Summary: shorewall6 blocks all ports when stopped
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 22778
Blocks: 23806
  Show dependency treegraph
 
Reported: 2017-07-31 01:27 CEST by james Whitby
Modified: 2019-04-11 09:30 CEST (History)
3 users (show)

See Also:
Source RPM: shorewall, drakx-net
CVE:
Status comment:


Attachments

Description james Whitby 2017-07-31 01:27:58 CEST
Install shorewall6.

In mcc set firewall to none.

All ipv6 ports are blocked.

Only fix I found was to enable shorewall6 with accept for all.
Comment 1 David Walser 2017-07-31 02:08:42 CEST
drakfirewall configures shorewall/shorewall6.

Source RPM: shorewall-ipv6 => shorewall, drakx-net
Assignee: bugsquad => mageiatools
Summary: Blocks all ports when stopped => shorewall6 blocks all ports when stopped

Comment 2 james Whitby 2017-07-31 03:06:58 CEST
Ok. 
Drakfirewall when set to "Everything (no firewall)"
blocks all ipv6 ports.
Comment 3 Jybz 2017-11-25 18:27:35 CET
Hello guys,

Please, let me say that I need to open the ipv6 ports, and it is true that the CCM don't manage the ipv6shorewall.

I will manage it with another way, but it is really a pity. Can I try to change the drakshorewall ?

Thank you

CC: (none) => j.biernacki

papoteur 2018-11-06 22:40:11 CET

Blocks: (none) => 23806

Jybz 2018-11-07 19:31:12 CET

Depends on: (none) => 22778

Comment 4 José Jorge 2019-04-10 11:01:43 CEST
In MGA7, we have now drakfirewall6 to manage separately IPv6 shorewall.

Resolution: (none) => FIXED
CC: (none) => lists.jjorge
Status: NEW => RESOLVED

Comment 5 papoteur 2019-04-10 16:35:19 CEST
Can this be ported to Mageia 6?
Because the problem remains.

CC: (none) => yves.brungard_mageia

Comment 6 José Jorge 2019-04-10 19:01:14 CEST
(In reply to papoteur from comment #5)
> Can this be ported to Mageia 6?
> Because the problem remains.

Yes, as this uses nothing from MGA7. But as MGA7 is very near from release, I don't feel it is worth.
Comment 7 papoteur 2019-04-11 09:30:09 CEST
Thanks José,

I would say that it worth to be ported in Mageia 6, even if I don't know if it is difficult. The bug is hidden and not evident to locate for a common user. And I presume that Mageia 6 will be supported still for 6 monthes from now. And we know that some users still use Mageia 5 ...

Papoteur

Note You need to log in before you can comment on or make changes to this bug.