add option for multicast_ttl value #80
Open
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
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.
As a pytak client administrator I want to set the MULTICAST_TTL value to allow clients to reach the TAK broadcast domain.
At times clients are deployed in virtual machines or containers on an overlay network where TTL=1 only gets to the host. Configuring a
PYTAK_MULTICAST_TTLenvironment variable provides admins an additional option to ease the networking configuration burden for the deployment scenario.Additionally, the socket option was no longer being set for the writer, just the reader (which is unnecessary).