Strange IPv6 behavior with avahi-daemon (on TrueNAS)

[computeralex92]

Hello,

after upgrading to 24.7 something strange is happening with my TrueNAS environment:

Code: [Select]

Jul 18 19:30:48 erebos avahi-daemon[4206]: Registering new address record for fd33:bcd:30fc:9e4b:be24:11ff:feef:9582 on enp6s18.*.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Registering new address record for fe80::be24:11ff:feef:9582 on enp6s18.*.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Withdrawing address record for 2003:ef:bf13:a200:be24:11ff:feef:9582 on enp6s18.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Withdrawing address record for fe80::be24:11ff:feef:9582 on enp6s18.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Withdrawing address record for 10.0.0.4 on enp6s18.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Host name conflict, retrying with erebos-2
Jul 18 19:30:48 erebos avahi-daemon[4206]: Registering new address record for fd33:bcd:30fc:9e4b:be24:11ff:feef:9582 on enp6s18.*.
Jul 18 19:30:48 erebos avahi-daemon[4206]: Registering new address record for 10.0.0.4 on enp6s18.IPv4.
Jul 18 19:30:49 erebos avahi-daemon[4206]: Server startup complete. Host name is erebos-2.local. Local service cookie is 1161687643.
Jul 18 19:30:50 erebos avahi-daemon[4206]: Service "erebos-2" (/services/SMB.service) successfully established.
Jul 18 19:30:50 erebos avahi-daemon[4206]: Service "erebos-2" (/services/HTTP.service) successfully established.
Jul 18 19:30:50 erebos avahi-daemon[4206]: Service "erebos-2" (/services/DEV_INFO.service) successfully established.
Jul 18 19:30:50 erebos avahi-daemon[4206]: Service "erebos-2" (/services/ADISK.service) successfully established.
Avahi is the implementation of the Apple Bonjour protocol or MDNS stuff; widely used by systems within the BSD & Linux ecosystem to allow e.g. SMB shares to be discovered by Apple devices.
This messages appeared when I restarted the opnsense the last time; a reboot of the TrueNAS is fixing the issue for the Mac devices because the correct name is online again.

I checked my logs of the TrueNAS system and it started to produce this messages at nearly every restart of the opnsense after when I upgraded to 24.7; that's why I'm asking here and not in the TrueNAS community...

To my setup:
My TrueNAS get a IPv4 address via a static lease from ISC DHCP, IPv6 is configured by "Track interface" on the LAN side and DHCPv6 on the WAN side (PPPoE connection to Telekom Germany).

From my perspective there is something strange going on in 24.7 regarding IPv6, as I also noticed after a reboot that the IPv6 address on the WAN side is active for a second before disappearing for XYZ minutes.
Also the opnsense is not able to get the gateway for IPv6; but the clients get a IPv6 address and are able to use it.

If you need some logs from the opnsense, just say it and I will provide it.

Thanks a lot,
Alex

[9axqe]

Maybe unrelated but since 24.7 I have HomeKit not working properly and Home Assistant unable to resolve .local URLs, both of which rely on mDNS.

I'm still investigating, but something is broken in regards to mDNS (it could actually by Home Assistant) and the timing fits the upgrade to 24.7.