From a4612cb89dc1bee449010e2db2033d22e1f413bb Mon Sep 17 00:00:00 2001 From: Leonid Bugaev Date: Fri, 6 Aug 2021 21:16:49 +0300 Subject: [PATCH] Updated Distributed configuration (markdown) --- Distributed-configuration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Distributed-configuration.md b/Distributed-configuration.md index 3882b0f..0c4cc7f 100644 --- a/Distributed-configuration.md +++ b/Distributed-configuration.md @@ -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.