Hannu, The only things a fresh avahi-daemon installation puts into the config (that is, not commented) are:
[server] use-ipv4=yes use-ipv6=yes ratelimit-interval-usec=1000000 ratelimit-burst=1000 [wide-area] enable-wide-area=yes [publish] [reflector] [rlimits] rlimit-core=0 rlimit-data=4194304 rlimit-fsize=0 rlimit-nofile=768 rlimit-stack=4194304 rlimit-nproc=3 If there was a domain name default, it would be "domain-name=local" (but commented out), without dot. But it will be derived from your hostname anyway. So maybe try commenting (disabling) any domain setup. If any, it should be something like 'gone.local' if gone is your machine. Check the /etc/avahi/hosts file too. My version has commented examples, only: # Examples: # 192.168.0.1 router.local # 2001::81:1 test.local so i guess it should work w/o any manual explicit configuration too. Also check if you got libnss-mdns installed, which is recommended by avahi. I am sorry i can not easily check how it works w/o manual configuration. I just can't remember any installation asked me anything about it so i guess the defaults should work out of the box. I deinstalled any avahi services on all machines in this small intranet because we don't seem to have any need for it, and we didn't miss anything afterwards. For example, i don't understand why laptops need a avahi-daemon, or rather, why avahi-discover should be depending on the daemon. Do you really want to publish your laptop 'files to access' in a mixed environment ? We have one printer and it seems network access via IPP works fine even without avahi. I guess a roaming laptop or smartphone could benefit in some trusted environment though. But seriously, in which business or university environment do you send off a printing job from your laptop without first being granted explicit access to the printer ? I admit i am oldfashioned and do not understand any modern usages of multicast dns. Well. in your situation, i would deinstall (with complete 'purge') anything with 'avahi' in its name, except it breaks essential other packages (for example, cups and gvfs need some avahi libs), especially the daemon. Then, i'd check if something i need does not work anymore. If so, reinstall avahi-discover. With luck, the error will be gone with a new package default config. It should be noted that such a task needs some experience (or boldness) with 'apt-get' or a good package manager. It's rather easy, and safe, if you know how to use 'aptitude'. If you configured things manually, and want to preserve the config, don't use 'purge'. Keep in mind that even if you deinstalled half your system, it can be reinstalled in a few moments, if only you keep track of what was removed (for example, the /var/log/aptitude). gl mi -- To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130625200440.0d571...@mirrors.kernel.org
