You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue you're encountering with TCP replay using GoReplay doesn't seem to be related to the version you're using or a limitation of the free version. The command sudo gor --input-tcp :8080 --output-tcp localhost:8081 is correctly structured for capturing and replaying traffic from port 8080 to 8081. Here are a few areas to investigate that might help resolve the issue:
Check GoReplay's output plugin configuration to ensure it's correctly set up to forward traffic to your server on port 8081.
Review network configurations and firewall rules that might be blocking traffic between ports 8080 and 8081.
Look for any error messages or unusual behavior when running the command, as these can provide clues to the underlying issue.
For further troubleshooting, consider consulting the GoReplay documentation or source code, specifically files related to TCP input and output plugins, and command line options (input_tcp.go, settings.go, and version.go).
If the problem persists, providing more details about any errors or the behavior you're observing could be helpful for diagnosing the issue more accurately.
I am trying to replay requests sent to a TCP server but it doesn't seem to be working.
I have a tcp server running on port 8081.
I use the following command to start gor
sudo gor --input-tcp :8080 --output-tcp localhost:8081
the client sends request to port 8080, but nothing seems to work.
Is it only availble in the pro version ?
The text was updated successfully, but these errors were encountered: