Settings: Add option to lock binding to IPv4 #559
Merged
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
WebsocketPP defaults to binding to an IPv6 interface. Since IPv6 is broken on so many networks, this adds an option to force WebsocketPP to use the default IPv4 interface to bind to.
Palakis
approved these changes
Sep 15, 2020
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.
Description
This adds an option to force WebsocketPP to use the default IPv4 interface to bind to.
Motivation and Context
WebsocketPP defaults to binding to an IPv6 interface. Since IPv6 is broken on so many networks, there is a need to give users the option to force disable it. This change does not affect the default behavior of obs-websocket.
Fixes #531
How Has This Been Tested?
Tested OS(s): Ubuntu 20.04
Types of changes
Checklist: