Spurious name conflicts

Hi, hope this is the right place for reporting issues with avahi-daemon as the readme on my system points to the bugtracker on freedesktop.org that does not list avahi as a bug report target. I am experiencing spurious name conflicts on various systems, all of which have a common trait in having two interfaces, one on the local lan, having a static IP address and the other getting a dhcp address from somewhere (typically an ADSL router). What happens is the following. Suppose that the host is called "foo". Initially, it is correctly advertised as foo.local. After some time the name conflict occurs and the host starts being advertised as foo-2.local, foo-3.local, etc., even if it is certainly the sole host named foo on the network. In practice there is a spurious name conflict with the host itself, probably due to some race in avahi. The unfortunate result is that no other system cannot find "foo" no more on the network, since they look for foo.local. I see the issue on a couple of debian jessie systems (avahi version 0.6.31); on a raspbian jessie system (same); and on an openwrt chaos calmer system (avahi version 0.6.31 again). I see a lot of reports for this same issue (or possibly something similar) on many distro bugtrackers, applications bugtrackers and question sites: - https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/831022 - https://serverfault.com/questions/714917/host-name-conflict-with-avahi-daemon-on-ubuntu-14-04-lts - https://github.com/foosel/netconnect

Posted by callegar on Apr 26, 2017, 3:54 PM

Tags

• github (Network)

Related issues

• [UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
• Server requests and latency increased after upgrading from Next.js 15 to 16
• Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
• Can't download videos from YouTube on cobalt.tools
• `google_service_networking_connection` produce an error when trying to destroy the resource
• WebGPU-based renderer for the editor