Agent will now fall back to p2p methods if c2 comms fail 3x in a row #262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… cycle through for p2p
…rt to after successful c2 comms
|
Closing to split up into multiple PRs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also fixed capitalization in the listenP2P flag for the sandcat agent command line arg, and you can now also set listenP2P server-side using the HTTP header "listenP2P" with value "true".
Agent will try available c2 comms to server - if it fails 3 times in a row, it'll start round-robin through the available p2p hosts and p2p methods
Server will dynamically include available p2p hostnames at build-time for agent to use, if HTTP header "fetchPeers" is included