Support for TCP connection #11
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This patch will add support for TCP (ip4 or ipv6) connections from subagent to agent in addition to unix sockets.
A tcp connection can be initiated by passing
tcp:<ipaddress>:portas socket-path to the constructor of theAgent.This is the same convention as using to
snmpd.confto specifyagentXSocket.Passing a path to a unix socket (eg.
/var/agentx/master) works as before. You can also useunix:/var/agentx/master.Very few changes are needed to do this, because tcp sockets behave similar to unix sockets. I also tried UDP sockets, but that requires more changes in the
Networkclass.