This long-running thread spans several ZimaOS generations, so the original 2024 CLI recipe should not be treated as the current default. Later replies explicitly said static IP configuration had moved into the web settings, while a June 2026 ZimaBoard 2 user reported one case where the UI would not edit eth1 until NetworkManager was adjusted manually.
Use the Current ZimaOS UI First
If the target Ethernet port can be edited in current Settings, use the UI rather than recreating a connection profile from an old forum command. That reduces the risk of selecting the wrong interface or leaving duplicate NetworkManager profiles.
The ZimaOS troubleshooting workflow is useful when the dashboard or network address itself is not reachable, while the Zima Client overview covers current Zima discovery and connection behavior. On dual-port hardware, the ZimaBoard 2 hardware provides the current Ethernet hardware context before you decide which interface should use the fixed address.
If You Must Use nmcli, Identify the Profile First
Do not paste an old connection name blindly. Start by inspecting the current profiles:
nmcli connection show
nmcli device statusNetworkManager's NetworkManager static IP examples shows the current supported pattern for manual IPv4 configuration. The NetworkManager IPv4 settings confirms that ipv4.method manual requires at least one address and that a gateway configures the normal default route.
Why the Old Copy-Paste Failed for Some Users
The thread documented two easy mistakes: the active connection name was not always exactly Wired connection 1, and the forum editor had converted straight quotes into typographic quotes.
If a command says the connection is unknown, copy the exact connection ID shown by nmcli connection show. Do not assume eth0, eth1, Wired connection 1, or a Zima-prefixed profile name is universal.
Consider a DHCP Reservation Instead
If your only goal is for ZimaOS to keep the same LAN address, a DHCP reservation on the router can be simpler because the host remains on automatic addressing while the router consistently leases the same address. That also reduces the chance of creating an address conflict outside the DHCP pool.
Bottom Line
Use the current ZimaOS network UI first. Keep the old nmcli method as a fallback for a port the UI cannot edit, and always inspect the current connection profile before modifying it. A router-side DHCP reservation is often the least fragile option for a normal home server.
