IPv6 functionality is broken

[Vectrobe]

Describe the issue you are experiencing

Any kind of network operation with any ipv6 address is completely broken, most commands such as ping return "bad address" or "Address not available"
This is despite ipv6 being available and the device being assigned correct local and global ipv6 addresses, and having direct access to a working ipv6 network, it is also still possible to ping the homeassistant device externally using mDNS, and it will both return the correct ipv6 local fe80 address, and successfully ping the device consistently. The problem is internal to the OS and its networking functionality.

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

11.4

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1. install the OS to a device (whether or not its specific to ARM64 is unclear)
2. ensure its connected to a working ipv6 network
3. run 'ping -6 homeassistant' or 'ping ::1', it will fail

Anything in the Supervisor logs that might be useful for us?

WARNING (MainThread) [supervisor.api.ingress] No valid ingress session

Anything in the Host logs that might be useful for us?

unknown

System information

System Information

version	core-2024.1.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.1.63-haos-raspi
arch	aarch64
timezone	Australia/Sydney
config_dir	/config

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.4
update_channel	stable
supervisor_version	supervisor-2023.12.0
agent_version	1.6.0
docker_version	24.0.7
disk_total	57.8 GB
disk_used	5.9 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	CEC Scanner (3.0), VLC (0.3.0), File editor (5.7.0), Terminal & SSH (9.8.1), Matter Server (5.0.2)

Dashboards

dashboards	1
resources	0
mode	auto-gen

Recorder

oldest_recorder_run	January 15, 2024 at 4:43 AM
current_recorder_run	January 15, 2024 at 4:02 PM
estimated_db_size	90.59 MiB
database_engine	sqlite
database_version	3.41.2

Additional information

moved from home-assistant/core#108071 (comment)

documentation failed to mention this for OS related faults

[agners]

run 'ping -6 homeassistant' or 'ping ::1', it will fail

In which context do you run this command? I assume using the SSH/Web terminal?

The SSH/Web terminal runs as an add-on, and for add-ons we indeed do not have IPv6 support currently. This is a Docker/Container/Supervisor limitations. There have been initial works being done on OS side, and attempts in implementing IPv6 support for add-ons on the Supervisor side (see home-assistant/supervisor#2133). But currently support is not completed yet.

In general, HAOS itself has IPv6 support. Home Assistant Core, which runs the main web server to deliver the front-end and connects to devices through it's integration runs on host network, and therefor supports IPv6 too. Add-on such as Matter and the OpenThread add-on, both technologies rely on IPv6, run in host network context too, and have IPv6 support.

This is despite ipv6 being available and the device being assigned correct local and global ipv6 addresses, and having direct access to a working ipv6 network, it is also still possible to ping the homeassistant device externally using mDNS, and it will both return the correct ipv6 local fe80 address, and successfully ping the device consistently. The problem is internal to the OS and its networking functionality.

mDNS and pinging link local IPv6 addresses should work fine from the host network context. Did you try to just use the mDNS name in Home Assistant Core?

[Vectrobe]

So if its specifically the web side terminal at fault I would have to use the physical display output and keyboard to verify?

[agners]

Yes, or you can use the "Advanced SSH & Web Terminal" from the community store. It runs on host network too (as indicated by the icon in the add-on store).

[agners]

@mytering @latargere the issue you are seeing in the Matter add-on is not an issue per see home-assistant/core#109926 (comment). This is a library bug trying to use the IPv6 localhost (::1) for multicast, which is not supported. This is not problematic for Matter operation. Please ignore the message, we are working on getting the localhost interface ignored.

[agners]

I am closing this issue as this is not a operating system issue per-se (see comment above). The missing IPv6 functionality for add-ons is handled by the linked issue above.