Skip to content

FCEFyN testbed documentation

Hardware-in-the-loop testing for OpenWrt and LibreMesh at FCEFyN, Universidad Nacional de Córdoba. Source and tooling live in fcefyn_testbed_utils. Tests align with openwrt-tests and libremesh-tests.


Before you start

Testbed goal and scope, in brief:

  • Validate firmware for OpenWrt and LibreMesh-based routers in an automated, repeatable way using the Labgrid + pytest ecosystem, following openwrt-tests and libremesh-tests.
  • Cover physical and emulated targets: tests on physical devices in a rack over physical links and on QEMU instances with WiFi simulated via vwifi.
  • Operate a shared lab: one DUT inventory for both projects (Lab architecture).

New developer? Start here: Developer quickstart - SSH setup, repos, firmware, and first test run.

Testbed overview

Relationship between orchestration host, switch, gateway, DUTs, power, and serial access:

High-level diagram of the testbed and main components

The design builds on the remote lab model from openwrt-tests, but scope is not limited to adding devices to that network. It also reuses and extends the approach with local infrastructure, along the same axes (orchestration, network, power, serial) with a focus on LibreMesh testing.


Quick actions

I want to… Go to
Run tests on lab hardware from my machine Developer quickstart
Build a LibreMesh firmware and test it automatically CI: Build & Test
SSH into a DUT SSH access to DUTs
Check the rack layout and device IPs Rack quick reference
Build firmware manually Build firmware
Add a new device to the lab Adding a DUT