Score:0

Declare avahi host as 127.0.0.1 result a collision

mx flag
bux

I'm trying to configure an avahi host with IP 127.0.0.1 (I want network computer to see themselves on a specific hostname for testing purposes).

So i added this in /etc/avahi/hosts file :

127.0.0.1 myhosname.local

But, when execute /usr/sbin/avahi-daemon :

ound user 'avahi' (UID 993) and group 'avahi' (GID 992).
Successfully dropped root privileges.
avahi-daemon 0.8 starting up.
Successfully called chroot().
Successfully dropped remaining capabilities.
Loading service file /services/blsi_bt_instrument.service.
Loading new static hostname blsi-0123456789ab.local.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.2.
New relevant interface eth0.IPv4 for mDNS.
Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
New relevant interface lo.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 172.17.0.2 on eth0.IPv4.
Registering new address record for 127.0.0.1 on lo.IPv4.
Server startup complete. Host name is 26e338178fdb.local. Local service cookie is 2934936630.
Static host name myhosname.local: avahi_server_add_address failure: Local name collision
[...]

This error happens : Static host name myhosname.local: avahi_server_add_address failure: Local name collision

I think it is because 127.0.0.1 is already used ? How can I achieve that ? Thanks !

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.