-
Notifications
You must be signed in to change notification settings - Fork 928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot manage vlan connections with nmcli due to ipv4.dns-data member #2636
Comments
Generally, you should not need to use nmcli directly. Instead use the What are you trying to achieve? It sounds like there is a unsupported property in the connection settings, can you check if that is indeed the case in |
There's no way to assign a 'default' connection when setting up multiple vlans, or set the priority of any one network path over another, except via nmcli, as far as I can tell. A non-desired network is being selected as the default, and I'm trying to override it. FWIW, I'm not aware of any way to set up VLANs in HAOS other than this, either, happy to learn if there's a better/right way. That command doesn't work, I've got an the output of
|
I am having this problem as well. Was trying to set static IPs for multiple interfaces. |
@Particpant did you get a solution for this? Thanks! |
No, I have not. |
This is the same behavior seen when using the interactive editor....it will let me manually remove DNS and add DNS servers with the add and remove commands. With that said when saving, it validates the properties and rattles off the "ipv4.dns-data: unknown property" error if the DNS property has a value set. I can, however, remove the DNS entry and save without issues, but now I don't have a DNS server configured.... |
Seeing exactly the same here on OS 10.4 - Thought I might be able to work around this by deleting the dns object and re-adding it. Nope. Same problem. dns-data gets added when you add a static route.. why? To compound the problem; when re-adding the DNS server with No dice either. I had to restore a snapshot to clean out the mess I made |
Same here. Always get ipv4.dns-data: unknown property on saving a connection. |
😿 came here was hoping for a fix. I have HA running on baremetal and I am getting the same error
|
I am having the same issue on 2023.9.3 |
Hi all, It seems that on this link similar issue has been solved: https://almalinux.discourse.group/t/unable-to-set-dns-with-nmcli-ipv4-dns/2442/4
My linux/network knowledge is so poor and barely know what these commands are doing so I am afraid of break something. |
I have the same issue, but you can save the config if you remove the ipv4.dns setting:
|
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
don't close. |
Thanks for the workaround! This workaround should not be necessary. Can it not be fixed? |
Hello, same issue here, please don't close the issue. Verified/reproduced on HaOS 11.1 Warning: nmcli (1.44.2) and NetworkManager (1.40.18) versions don't match. Restarting NetworkManager is advised. I used nmcli on HaOS in the past, but I don't remember this message in previous HaOS versions. PS: workaround as eplained is ok (after deletion of ipv4.dns is sufficient to re-add DNS in the HomeAssistant user interface (settings->system->network) |
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
still present |
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 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
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
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:
The text was updated successfully, but these errors were encountered: