operating-system: Cannot manage vlan connections with nmcli due to ipv4.dns-data member
Describe the issue you are experiencing
If I try to modify any of my vlan connections, say to rename them, or to mark as ‘never-default’, I run into an error from nmcli:
nmcli con mod <uuid> ipv4.never-default 'yes'
Error: Failed to modify connection 'Supervisor enp3s0.8': ipv4.dns-data: unknown property
nmcli con mod <uuid> ipv4.dns-data ''
Error: invalid property 'dns-data': 'dns-data' not among [method, dns, dns-search, dns-options, dns-priority, addresses, gateway, routes, route-metric, route-table, routing-rules, replace-local-rule, ignore-auto-routes, ignore-auto-dns, dhcp-client-id, dhcp-iaid, dhcp-timeout, dhcp-send-hostname, dhcp-hostname, dhcp-fqdn, dhcp-hostname-flags, never-default, may-fail, required-timeout, dad-timeout, dhcp-vendor-class-identifier, link-local, dhcp-reject-servers, auto-route-ext-gw].
nmcli similarly refuses to apply modifications via the interactive editor.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
Home Assistant OS 10.3
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- Have vlan connections set up in nmcli (followed tutorial here: https://community.home-assistant.io/t/setup-vlan-and-ha-tutorial/87705/111)
- Be on current HAOS (unknown if this is newly introduced or longstanding.
- Attempt to modify any existing connection via nmcli …
Anything in the Supervisor logs that might be useful for us?
I didn't see anything relevant in these logs
Anything in the Host logs that might be useful for us?
I didn't see anything relevant in these logs
System information
System Information
| version | core-2023.7.1 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.4 |
| os_name | Linux |
| os_version | 6.1.34 |
| arch | x86_64 |
| timezone | America/Los_Angeles |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.32.1 |
| Stage | running |
| Available Repositories | 1272 |
| Downloaded Repositories | 3 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | May 18, 2024 at 12:00 AM |
| relayer_connected | true |
| relayer_region | us-east-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | false |
| remote_server | us-east-1-8.ui.nabu.casa |
| certificate_status | ready |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 10.3 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.07.1 |
| agent_version | 1.5.1 |
| docker_version | 23.0.6 |
| disk_total | 109.3 GB |
| disk_used | 13.5 GB |
| healthy | true |
| supported | true |
| board | generic-x86-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Samba share (10.0.2), File editor (5.6.0), Terminal & SSH (9.7.1), Advanced SSH & Web Terminal (15.0.3), Z-Wave JS UI (1.14.0), ESPHome (2023.6.4), Logitech Media Server (0.0.53) |
Dashboards
| dashboards | 7 |
|---|---|
| resources | 0 |
| views | 19 |
| mode | storage |
Recorder
| oldest_recorder_run | June 29, 2023 at 2:06 PM |
|---|---|
| current_recorder_run | July 9, 2023 at 7:23 PM |
| estimated_db_size | 194.51 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
Additional information
I’ve rebooted multiple times (both HA and the hardware itself) to no avail. Additionally, I’ve seen a similar issue referenced elsewhere, which indicate a possible version mismatch between nmcli and NetworkManager: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1307
I wasn’t able to run any of the suggested troubleshooting steps, as systemctl and journalctl aren’t installed in HAOS:
~ # nmcli --version
nmcli tool, version 1.42.8
~ # systemctl restart NetworkManager.service
-bash: systemctl: command not found
~ # journalctl -b0 -u NetworkManager | grep 'is starting'
-bash: journalctl: command not found
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 2
- Comments: 17 (1 by maintainers)
don’t close.