[Bug 1083565] Re: avahi malfunctions on a machine connected to the network via multiple interfaces

[carlostipton1319]

if Avahi malfunctions on a machine connected to the network via multiple
interfaces, it can cause issues with service discovery and hostname
resolution. Here are a few steps you can try to troubleshoot the
problem:

Check network connectivity: Ensure that all network interfaces are properly connected and have a valid IP configuration. Verify that you can access other devices on the network and that there are no general connectivity issues.
https://homecleaningblog.com/preparing-your-home-for-garage-door-repairs/
Restart Avahi service: Restart the Avahi service on the machine. This can help refresh its configuration and resolve any temporary issues. You can do this by running the appropriate command for your operating system, such as "sudo systemctl restart avahi-daemon" on Linux.

Verify Avahi configuration: Review the Avahi configuration file
(/etc/avahi/avahi-daemon.conf) and check for any misconfigurations or
conflicts. Pay attention to settings related to interfaces and network
discovery. Make sure that all relevant interfaces are enabled for Avahi
service.

Check firewall settings: Ensure that the firewall on the machine is not
blocking Avahi traffic. Avahi uses specific ports and protocols for
service discovery. Adjust the firewall rules to allow Avahi traffic to
pass through.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1083565

Title:
  avahi malfunctions on a machine connected to the network via multiple
  interfaces

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a router making up one local NAT network connected to the
  internet. The router allows to connect both wired and wireless. My
  laptops are configured to use both wired and wireless. So I can walk
  around with them and also connect to the quicker wired network if they
  are on the desk.

  Problem is that when the laptops are on my desk and I plug in the
  network cables they stay connected on wireless and so they get
  connected twice, wired and wireless, with two IP addresses, appearing
  as two computers for the router and all other computers in the
  network. Most things still simply work, like accessing the internet
  from the laptops, SSHing to another computer, ... what causes problems
  is Bonjour/mDNS. Avahi broadcasts available services (I have shared
  CUPS printers on the laptops) into the network, using the host name of
  the machine assigned on installation, for example "till-lenovo". As
  the broadcasts go through two interfaces there is a service name
  conflict and it seems that Avahi tries to overcome it by using host
  names like "till-lenovo-1", "till-lenovo-2", ... When the laptop keeps
  running one sees in the "avahi-discover" output on another machine the
  entries from the laptop, but with host names (and so the service
  names) changing from time to time. This leads to a client with a print
  queue pointing to a printer shared by the laptop via the printer's
  Bonjour service name cannot print any more.

  I have done a short test and Avahi stops adding numbers to the
  original host name when turning off wireless on the laptop so that it
  connects only through the wired network.

  One way of fixing (or working around?) the problem would be a change
  in network-manager to automatically turn off wireless if the computer
  is connected to a wired network and switching wireless back on when
  the network cable gets disconnected. This would probably also solve
  problems with other server functionality. --->> http://somapills.net

  Another solution would be a change in Avahi, somehow recognizing that
  the broadcasts through the two interfaces come from the same computer
  and so they can (and should) have the same service names, or
  recognizing that the two interfaces go into the same network and
  therefore broadcast only through one of them, stopping the
  broadcasting through the weaker one (the wireless in our case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1083565/+subscriptions