disuye
(disuye)
February 24, 2024, 11:54am
1
I run HA out of VirtualBox so this issue might have more to do with virtual machine networking (not my skillset!) than Home Assistant, but with regards to the following command…
curl -6 'http://umbrel.local:8332/' -u 'umbrel:PASSWORD' -d '{"jsonrpc":"1.0","id":"homeassistant","method":"getblockcount","params":[]}' -v
On my desktop Terminal I am given the correct JSON response. Unfortunately HA Terminal spits out the following error…
* Could not resolve host: umbrel.local
* Closing connection
curl: (6) Could not resolve host: umbrel.local
Any thoughts?
If I use -4 / IPV4 then I am able to connect to the server (both on desktop and HA Terminals) however no JSON response is given in either instance. Thanks.
disuye
(disuye)
February 25, 2024, 8:46am
2
Does anyone know if my issue is related to this?
opened 08:35AM - 16 Jan 24 UTC
closed 09:58PM - 16 Feb 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