Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Avahi does not query domain it's on hence users are both unaware and unable to take advantage of dns-sd Wide-area setups. It should default on checking both local and the search domain which is defined in network settings. ( which is either manually set or passed on via dhcp ) Probably needs to query the domain per service. Noticed this when setting up dns-sd wide-area printing setup ( single cups back end for the uni ) avahai scanned local and found 2 printers and feed it to s-c-p/cups but not the ones defined in the dns-sd wide area setup. avahi-browse _ipp._tcp -t -r -d <domain> does fetch the info from the dns server.. It's perfectly logical to default searching on both local and the domain avahi resides on however if user needs to browse any domain he's not on he should need to explicitly tell avahi to do so either through the application that uses avahi or through some configuration in avahi itself.. Version-Release number of selected component (if applicable): 06.25-5 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I tested dns-sd wide area setup with tiger, leopard and windows xp installed with Bonjour software from Apple website and they all worked out of the box. the key is that search domain ( or dns suffix as they twist it in the world of M$ ) contains the domain entry.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
We don't merge browsing domains, since we believe that is a job for the clients. The clients should be patched to browse for all configured browsing domains. Which client is this?
Dont the client ask avahi which domain to browse? Avahi should use the domain that is defined in the network settings by default instead of "browse-domains=0pointer.de, zeroconf.org" for some odd reason your domain and zeroconf... Users should not need to define browser domain they will get it either via dhcp or they will manually set it when they configure their network connection. The only reason for them to set the domain is if they are going to browse domains other then the one they are currently on.. If it's not avahi responsibility to keep track of this then all of clients need to be patch to try first the domain that's defined in the network settings then "user defined" one..
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.
Lennart Ping
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping