Thank you to u/Bici0 for sharing a compact ZimaBoard server built around two network connections, Proxmox and remote access. The machine boots from PCIe NVMe storage, keeps data on two mirrored SSDs, and sits in a small rack with a separate remote KVM.
The original Reddit build is useful because the creator explains what each physical connection is meant to do. One Ethernet port goes to the normal home network; the other connects to a secondary VPN router. The resulting project is as much about operating the server from elsewhere as it is about fitting hardware onto a desk.
A Compact Rack with Separate Boot and Data Storage
The ZimaBoard runs Proxmox VE from an NVMe drive connected through PCIe, with an aluminum heatsink on that storage assembly. Two SSDs provide RAID 1 data redundancy. This keeps the hypervisor’s boot device conceptually separate from the mirrored data drives.
The creator also places a GL.iNet Comet PoE remote KVM in the rack. The rack is described as a ZimaBlade rack, but the computer itself is a ZimaBoard. That distinction matters when identifying the build: an accessory’s product name does not change which board is running the workloads.
| Component | Role described by the creator |
|---|---|
| ZimaBoard | Always-on Proxmox VE host |
| PCIe NVMe drive and heatsink | Hypervisor boot storage |
| Two SSDs in RAID 1 | Mirrored data storage |
| eth0 | Connection to the main LAN and fiber router |
| eth1 | Connection to a secondary GL.iNet VPN router |
| Tailscale | Reported subnet-router and exit-node roles over the VPN network |
| Comet PoE remote KVM | Separate console-access device mounted in the rack |

Two Ethernet Ports Serve Different Connections
The first interface, eth0, connects to the ordinary home LAN through the fiber router. The second, eth1, goes to a secondary router used for VPN connectivity. The owner therefore gives the server access to two distinct network paths rather than describing both ports as interchangeable cables.
That is the topology reported in the post. It does not include a complete Proxmox bridge configuration, routing table or firewall policy. Two connected interfaces alone cannot establish which gateway a particular VM uses, whether traffic is forwarded between networks, or what happens when the VPN disconnects.
For a reader reproducing the idea, documenting those choices would be the next step. Write down the management address, the guest network attachment and the intended default route before changing a working remote connection. This is a practical consequence of the layout, not a set of settings recovered from the original machine.

A Subnet Router and an Exit Node Answer Different Questions
The creator reports using Tailscale as both a subnet router and an exit node over the VPN network. Those names describe different traffic destinations. Tailscale’s subnet-router documentation explains access to private network devices that do not themselves run the client. Its exit-node documentation describes routing public internet traffic through a selected device.
For this build, the distinction is useful when reading the phrase “remote access.” Reaching a home file service and choosing where a remote laptop’s internet traffic exits are separate operations. A design can support both, but success with one does not demonstrate that the other is correctly configured.
The source does not publish a packet trace, DNS behavior or VPN failure test. It therefore supports the creator’s intended arrangement, without establishing that all traffic always follows one route or that a kill switch has been verified.
Remote Console Access Adds Another Way to Reach the Host
The Comet device is physically separate from the Proxmox host and occupies the lower portion of the assembly. That gives the rack a different sort of management component from an application running inside a guest. A problem affecting the guest’s network access does not necessarily describe the state of the physical console.
There are still dependencies to consider when copying the arrangement. The remote device needs power and a reachable network path of its own. The post does not document an independent internet connection or a complete recovery drill, so the presence of the KVM should not be read as a guarantee of access through every failure.
Our quiet mini-rack story with ZimaBoard storage and Proxmox nodes offers a related comparison: compact systems can divide storage, compute and management roles in different ways. Comparing responsibilities is more useful than assuming that every small rack follows the same architecture.
Mirrored SSDs Address One Storage Failure Scenario
RAID 1 is the creator’s choice for data redundancy. The mirrored pair is visible in the annotated images, while the NVMe device has a separate boot role. That makes the physical storage layout relatively easy to follow even without a detailed hypervisor configuration.
A mirror is still a different tool from a recoverable historical copy. It can preserve the same deletion or unwanted change on both members. The post does not describe a separate backup destination, retained versions or a tested restore, so those capabilities cannot be inferred from the two-drive layout.
For another owner, the useful follow-up would be to identify where the Proxmox guests and important files are backed up, then try restoring a small sample somewhere separate. That would extend this storage design into a recovery plan; it is not a result claimed for Bici0’s machine.
The Rack Makes Cabling Part of the Project
The side photo shows a front-facing USB extension and the way cables pass around the storage devices. These details are modest but practical: a connector that can be reached without dismantling the stack changes how easy it is to maintain a compact build.

In a follow-up, the owner says the SATA and NVMe drives are powered through the ZimaBoard adapter without additional power supplies. That describes this particular combination of parts. It does not establish a power budget for arbitrary extra drives or accessories.
The creator calls the setup quiet and efficient, but supplies no wattmeter or acoustic measurements. The useful evidence here is the assembly and the assigned roles. The original ZimaBoard product page provides the matching hardware reference. Our small homelab story from u/jc-21 gives another example of building a service plan around limited physical space.
FAQ
Is this server a ZimaBoard or a ZimaBlade?
The computer is a ZimaBoard. The creator refers to a ZimaBlade rack as part of the mounting arrangement, which should not be confused with the host hardware.
What does each network port connect to?
eth0 connects to the main LAN through the fiber router. eth1 connects to a secondary GL.iNet router used for the VPN network.
Does RAID 1 mean the files have a separate backup?
No separate backup is documented. The mirrored SSDs provide data redundancy, but the source does not establish retained versions or an independent recovery copy.
Can the exact VPN routing be copied from the post?
The post provides the topology and intended roles, not the complete bridge, firewall, routing or DNS configuration. Those settings would need to be designed and checked separately.
Conclusion
Bici0’s ZimaBoard rack gives a small server a clearly described network and management role. NVMe boot storage, mirrored data SSDs, two router connections and a separate remote console all fit into one compact assembly. Its value as a build story is the visible connection between those parts and their jobs, with routing and recovery details left as questions to verify before reproducing the design.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.


