nickp85 Posted April 30 Share Posted April 30 Seeing these log lines constantly in the system log. Any idea what they are from? Apr 30 00:48:43 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. Apr 30 00:49:17 nicknas2 avahi-daemon[21853]: Registering new address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0.*. Apr 30 00:49:29 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. Apr 30 00:49:50 nicknas2 avahi-daemon[21853]: Registering new address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0.*. Apr 30 00:49:58 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. Apr 30 00:50:17 nicknas2 avahi-daemon[21853]: Registering new address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0.*. Apr 30 00:50:25 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. Apr 30 00:51:04 nicknas2 avahi-daemon[21853]: Registering new address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0.*. Apr 30 00:51:09 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. Apr 30 00:51:44 nicknas2 avahi-daemon[21853]: Registering new address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0.*. Apr 30 00:51:49 nicknas2 avahi-daemon[21853]: Withdrawing address record for fd4b:e720:c542:145:9e53:22ff:fe8a:5ccb on br0. nicknas2-diagnostics-20240430-0055.zip Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 It seems to be a conflict with the Homebridge docker container which also uses avahi. If I stop that Docker the problem stops. Any way to fix it? Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 Well, I didn't fix the issue but found something online for how to disable Avahi in Homebridge. I'm not using it anyway. https://github.com/homebridge/docker-homebridge?tab=readme-ov-file#parameters The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. --net=host - Shares host networking with container, required -v /homebridge - The Homebridge config and plugin location, required Optional Settings: -e TZ - for timezone information e.g. -e TZ=Australia/Canberra -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 nevermind... didn't stop the log lines in the Unraid log... help! Quote Link to comment
bmartino1 Posted April 30 Share Posted April 30 (edited) looks like your getting 2 ipv6 address to br0 how many physical eth adapters does your system have and are in the br0 interface? Try to clear the ipv6 and restart the ms avia service: ip -6 addr flush dev br0 && ifconfig br0 inet6 0 restart service: /etc/rc.d/rc.avahidaemon restart Per your docker variable: -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container you may want that to be 0 as it is causing a networking conflict and ipv6 ip change loop Edited April 30 by bmartino1 Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 (edited) 7 minutes ago, bmartino1 said: looks like your getting 2 ipv6 address to br0 how many physical eth adapters does your system have and are in the br0 interface? Try to clear the ipv6 and restart the ms avia service: ip -6 addr flush dev br0 && ifconfig br0 inet6 0 restart service: /etc/rc.d/rc.avahidaemon restart Per your docker variable: -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container you may want that to be 0 as it is causing a networking conflict and ipv6 ip change loop I did try setting that variable to 0 but it didn't stop the conflict. The system has 2 physical NIC, only one is assigned to br0 and the other is a passthrough to a VM. I also use pi-hole in docker so have a second ipv4/ipv6 IP for it to exist on my network. Perhaps that is where the double IP is coming from? I tried to run the first command you provide but I think it errored? ip -6 addr flush dev br0 && ifconfig br0 inet6 0 getaddrinfo: 0: -9 0: Resolver Error 0 (no error) ifconfig: `--help' gives usage information. I restarted avahi anyway and see the following log lines Apr 30 14:38:50 nicknas2 avahi-daemon[16278]: Got SIGTERM, quitting. Apr 30 14:38:50 nicknas2 avahi-dnsconfd[16287]: read(): EOF Apr 30 14:38:50 nicknas2 avahi-daemon[16278]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.223. Apr 30 14:38:50 nicknas2 avahi-daemon[16278]: avahi-daemon 0.8 exiting. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Successfully dropped root privileges. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: avahi-daemon 0.8 starting up. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Successfully called chroot(). Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Successfully dropped remaining capabilities. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Loading service file /services/sftp-ssh.service. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Loading service file /services/smb.service. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Loading service file /services/ssh.service. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: New relevant interface virbr0.IPv4 for mDNS. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.223. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: New relevant interface br0.IPv4 for mDNS. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Network interface enumeration completed. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: Registering new address record for 192.168.1.223 on br0.IPv4. Apr 30 14:38:51 nicknas2 avahi-daemon[29972]: Server startup complete. Host name is nicknas2.local. Local service cookie is 4006073296. Apr 30 14:38:52 nicknas2 avahi-daemon[29972]: Service "nicknas2" (/services/ssh.service) successfully established. Apr 30 14:38:52 nicknas2 avahi-daemon[29972]: Service "nicknas2" (/services/smb.service) successfully established. Apr 30 14:38:52 nicknas2 avahi-daemon[29972]: Service "nicknas2" (/services/sftp-ssh.service) successfully established. Edited April 30 by nickp85 Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 Now I am getting this regularly in the log but no longer the other message Apr 30 14:50:30 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 14:50:30 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Apr 30 14:50:32 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is reachable again Apr 30 14:50:35 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 14:50:35 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Apr 30 14:50:42 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is reachable again Apr 30 14:54:35 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 14:54:36 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Apr 30 14:54:37 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is reachable again Apr 30 14:54:40 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 14:54:41 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Apr 30 14:54:46 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is reachable again Apr 30 15:14:08 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 15:14:09 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Apr 30 15:14:10 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is reachable again Apr 30 15:14:13 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 15:14:14 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router Quote Link to comment
bmartino1 Posted April 30 Share Posted April 30 (edited) you will need to turn off the dockers avahi zero config server. Its conflicting with unraids zero config server... Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** edit the docker and set Avila to 0: -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container ^there should only be 1 avahi server... if you have problems you will need to add dns ip routs to your pihole instance... Edited May 1 by bmartino1 spelling Quote Link to comment
nickp85 Posted April 30 Author Share Posted April 30 25 minutes ago, bmartino1 said: you wil need to turn off teh docers avia zeroconfig server. its conflicting with unrads zerconfig server.. Apr 30 14:38:50 nicknas2 avahi-daemon[29972]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** edit the docker and set Avila to 0: -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container ^there should only be 1 aviah server... if you have problems you wil lneed to add dns ip routs to your pihole instance... pihole does not run avahi. Homebridge does and I disabled it already via the variable, the problem has not stopped. I'm not sure what to do next. Quote Link to comment
bmartino1 Posted May 1 Share Posted May 1 (edited) avahi uses dns... pihole is or should be you dns server and should add static routes to assist in avahi zereconf... ... https://unix.stackexchange.com/questions/566932/what-is-the-avahi-daemon ... https://linux.die.net/man/8/avahi-daemon I would then recommend rebooting the entire machine. Edited May 1 by bmartino1 Quote Link to comment
bmartino1 Posted May 1 Share Posted May 1 (edited) if we could edit service configs, I would have you turn off ipv6. by adding noipv6rs noipv6 to the avahi config server since ipv4 seems to be working... Do you have any apple device on the network? What is your curenter router? It appears that the router is not doing ipv6 correctly and is breaking avahi: Apr 30 15:14:13 nicknas2 dhcpcd[1374]: br0: fe80::ea9c:25ff:fe89:a700 is unreachable Apr 30 15:14:14 nicknas2 dhcpcd[1374]: br0: soliciting an IPv6 router you can also try ifconfig br0 down && sleep 10 && ifconfig br0 up To then bring down the adapter and bring it back up. it appears that br0 may also be getting a bad response or captured bad ipv6 data that it can no longer talk to as it was using the docker avahi server... Otherwise, I would have you turn off ipv6 on unraid. In network settings. Edited May 1 by bmartino1 fix comand - spelling Quote Link to comment
nickp85 Posted May 1 Author Share Posted May 1 35 minutes ago, bmartino1 said: avahi uses dns... pihole is or should be you dns server and should add static routes to assist in avahi zereconf... ... https://unix.stackexchange.com/questions/566932/what-is-the-avahi-daemon ... https://linux.die.net/man/8/avahi-daemon I would then recommend rebooting the entire machine. I already have pihole on a separate IP and have the correct routes. My network uses pihole for all DNS. I’m not sure how that’s relevant here? I’ve rebooted Unraid several times. It always comes back with the first error I posted about withdrawing and registering address records. I do have Apple devices on my network, a lot of them. Quote Link to comment
bmartino1 Posted May 1 Share Posted May 1 (edited) 3 minutes ago, nickp85 said: I already have pihole on a separate IP and have the correct routes. My network uses pihole for all DNS. I’m not sure how that’s relevant here? I’ve rebooted Unraid several times. It always comes back with the first error I posted about withdrawing and registering address records. I do have Apple devices on my network, a lot of them. Thx apple try their forum? as well - https://discussions.apple.com/thread/335222?sortBy=best fun i'm out of ideas then on how to fix the issue as this could be a broader issues from apple zerconfig and simlar to netbios the other apples zerconf may have saved it... Ontop of the router on your networking and there ipv6 implementation.... I would recommend disabling ipv6 on unraid to see if that fixes the issues. Edited May 1 by bmartino1 Quote Link to comment
nickp85 Posted May 6 Author Share Posted May 6 Still looking for a solution to this issue if someone can please help. Thank you! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.