Current Answer: Yes, ZimaOS Can Put Its Two Ethernet Ports on Different Networks
Modern ZimaOS exposes every physical Ethernet port separately in Settings → Network. Each interface can receive its own DHCP address or manual static IP. That is exactly what you need when a ZimaBoard should be reachable on two separate subnets at the same time.
The ZimaOS network interfaces describes per-port link state, speed, IP and manual addressing.
Use Different Subnets on the Two Ports
Example:
eth0: 192.168.10.20/24
eth1: 10.20.0.20/24Clients on 192.168.10.0/24 can reach the first address, while clients on 10.20.0.0/24 use the second. Do not configure both ports in the same subnet unless you have a specific reason and understand Linux routing/ARP behavior.
Usually Only One Interface Should Own the Default Gateway
If both networks provide internet gateways and you enter both as equal defaults, outbound traffic can take an unexpected path. Check:
ip addr
ip routeThe Linux IP routing table explains how default and connected routes are selected. For simple dual-network access, one default gateway plus a directly connected second subnet is easier to reason about.
This Is Not Link Aggregation
Two ports on two networks do not double the speed of one client connection. Link aggregation/LACP is a different design that usually requires switch configuration and multiple flows. The original thread was explicitly asking for simultaneous membership in two networks, not bonding.
Decide Whether ZimaOS Should Route Between the Networks
By default, “ZimaOS has an address on both networks” and “ZimaOS forwards traffic between the networks” are different things. If you want it to act as a router/firewall, that requires IP forwarding and deliberate firewall policy. Do not enable forwarding casually between a trusted LAN and an untrusted IoT/guest network.
The Linux IP forwarding covers the kernel-level behavior.
Docker Apps May Listen on Both Interfaces Unless You Restrict Them
A container port published as 0.0.0.0:PORT is typically reachable through any host interface allowed by firewall policy. If one app should exist only on one network, bind it to the intended host IP or add firewall restrictions.
The ZimaOS app networking helps when Docker services share the same dual-homed server.
Use Dual NICs for Separation, Not as a Substitute for Remote Access
Common designs include main LAN + camera network, home LAN + lab VLAN, or management LAN + storage network. If the only goal is reaching ZimaOS from outside the house, use secure remote access rather than attaching the NAS to an unnecessary second local network.
The ZimaBoard 2 networking and Pi-hole network services provide practical dual-NIC use cases.
Test the Two Paths From Clients on Both Networks
After saving both interfaces, do not stop at “both links are green.” From a client on Network A, ping and open the ZimaOS address on Network A. Repeat from Network B using the second address. Then check ip route get DESTINATION on ZimaOS when troubleshooting unexpected outbound paths. This proves which interface and source IP Linux actually chooses rather than relying on dashboard labels alone.
FAQ
Can both ZimaBoard Ethernet ports work at the same time?
Yes. In current ZimaOS, each physical interface is shown and configured separately.
Can each port use a different static IP?
Yes. Put the two interfaces on different subnets and configure the address appropriate for each network.
Should both interfaces have a default gateway?
Usually no for a simple dual-network server. One default gateway avoids ambiguous outbound routing unless you intentionally configure policy routing.
Does using both ports double SMB speed?
Not automatically. Two independent networks are not link aggregation, and one normal SMB session usually follows one route.
Can Docker apps be reachable from both networks?
Yes if their ports are published on all host addresses and firewall policy allows it. Bind or filter them if only one network should reach the app.
Can ZimaOS route traffic between the two networks?
Linux can route when IP forwarding and firewall rules are configured, but that is a separate network-security role from simply giving the NAS two addresses.
