TRex
trex-tgn.cisco.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What TRex is
TRex is an open-source traffic generator for benchmarking platforms with realistic network traffic. It produces Layer 3–7 traffic in stateless, stateful, and advanced stateful modes. Stateless mode supports multiple streams, packet-field changes, and statistics, latency, and jitter measures by stream or group. Advanced stateful mode emulates Layer 7 traffic over scalable TCP and UDP flows. Its emulation includes ARP, IPv6, ND, MLD, IGMP, ICMP, DOT1X, DHCPv4, DHCPv6, and DNS. TRex provides Python automation APIs and a console interface; stateless functions can also be accessed through JSON-RPC. The manual describes it as a Linux application using DPDK and Linux kernel modules, intended for COTS x86 servers. The site says one server can scale up to 200 Gb/sec. It can run in a virtual machine or Docker for low-performance, low-footprint use without additional hardware, though virtual switches can constrain throughput and virtual-machine latency results are not accurate. TRex is free, but hardware and NIC requirements apply.
Who it suits
TRex suits teams benchmarking network platforms, testing switches, or generating traffic for client, server, production, or routing protocol tests. It is aimed at Linux environments with appropriate hardware and NICs.
Good to know, and what to watch
- Generates stateless, stateful, and advanced stateful traffic.
- Provides Python APIs and a console interface.
- Emulates a broad set of network protocols.
- Can run in a virtual machine or Docker for low-footprint use.
- TRex is a Linux application.
- Hardware and NIC requirements apply.
- Virtual switches can limit throughput.
- Virtual-machine latency results are not accurate.
Plans
Every plan and priceTRex
Free plan
The Club's review
TRex is a free, open-source traffic generator for engineers benchmarking network devices and platforms. It is strongest when realistic, scalable traffic and automation matter more than a turnkey interface. Its broad test modes are compelling, but Linux and hardware requirements make deployment planning part of the choice.
Overview
TRex generates Layer 3–7 traffic in stateless, stateful, and advanced stateful modes. Stateless tests can use multiple streams, modify packet fields, and collect statistics, latency, and jitter by stream or group. Advanced stateful mode emulates Layer 7 traffic over scalable TCP and UDP flows. The site says one server can scale up to 200 Gb/sec, positioning TRex for high-scale benchmarks as well as switch, routing, client/server scale, production, and DDoS traffic tests.
Protocol emulation includes ARP, IPv6, neighbor discovery, MLD, IGMP, ICMP, DOT1X, DHCPv4 and DHCPv6, and DNS. Its broader protocol support also spans LLDP, mDNS, NetFlow/IPFIX, OSPF, RIP, and GTP-U. That breadth lets teams exercise varied network behavior within one traffic-generation tool, though TRex is a specialist benchmark platform rather than a general-purpose network monitor.
Key features
Automation and integration
Python APIs cover stateless, stateful, advanced stateful, emulation, and NDR functions; the stateless API can also be used through JSON-RPC. A console interface offers another way to operate the system, and integration with BIRD supports Linux-based stack configuration. These options suit teams incorporating repeatable traffic scenarios into their workflows, especially those already comfortable with scripting.
Deployment trade-offs
The manual describes TRex as a Linux application using DPDK and interacting with Linux kernel modules, and says it should work on COTS x86 servers. ARM compilation is possible, but ARM is not tested in the regression process. A virtual machine or Docker can provide a low-footprint, low-performance setup without extra hardware, useful for basic evaluation; virtual switches can hold throughput to around 1 MPPS, and virtual-machine latency results are inaccurate. Those limits rule out relying on virtual deployments for high-performance or precise latency benchmarks.
TRexViewer supports live monitoring on Windows only. That restriction matters for teams seeking a graphical monitoring application, even though the traffic generator itself is described as a Linux application. Support resources include the TRex community forum and Cisco DevNet community.
Pricing
TRex costs free under its open-source plan. The free plan includes the Linux application, while hardware and NIC requirements still apply; it is therefore most attractive to teams able to supply and manage compatible infrastructure. There is no paid tier described, so there is no lower-cost plan that trades away capabilities, but the zero price does not remove the operational cost of suitable hardware and setup.
Platforms
The listed platforms are API, Linux, macOS, self-hosted, web, and Windows. In practice, the manual’s Linux and DPDK description is the key deployment constraint; the platform list should not be read as meaning every listed environment can host the traffic generator equally. TRexViewer’s live monitoring application is specifically Windows-only.
Who it's for
TRex is a strong fit for network engineers and test teams that need scalable stateful or stateless traffic, protocol emulation, and programmable benchmarks. Its use cases include high-scale stateful network-device testing, switch and routing tests, client/server scale checks, production testing, and DDoS traffic generation. Teams that need accurate virtual-machine latency results, or that cannot accommodate Linux and hardware requirements, should look elsewhere.
Pros and cons
- Pros: Three traffic modes, including Layer 7 stateful emulation, cover a wide range of benchmark scenarios.
- Pros: Extensive protocol emulation and broad protocol support make it useful for varied network-device tests.
- Pros: Python APIs, JSON-RPC access for stateless automation, and a console support repeatable workflows without a paid plan.
- Cons: Linux, DPDK, and hardware/NIC requirements create a real infrastructure burden despite the free plan.
- Cons: Virtual switches can limit throughput to around 1 MPPS, while virtual-machine latency results are inaccurate.
- Cons: TRexViewer’s live monitoring application is available only on Windows.
Alternatives
Network Testing Software is a useful starting point for comparing tools across the category. Choose PingPlotter instead when monitoring a single connection is the priority: its free plan allows one connection, no remote collection, and 10-minute monitoring history, and it also offers a Professional Edition at $29 a month.
OpenSpeedTest is a better fit for HTML5 network speed testing or embedding a speed-test widget, rather than TRex’s traffic-generation benchmarks. LibreSpeed is another free, self-hosted option when the goal is a speed-test service rather than device benchmarking.
Choose EVE-NG when the need is a network emulation lab; its free tier is capped at 7 nodes per instance and 63 per lab. iPerf2 is a free alternative for readers comparing network testing tools. Tessabyte is a paid alternative with one-user licensing at $39 once, for readers who prefer that licensing model. Cisco pyATS is a free option for network test automation rather than traffic generation. Netpicker is another network-focused option, with a free Foundation plan for unlimited network devices and a single user.
Verdict
Choose TRex if your team needs high-scale, programmable traffic generation across varied protocols and can provide a suitable Linux and hardware environment. Its free, open-source model and broad traffic modes are persuasive for serious benchmarking. Look elsewhere if virtualized latency accuracy or a low-infrastructure speed-test or monitoring tool is the priority.
The verdict
TRex offers multiple traffic-generation modes and automation options for network benchmarking. Its Linux and hardware requirements, along with virtual-environment limits, are important constraints to plan around.
What the maker publishes
- Advanced stateful
- Advanced stateful mode emulates Layer 7 traffic over scalable TCP and UDP flows. source
- Automation
- TRex provides a Python API and a console interface, and its stateless API can be used through JSON-RPC from languages that support it. source
- Automation API
- The documentation provides Python automation APIs for stateless, stateful, advanced stateful, emulation, and NDR functions. source
- Deployment
- The documentation describes running TRex in a virtual machine or Docker for low-performance, low-footprint use without additional hardware. source
- Deployment
- TRex is a Linux application; the documentation also describes running it in Docker or a VirtualBox virtual machine for experimentation. source
- Emulation protocols
- Emulation includes ARP, IPv6, ND, MLD, IGMP, ICMP, DOT1X, DHCPv4, DHCPv6, and DNS. source
- GUI support
- The TRexViewer live monitoring application is supported only on Windows OS. source
- Integration
- The documentation describes an integration with BIRD for Linux based stack configuration. source
- Operating system
- The manual describes TRex as a Linux application that uses DPDK and interacts with Linux kernel modules. source
- Performance
- The site says TRex can scale up to 200 Gb/sec with one server. source
- Platform limit
- The manual says TRex should work on COTS x86 servers; ARM compilation is possible but is not tested in its regression. source
- Platform limit
- The manual says TRex should work on COTS x86 servers and can be compiled for ARM, though ARM is not tested in its regression setup. source
- Protocol emulation
- Its emulation functionality includes ARP, IPv6, ND, MLD, IGMP, ICMP, DOT1X, DHCPv4, DHCPv6, and DNS. source
- Purpose
- TRex is an open source traffic generator for benchmarking platforms with realistic traffic. source
- Purpose
- TRex is an open source traffic generator for benchmarking and testing network devices with realistic traffic. source
- Security
- The opened official pages do not state security certifications or compliance claims. source
- Stateful features
- Advanced Stateful mode supports L7 traffic with scalable TCP and UDP. source
- Stateless features
- Stateless mode supports multiple streams, packet field changes, and per-stream or per-group statistics, latency, and jitter. source
- Stateless features
- Stateless mode supports multiple streams, packet field changes, and per stream or group statistics, latency, and jitter. source
- Support
- The documentation lists a TRex community forum and Cisco DevNet community as support resources. source
- Traffic generation
- TRex generates L3–7 traffic and offers stateful and stateless traffic generation modes. source
- Traffic modes
- It supports stateless, stateful, and advanced stateful traffic generation. source
- Use cases
- The FAQ lists high-scale stateful network-device benchmarks, DDoS traffic generation, switch testing, client and server scale tests, production tests, and routing protocol tests as use cases. source
- Use cases
- The FAQ lists high scale benchmarks, switch testing, large client and server scale tests, production tests, and routing protocol tests as common use cases. source
Checked against the maker's pages on 4 Oct 2026.