Having reviewed the logs and comments, the core problem seems to be avahi-daemon's inability to reliably manage multiple network interfaces.
As a potential path forward, I'd like to propose a two-part solution: Add a Configuration Option: Introduce a new parameter in avahi- daemon.conf, such as allow-interfaces=, where a user can explicitly list which network interfaces the daemon should monitor (e.g., allow- interfaces=eth0,wlan0). This would provide a robust workaround for systems where automatic detection is failing. Enhance Startup Logging: Increase the verbosity of the daemon's logs during startup to clearly report which interfaces it detects and whether it successfully binds to each one. This would make diagnosing this and similar issues much easier in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083565 Title: avahi malfunctions on a machine connected to the network via multiple interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1083565/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
