Closed simphide closed 1 year ago
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (zeroconf
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zeroconf documentation zeroconf source (message by IssueLinks)
The problem still persists 😐
While IPv6 is disabled in HA configuration:
See it anyway enabled/exists on HA OS/Supervisor (?) level:
That leading to following: mDNS occasionally returns IPv6 addresses.
➜ ~ wget http://ewelink_100169f2ad.local.:8081/zeroconf/info
--2023-02-18 20:37:08-- http://ewelink_100169f2ad.local.:8081/zeroconf/info
Resolving ewelink_100169f2ad.local. (ewelink_100169f2ad.local.)... fe80::96b5:55ff:fef7:f108
Connecting to ewelink_100169f2ad.local. (ewelink_100169f2ad.local.)|fe80::96b5:55ff:fef7:f108|:8081... failed: Invalid argument.
Same time on PC with ONLY IPv4 enabled.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem still exists...
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem still exists...
This issue looks similar to https://github.com/home-assistant/core/issues/69669 .
Do you have a firewall on the server running HA that blocks all outgoing ipv6 traffic?
On Debian it was the case by default for me when using ufw
for example. In /etc/default/ufw
:
# Set to yes to apply rules to support IPv6 (no means only IPv6 on loopback
# accepted). You will need to 'disable' and then 'enable' the firewall for
# the changes to take affect.
IPV6=no
In my case setting it to IPV6=yes
followed by disabling and enabling ufw
fixes the issue.
In my case setting it to
IPV6=yes
followed by disabling and enablingufw
fixes the issue.
This worked for me as well. Thanks.
Same! It solved my problem! Thank you very much!
The problem
I am currently getting the following error from Zeroconf as soon as Home Assistant starts:
This is then follower by these recurring error messages:
When I grep via netstats for the ports that Home Assistant is using, I get the following:
The network adapter shows that the IPv6 address is correct:
Does it lead to trouble that Home Assistant trys to use Port 5353 via :::5353 and fe80::921b:eff:fe5:5353?
Best regards Simon
What version of Home Assistant Core has the issue?
Home Assistant 2023.2.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Zeroconf
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zeroconf/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response