Thank you to u/beepbeepboop-2 for sharing a ZimaBoard story built around infrastructure rather than a photo library. In this lab, small boards support routing, virtualization and network experiments. The interesting result is the opportunity to work through real dependencies between a firewall, virtual machines and storage.
The original Reddit contribution describes pfSense, a three-node Proxmox environment, VLANs and a separate TrueNAS storage system. A recurring network timeout becomes the most useful episode: it forces the creator to reconsider how much traffic should share one physical interface.
ZimaBoard Became Part of the Networkโs Foundation
One early role was the main pfSense router and firewall. The creator separated management, LAN, Wi-Fi, access-point infrastructure and lab or DMZ systems into different VLANs. DHCP, routing between VLANs and firewall policy sit with pfSense in this design.
The value of those boundaries is easiest to see through a user action. A lab VM can belong to a different network from an everyday client. Whether it may reach another system is then a policy decision, rather than a consequence of putting every device into the same local network.
Netgateโs pfSense VLAN documentation provides the configuration background for readers developing that idea. A VLAN is one part of the arrangement; the interfaces, switch configuration and routing policy still have to agree about how traffic moves.

Three Different Layers Have Three Different Jobs
| Layer | Role described in this lab | Why the distinction matters |
|---|---|---|
| pfSense | DHCP, routing and firewall policy | Decides how the networks communicate |
| Proxmox VE and SDN | Virtual machines, virtual switching and network attachment | Places workloads into their intended networks |
| TrueNAS | Separate shared NFS storage | Provides storage outside the ZimaBoard compute role |
| Backup environment | Centralized protection with changing destinations | Introduces another source of traffic to consider |
In the creatorโs SDN arrangement, Proxmox supplies switching and VM network attachment; it is not performing NAT, routing or DHCP for that environment. That is a description of this configuration, not a statement that Proxmox has no other networking capabilities. The official Proxmox SDN documentation covers the broader feature set.
Separating those roles makes troubleshooting more precise. A VM can have the right virtual network attachment while an upstream firewall rule still prevents access. A reachable shared-storage server can also be a separate concern from the availability of a particular compute node.
Our ZimaBoard Proxmox cluster guide offers related setup context. This community account adds the operating experience: the network becomes more interesting once shared services and experiments are running together.
A Timeout Changed the Way the Creator Viewed Backup Traffic
After expanding backup activity, the creator began seeing intermittent connectivity losses. Rebooting pfSense restored access temporarily. Logs repeatedly showed re1: watchdog timeout, and the affected interface also carried several VLANs.
During troubleshooting, two newer backup destinations were disabled while the original workflow stayed active. Stability improved. The creator is explicit about the limit of that observation: it does not prove that backup traffic alone caused the problem. It does, however, identify a useful change to investigate.
This is the difference between a useful incident report and an unsupported fix. The sequence records the symptom, the log evidence, the change made and the result observed. It does not establish a universal interface limit or a driver diagnosis for every ZimaBoard running pfSense.
Netgateโs packet-loss troubleshooting guidance is an appropriate reference for investigating lost traffic. In this story, the next design direction is to spread some VLAN traffic across separate physical interfaces instead of concentrating everything on one.
The Cluster Is a Place to Learn Infrastructure Concepts
The three-node environment gives the creator room to explore VM migration, shared NFS storage, centralized backups, high availability and VLAN-aware networking. Windows Server, Kali Linux, Docker workloads and Guacamole appear among the experiments. The point is the range of infrastructure relationships that can be studied at a manageable physical scale.
The storage choice is particularly clear: TrueNAS provides shared storage separately, while the ZimaBoards serve the compute role. This is not an all-in-one ZimaOS NAS configuration. A mixed lab can still be a strong ZimaBoard story when the contribution explains exactly what the boards do.
High availability is named as an area of experimentation. The post does not provide a failover test record or a service-level guarantee. Reading the build as a learning environment preserves its value without turning a list of platform features into promises about uptime.
A smaller, physically customized virtualization build appears in the silent dual-NVMe ZimaBoard 2 homelab. The contrast is useful: one story emphasizes compact packaging, while this one emphasizes network boundaries and the behavior of a mixed infrastructure stack.
Permanent Infrastructure Needs Better Physical Organization
The creatorโs main hardware complaint is the lack of a suitable rack-mount ecosystem for their boards. Once the machines become permanent infrastructure, shelves full of power leads, SATA cables and network connections are harder to treat as a temporary arrangement.
The request is specific: a well-designed 1U or multi-board enclosure with airflow, cable management and accessible interfaces. The story does not claim such an enclosure was built or supplied. It records what the owner still wants after using the hardware in a larger installation.
For a new build, compare the actual ports and expansion arrangement of the model being purchased. The current ZimaBoard 2 specifications describe a different generation; the contributorโs original ZimaBoards should not be silently relabeled as that newer model. Hardware selection belongs alongside the network design, especially when one interface is expected to carry several roles.
FAQ
Is ZimaOS the operating system in this story?
The described roles use pfSense and Proxmox on ZimaBoard hardware, with a separate TrueNAS storage system. The contribution is a Zima hardware story rather than a ZimaOS NAS walkthrough.
What does Proxmox SDN do in this particular setup?
It provides virtual switching and network attachment for VMs. The creator assigns routing, DHCP and firewall policy to pfSense in the reported arrangement.
Did backup traffic definitely cause the watchdog timeouts?
The creator does not claim that. Reducing the newer backup activity improved stability, but the observation alone does not establish a single root cause.
Are the ZimaBoards also the primary shared-storage servers?
No. Shared NFS storage is provided separately through TrueNAS. This distinction is central to understanding the compute and storage roles.
Does the three-node cluster prove uninterrupted service?
No uptime guarantee or completed failover test is documented. The account describes experiments with clustering and high availability, alongside the problems encountered while learning.
Conclusion
For beepbeepboop-2, ZimaBoard became a compact platform for learning how infrastructure behaves. The firewall, virtual networks, compute nodes and shared storage each have a role, and their interactions create the lessons that a successful installation screen cannot provide.
The timeout episode is the strongest example. A logged symptom led to a controlled change and a more deliberate plan for distributing traffic. The project earns its interest through that operating experience, including the physical organization that the creator still wants to improve.
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.


