Support & community

Getting help

Before asking, please check the resources that most often already hold the answer:

• This user guide and the FAQ.
• The man pages (man tcpreplay, tcpreplay --help).
• The GitHub Discussions and issue tracker — someone may have hit the same thing.
• The tcpreplay-users mailing list archives.

Still stuck? Ask on GitHub Discussions or the tcpreplay-users mailing list.

Reporting a good bug report

The quality of a bug report largely determines how fast it can be resolved. Include enough for someone to reproduce it.

Build / compile problemsRuntime problems

• The Tcpreplay version you're compiling.
• Your platform (OS, version, architecture).
• The contents of config.status.
• The output of configure and make.

• Version information (tcpreplay --version).
• The exact command line — options and arguments.
• Your platform (OS, version, architecture).
• The make/model of the NIC(s) and driver version, if relevant.
• The error message and a description of what happened vs. what you expected.

File it on the issue tracker.

Security issues go through a private channel

Do not report a security vulnerability in a public issue. Use GitHub's private security-advisory process — see SECURITY.md in the repository.

Contributing

Contributions — bug fixes, features, docs — are welcome:

• Discuss first? Design questions and proposals fit GitHub Discussions.
• Ready to code? See Contributing for the fork → branch → pull-request workflow and the build/test setup.
• Digging into internals? The Developers section has the library and plugin guides.

Developers can also follow the tcpreplay-devel mailing list; how-to questions belong on tcpreplay-users instead.

The mailing lists

List	For
tcpreplay-users	Usage questions and help.
tcpreplay-devel	Development discussion.