Description of problem: shoewall6 does not contain the dedicated mDNSbi macro, it is read from the shorewall macro. But the latter contains the IPv4 multicast addresses. While shorewall6 contains the dedicated mDNS macro, which is converted from IPv4 to IPv6. Version-Release number of selected component (if applicable): Any How reproducible: Steps to Reproduce: 1. Install shorewall6 package 2. Use mDNSbi macro somewhere in /etc/shorewall6/rules 3. Try to compile or check the shorewall6 configuration. Actual results: Shorewall6 configuration with mDNSbi macro used cannot be compiled and installed. [root@somehost ~]# shorewall6 check Checking... Processing /etc/shorewall6/params ... Processing /etc/shorewall6/shorewall6.conf... Loading Modules... Checking /etc/shorewall6/zones... Checking /etc/shorewall6/interfaces... Checking /etc/shorewall6/hosts... Determining Hosts in Zones... Locating Action Files... Checking /etc/shorewall6/policy... Adding rules for DHCP Checking TCP Flags filtering... Checking MAC Filtration -- Phase 1... Checking /etc/shorewall6/maclist... Checking /etc/shorewall6/rules... Checking /usr/share/shorewall6/action.AllowICMPs for chain AllowICMPs... ERROR: Unknown Host (224.0.0.251) /usr/share/shorewall/macro.mDNSbi (line 13) from /etc/shorewall6/rules (line 49) [root@somehost ~]# shorewall6 show macro mDNSbi Shorewall 4.6.11.1 Macro mDNSbi at somehost - Вт янв 5 18:19:50 MSK 2016 # # Shorewall version 4 - Bi-directional Multicast DNS Macro. # # /usr/share/shorewall/macro.mDNSbi # # This macro handles multicast DNS traffic # ############################################################################### ?FORMAT 2 ############################################################################### #ACTION SOURCE DEST PROTO DEST SOURCE ORIGIN RATE # PORT(S) PORT(S) DEST LIMIT PARAM - 224.0.0.251 udp 5353 PARAM - - udp 1024: 5353 PARAM - 224.0.0.251 2 PARAM DEST SOURCE:224.0.0.251 udp 5353 PARAM DEST SOURCE udp 1024: 5353 PARAM DEST SOURCE:224.0.0.251 2 [root@somehost ~]# Expected results: shorewall6 configuration can be compiled and installed. Shorewall6 contain mDNSbi macro adopted for IPv6. [root@somehost ~]# shorewall6 show macro mDNSbi Shorewall 4.6.11.1 Macro mDNSbi at somehost - Вт янв 5 18:19:50 MSK 2016 # # Shorewall version 4 - Bi-directional Multicast DNS Macro. # # /usr/share/shorewall6/macro.mDNSbi # # This macro handles multicast DNS traffic # ############################################################################### ?FORMAT 2 ############################################################################### #ACTION SOURCE DEST PROTO DEST SOURCE ORIGIN RATE # PORT(S) PORT(S) DEST LIMIT PARAM - <ff02::fb> udp 5353 PARAM - - udp 1024: 5353 PARAM - <ff02::fb> 2 PARAM DEST SOURCE:<ff02::fb> udp 5353 PARAM DEST SOURCE udp 1024: 5353 PARAM DEST SOURCE:<ff02::fb> 2 [root@somehost ~]# Additional info: [root@somehost ~]# shorewall6 show macro mDNS Shorewall 4.6.11.1 Macro mDNS at lightstar.home - Вт янв 5 18:22:59 MSK 2016 # # Shorewall version 4 - Multicast DNS Macro # # /usr/share/shorewall6/macro.mDNS # # This macro handles multicast DNS traffic. # ############################################################################### ?FORMAT 2 ############################################################################### #ACTION SOURCE DEST PROTO DEST SOURCE # PORT(S) PORT(S) PARAM - <ff02::fb> udp 5353 PARAM - - udp 32768: 5353 PARAM - <ff02::fb> 2 PARAM DEST SOURCE:<ff02::fb> udp 5353 PARAM DEST SOURCE:<ff02::fb> 2 [root@somehost ~]#
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi, could you please check if your issue is present in 5.0.x as well? I have built packages here: https://copr.fedorainfracloud.org/coprs/mbaldessari/shorewall/ thanks, Michele
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.