Bug 16311

Description of problem: I have an HP printer with no interfaces other than wifi. This fails to be auto-discovered by either system-config-printer or by hp-setup -- I have to supply the printer's actual IP address in either case. Suspecting that the failure of auto-discovery was somehow caused by the firewall, I performed a series of experiments and found the following strange behaviour:

For network auto-dicsovery to work, "network services autodiscovery" must be enabled in the firewall. This may not seem surprising, until I add that this is the case whether or not the firewall is disabled! To put it otherwise, if you do not wish firewall enabled, you must still enable "network services autodiscovery" in the firewall before disabling the firewall.

Network auto-discovery will also work if the firewall is enabled, but not applied to Ethernet interface(s). This is true even if having enabled the firewall (without "network services autodiscovery") you are still looking at the window asking you which interface(s) it should be applied to. Until you click OK to confirm applicability to your Ethernet interface(s), auto-discovery will work. Once you click OK, with Ethernet interface(s) checked, it will stop working. If you uncheck Ethernet interface(s) before clicking OK, auto-discovery will continue working.

This does not look like intended behaviour. :-)


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Set the firewall to any of the above described states
2. Run /usr/bin/hp-probe
3.


Reproducible: 

Steps to Reproduce: