Dear Maintainer,


    * What led up to the situation?
    * What exactly did you do (or not do) that was effective (or
      ineffective)?
      The installation of the package

    * What was the outcome of this action?
      I could access the server via SMB from my windows box.
      I noticed that I could ping the server and that there are new
iptables entries

    * What outcome did you expect instead?
      That I get asked if I would like that default rules get appiled
which prevent some kind of services to function.

Dear Maintainer,

I wanted to provide an additional aspect on this ticket.

I recently reinstalled Debian Testing with KDE. Due to KDE firewalld was
installed too.

Unfortunately, firewalld blocks mDNS ports by default. Due to this, my
system was unable to find a network printer. It took me quite long to
figure that out. The StackOverflow question I opened for it is [1], but
I think the information here are sufficient already.

On Kubuntu (24.04 live image and some not to recent installation) mDNS
is not blocked and the network printer was detected easily.

I would appreciate if you could reconsider this rule.

Best

Am 03.09.24 um 10:29 schrieb Max Görner:

The default "home" firewalld zone should allow mdns.
Which zone did you have enabled in firewalld when you tried to discover
the printer?

According to my firewalld.conf I have DefaultZone=public and in my
/usr/lib/systemd/system/firewalld.service no zone seems to be set.

However, the point is that I did not configure anything. Directly after
installing Debian Testing + KDE firewalld was installed and configured. I
wasn't aware of it at all.

So, if there is a zone allowing mDNS already, could that become the
default zone?