Red Hat Bugzilla – Bug 847840
Network printer is not discovered when firewalld is running
Last modified: 2013-08-01 08:54:04 EDT
Description of problem:
In my firewalld configuration the following services are enabled:
But when firealld is running, no printer is discovered on the local network. If added the printer is working, even if firewalld is runnning. So the problem is with discovery only.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start firewalld
2. search for printers in system settings
No printers found
printers are found, if the needed services (as told by system settings) are enabled.
Maybe there's another service that needs to be enabled in my config?
(In reply to comment #0)
> In my firewalld configuration the following services are enabled:
> Maybe there's another service that needs to be enabled in my config?
These should be sufficient for the discovery to work.
What's the output of 'firewall-cmd --list=all' ?
> But when firealld is running, no printer is discovered on the local network.
So it works when firewalld is stopped ?
Yes, when firewalld is stopped, the printer discovery works.
What kind of printer is this? Is it using mdns?
Yes, I tried mdns and slp, both did not work. It is an HP OfficeJet 4500.
Please open port 5353/udp instead of using mdns. It could be that the printer is using unicast instead of multicast for mdns.
The service file /usr/lib/firewalld/services/mdns.xml opens port 5353 for udp. Is something wrong with this?
The service opens the port for the multicast address only. If your printer is using unicast instead of multicast, then it does not match.
So what do I put in my own service file under /etc then, do enable the unicast port?
Copy the file from /usr/lib/firewalld/mdns.xml and remove the destination line.
That worked, the printer is now found by system settings. But when searching with hp-setup and method mdns, nothing is found.
That might be a result of the unicast use.. it should use multicast.
Is that working without a firewall?
Yes without firewalld it is working.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.