This system is useful for CI/CD and other Automated testing, as well as personal
test beds. It is designed to be fully functional as a remote access test system. This
test bed includes an RF chamber, powerful 6-radio + 10G LANforge WiFi test system,
remote power switch, usb camera, and optional external control system for orchestrating
tests across multiple systems.
LANforge test system acts as WiFi stations and upstream server for traffic generation.
LANforge may act as NAT router for DUT: DUT connects to eth2 and gets DHCP, eth3 on LANforge
performs NAT and connects to the upstream network (Internet).
Serial console ports on DUT and LANforge are brought to outside control node. Or optionally,
DUT serial console may connect to LANforge and then no external control node is needed.
Dataplane: Throughput over different packet sizes, wifi modes, NSS and more.
Capacity: Throughput over different numbers of WiFi stations.
Stability: Throughput and stability over longer time, with UDP, TCP, HTTP, VOIP traffic mix
and optional station reconnects while under load.
Includes these Building Blocks
LANforge Multi station Emulation and Traffic Generation Hardware – Suggested
6 wave-2 radios (3x 2.4GHz, 3x 5GHz NICs), 2 10gE ports. More affordable options
CT820a-Medium RF Chamber.
Remote access power switch.
20db fixed attenuator for each LANforge SMA port.
Optional Controller system (1U rackmount server or similar).
Scripts to poll build tools to find new images (Test Orchestrator) and create historical reports
from multiple test-bed runs.
Scripts to handle tests created by the Test Orchestrator (Test Bed Controller).
LANforge WiFi software for test creation and execution, traffic generation and more.
Supports automated as well as manual testing.
PASS/FAIL results table for many tests.
Key Performance Indicator CSV data for many test cases. May be used to graph historical performance over different builds.
Detailed per test measurements, pdf reports and graphs.
Approxmiate System Pricing
Mid-level system: $40k
High-end system: $65k
Lead Times: Most LANforge systems can generally be shipped within a few weeks
after receiving customer PO. RF chambers may need more lead time.
Illustrated lights-out chamber setup guide
Internal chamber setup.
Configure remote power switch for DHCP and connect to inside power in the RF chamber. Use Ethernet cable to connect
the power switch to the chamber wall connector 1. Record the IP address of the power switch.
Connect LANforge management Ethernet port to chamber wall connector 2.
Connect LANforge uplink Ethernet port (eth3 usually) to chamber wall connector 3.
Connect DUT serial port to USB hub.
Connect LANforge serial port to USB hub.
Connect USB hub cable to RF chamber wall connector.
Connect DUT WAN Ethernet port to LANforge port eth2. This specific configuration assumes
that the DUT AP is NOT acting as a router or providing its own DHCP server.
Connect 20-db or similar fixed-attenuators to the SMA ports on the LANforge (or optionally, on DUT).
This helps keep the RF signal from being too strong, considering the LANforge stations and DUT are just
a few inches apart. Connect SMA antennas to the attenuators.
Plug in LED light, LANforge system, powered USB hub and DUT to the remote power switch.
External chamber setup.
Connect USB port to controller will connect to provide serial-console access to DUT and LANforge.
Connect RF Ethernet ports 1 and 2 to lab network.
Connect RF Ethernet ports 3 to Internet network (or lab network in simpler setups) DUT will use this
to access the Internet and/or cloud-controllers.
Connect AC power cord from RF chamber to wall socket.
Network configuration notes.
LANforge management port should have a DHCP address reserved for it so that it always gets
the same well-known IP address.
LANforge port eth3 must use a staticly configured IP address, configured from within the LANforge tool.
WiFi station IP addresses will be given out by LANforge port eth2, so lab network does not need to care about
serving DHCP to the WiFi stations. NAT on LANforge port eth3 will make sure lab network does not conflict with
WiFi station addressing.