github/goreplay
4
0
Fork 0
mirror of https://github.com/buger/goreplay.git synced 2026-10-21 05:22:12 +00:00
Code Issues Releases Wiki Activity

Updated Distributed configuration (markdown)

Leonid Bugaev
2021-08-06 21:16:49 +03:00
parent feb9b86564
commit a4612cb89d
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Distributed-configuration.md
+3 -1
@@ -13,6 +13,8 @@ If you have multiple replay machines you can split traffic among them using `--s
gor --input-raw :80 --split-output --output-tcp replay1.local:28020 --output-tcp replay2.local:28020
```
You can configure amount of connections using by --output-tcp using `--output-tcp-workers` (default 10).
### Encryption
Traffic between `--input-tcp` and `--output-tcp` can be encrypted using TLS protocol. To make it work you need to generate SSL certificate, specify paths to it and key used for generating cert, and enable secure mode.
@@ -24,7 +26,7 @@ openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -subj
Do not forget to replace "localhost" by your domain or IP.
When you configured secure input, enable `--output-tcp-secure` flag for the GoReplay clients, connecting to it.
Use `--output-tcp-skip-verify` to ignore TLS verification.
***
[GoReplay PRO](https://goreplay.com/pro.html) support accurate recording and replaying of tcp sessions, and when `--recognize-tcp-sessions` option is passed, instead of round-robin it will use a smarter algorithm which ensures that same sessions will be sent to the same replay instance.