Closed benniju closed 1 month ago
Don't know anything about HA, but have you enabled ipv6 networking in docker (docs at https://docs.docker.com/config/daemon/ipv6/)?
Hmm, I'm not really comfortable with modifying the defalt setup, as this is usually quite locked up and not supposed to be changed.
I have found another thread about IPv6 Support though: https://community.home-assistant.io/t/ipv6-only-with-home-assistant-os/688811 There also seems to be some work on this, but not any progress currently. But you can enable IPv6 by following this tutorial apparently: https://github.com/home-assistant/supervisor/issues/2133#issuecomment-1950722961
Thanks for your issue report, however, it is in an incorrect location.
This is the issue tracker for the community add-ons repository index; your issue/feature request is however meant for the Home Assistant project. Please report it with that project instead.
../Frenck
Problem/Motivation
I wan't to use IPv6 networing in some of the Addons, in this case uptime-kuma to monitor and ping an host which only has an AAAA (IPv6) record and only IPv6 Address, for example
ipv6.google.com
Expected behavior
I expect the ping to work and not to give an error.
Actual behavior
The ping fails with the error
ping: connect: Address not available
This is the output when I try to use ping in the docker container using docker exec:
See this issue discussion for some additional information: https://github.com/louislam/uptime-kuma/issues/3113#issuecomment-2133211835
Steps to reproduce
Add a Ping monitor in Uptime Kuma with the hostname
ipv6.google.com
Proposed changes
Add IPv6 support for the default Home Assistant docker network.
The problem does not occur when creating the addon locally and adding
host_network: true
to config.yaml But this is not a real solution, as it decreases the security rating and you can not change the port easily anymore then.