http://bugzilla.suse.com/show_bug.cgi?id=959707
http://bugzilla.suse.com/show_bug.cgi?id=959707#c4
--- Comment #4 from Matthias Gerstner ---
New SuSEfirewall2 maintainer here. I'm working on the backlog bugs. Sorry for
the delay.
SuSEfirewall2 by default drops all input packets on ports that have not been
explicitly allowed and that are not part of an existing connection, initiated
by the host. It seems the multicast packets used for mdns are not covered by
the connection tracking and are thus dropped.
You can work around this limitation by explicitly allowing mdns packets in. To
do this add "mdns" to the configuration setting FW_SERVICES_{net}_UDP in
/etc/sysconfig/SuSEfirewall2. You need to replace {net} with EXT/INT/DMZ as
appropriate for your use case.
We might also think about allowing mdns input by default for the internal
network. I think this might be the most common use case, to discover devices
like printers.
--
You are receiving this mail because:
You are on the CC list for the bug.