I ditched my Raspberry Pi for this

A compact x86 mini-computer (the Zema board) replaced a Raspberry Pi travel setup, enabling a single “travel NAS + travel router” approach that kept a family connected in hotels, Airbnbs, and even on a plane—while also streaming Plex and uploading vlog footage back to a studio. The core win wasn’t just raw performance; it was flexibility. With an Intel Celeron quad-core (8GB RAM, 32GB storage) and multiple expansion options (including SATA and an add-in PCIe slot), the Zema board could run storage and networking software that a Raspberry Pi couldn’t comfortably support for this trip’s heavier demands.

The project started with prior Raspberry Pi builds: an OpenWrt-based travel router and an OpenMediaVault travel NAS for backing up files to the studio. But the Japan trip required more: faster connectivity for six kids, Plex streaming during a 14-hour flight, Docker/VM experimentation, and a reliable way to back up recorded footage overnight. The creator also wanted nested virtualization—specifically the ability to run Proxmox—so the Zema board became the platform of choice after it was found in a closet.

Proxmox was installed on an external SSD, with PCI passthrough enabled by turning on BIOS settings (IOMMU/VT-d). That unlocked the idea of running a router stack inside a virtual machine. However, the router experiment hit practical roadblocks: OpenWrt-on-virtualized hardware proved driver-heavy, and a wireless router VM approach (using RASP AP) suffered from stability issues—connections dropped and didn’t reliably recover. With limited time before departure, the “one device running everything under virtualization” plan was abandoned.

For routing, the solution shifted to a purpose-built travel router: a GL.iNet gigabit travel router running OpenWrt with a simple setup flow. It connected to whatever network was available (wired or via client mode), then broadcast a local Wi‑Fi for the family, handled DHCP for the Zema board, and supported VPN-style protection for traffic.

For storage and media, the creator ultimately used CasaOS—the Debian 11-based system shipped with the Zema board—rather than TrueNAS. TrueNAS installed cleanly and storage setup was manageable, but Plex became a deadline-killing problem: Plex deployed via Kubernetes repeatedly tried to pull the newest image from GitHub and failed when GitHub wasn’t reachable, leaving Plex unable to boot. CasaOS delivered a more dependable path: plug in two SSDs (via a SATA Y-connector), manage folders through a web interface, install Plex from the app store, and keep the system accessible over the network.

The final piece was remote syncing. Instead of relying on a traditional cloud sync workflow, SyncThing ran as a Docker container on the travel NAS and on the studio NAS. Using SyncThing’s remote device pairing (device ID exchange), the two systems discovered each other over the internet without a VPN and synced footage continuously, letting uploads “trickle” overnight. Plex worked across devices (iPads included) and even on the plane under-seat. The result: a travel setup that prioritized reliability over experimentation, delivering connectivity, offline-friendly media, and automated backup while moving across Japan.