Description of problem:
While in theory it's not necessary, because both mdns and upnp operate on the local subnet and thus link-layer broadcasting is enough to ensure all hosts get the packets, my switch+router (Alice Gate VoIP AGPF_4.5.0sx, by Pirelli) refuses to switch packets between ethernet and wi-fi unless all hosts declare they partecipate in a multicast group using IGMP.
This means that effectively mDNS and UPnP communication is blocked, and the relevant options in the firewalld GUI have no effect.
I believe the correct solution would be for firewalld to offer a configuration option inside service XML files to mark that multicast is required.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable a multicast service such as mDNS from firewall-config or firewall-cmd
2. Have a switch/router that requires IGMP for local multicast
3. Attempt to send multicast packets to the other host and to get replies (for example with "getent hosts <hostname>.local")
Packets are not delivered, because the hosts are not marked as inside the multicast group. wireshark shows no activity, and neither does iptables -j LOG
Packets are delivered fine, reach the appropriate filter rule, and then are forwarded to the application or rejected as configured.
A successful workaround is
firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p igmp -j ACCEPT
For the record, this problem affects old system-config-firewall on EL 6 too, and in there one can solve this problem by editing /etc/sysconfig/iptables.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.