Network hardware testing for real-world conditions

Test routers, gateways and connected devices across real traffic, network configurations and multi-device environments with Midair.

Modern network devices fail in ways traditional tests often miss: unstable connections, timing issues, configuration conflicts, and failures that only appear across multiple devices.

Why network devices fail in production

Network hardware rarely fails in isolation.

Problems often appear when firmware, communication protocols, hardware limitations, and real traffic conditions interact.

Midair makes these scenarios repeatable before they become production failures. The device, firmware version, network conditions and test configuration stay attached to each run.

What makes network testing complex

Network conditions vary from one run to the next, and that makes a result hard to reproduce.

Variability in network conditions and traffic

Latency, loss and traffic mix vary between runs, so the same test can give a different result

Interaction between multiple communication protocols

A device often runs several protocols at once, and a fault can sit in the interaction between them

Performance bottlenecks under load

Issues that only surface under high traffic volumes are hard to catch without load simulation

Hidden firmware and system behavior

Many failures happen below application level and require deeper system visibility.

Device fleet complexity

Managing multiple devices, firmware versions, and test configurations becomes difficult as systems grow.

Difficulty reproducing real-world scenarios

Production failures are complex to replicate in controlled test environments

Environments

Network environments we work with

Our work includes environments involving:

Wi-Fi (IEEE 802.11)
DSL and broadband communication
Bluetooth and short-range protocols
SFP-based network interfaces
Routers and gateways
Embedded Linux devices
High-performance packet processing using DPDK and TRex
Midair

How Midair tests network hardware

TS Factory does most of the work here. Visao comes in only when a failure points back to the code.

1

Reproduce the scenario

TS Factory

Run the same network scenario across devices, firmware versions, traffic profiles and configurations. Record the exact environment behind every run.

2

Observe the system

Delta

Collect logs, system events and resource data while the scenario runs, so a failed result comes with runtime evidence.

3

Trace the problem back to code

Visao · when needed

When a failure points to firmware or software logic, use static analysis to investigate code-level issues before another run.

4

Keep the investigation together

Midair

Connect the device and firmware configuration, test run, code findings and runtime evidence in one place, then rerun the same conditions after a fix.

Reproduce the exact network failure

Router A + Firmware 2.4.1 + Wi-Fi profile X + Traffic load Y + Configuration Z → failure

After a fix, rerun the same setup and compare the result.

Use cases

Midair is built for teams whose product is the network path itself.

•

Routers and gateways

Validate firmware, connectivity, and system behavior across real network conditions.

•

Connected embedded devices

Embedded devices that rely on WiFi, Bluetooth, or other wireless protocols for operation

•

High-performance networking systems

Platforms requiring DPDK or TRex-level traffic generation and packet processing validation

•

Multi-device and IoT environments

Connected device ecosystems where network stability directly impacts system reliability

•

Latency- and throughput-sensitive systems

Applications where latency, throughput, and packet loss must meet precise specifications

Start your pilot

Pick a plan and start a Midair pilot with your own device, firmware and network environment.