kiwi35
February 12, 2024, 9:44am
1
Hello,
koying
February 12, 2024, 2:20pm
2
HA itself should have IPV6, but not the addons, apparently.
opened 08:35AM - 16 Jan 24 UTC
bug
board/raspberrypi
### 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?
```txt
WARNING (MainThread) [supervisor.api.ingress] No valid ingress session
```
### Anything in the Host logs that might be useful for us?
```txt
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
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
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)
</details>
<details><summary>Dashboards</summary>
dashboards | 1
-- | --
resources | 0
mode | auto-gen
</details>
<details><summary>Recorder</summary>
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
</details>
### Additional information
moved from https://github.com/home-assistant/core/issues/108071#issuecomment-1891523208
documentation failed to mention this for OS related faults
WallyR
February 13, 2024, 11:10pm
3
You will get all types of errors with IPv6, like addons not working, integrations not working and problems with defining the IPv6 network in HA itself.
I have yet to find a way to define multiple IPv6 addresses in HA, so I can have both fe80, fc00 and my DHCP-PD prefix. There also seems to be no way to insert your InterfaceI in addresses.
kiwi35
February 14, 2024, 3:11pm
4
Well maybe in 2024 to have some IPv6 working stuff should be a good idea… Really… I don’t want see 240.x.x.x ip used … (see nanog mailing list).
1 Like
koying
February 15, 2024, 7:03am
5
Could you clarify what you’re talking about? I don’t have the reference
1 Like
kiwi35
February 15, 2024, 1:21pm
6
Well some people want to use reserved 240.0.0.0/4 prefix to global internet instead of moving into IPv6, see : https://mailman.nanog.org/pipermail/nanog/2024-February/224821.html
