mDNS Host name conflict not occurring

Technical Support
, , , ,
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

Thank you for reaching out with your question about mDNS hostname conflict resolution on your Verdin iMX8MP SOM with Torizon Core 5. It seems that the avahi-daemon is not resolving hostname conflicts as expected when IPv6 is enabled, which is indeed an unusual behavior.

Here are some steps you can take to troubleshoot and potentially resolve this issue without disabling IPv6:

  1. Avahi Configuration: Check the Avahi configuration file located at /etc/avahi/avahi-daemon.conf. Ensure that the use-ipv6 setting is enabled by setting it to yes. This ensures that Avahi is configured to handle both IPv4 and IPv6.

  2. Network Interface Setup: Verify that your network interfaces are properly configured to support both IPv4 and IPv6. Misconfigurations at the network level can sometimes lead to unexpected behavior.

  3. Avahi Version: Make sure you are using the latest version of Avahi available for your Torizon Core version. Updates or patches might address specific issues related to IPv6.

  4. Log Analysis: Examine the Avahi logs for any error messages or warnings that could provide more insight into the issue. You can view these logs using the command journalctl -u avahi-daemon.

  5. Alternative Network Testing: If possible, test your setup on a different network environment to rule out any network-specific issues that might be affecting mDNS behavior.

The interaction between mDNS and IPv6 can sometimes lead to unexpected results due to network configurations or specific conditions. By following these steps, you should be able to diagnose and potentially resolve the problem.

I hope this helps, and please feel free to reach out if you have any further questions.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Plugging Ethernet cable crashes M7.