Open
Conversation
Using TCP6-LISTEN instead of just TCP-LISTEN will make `socat` bind to `::` and `0.0.0.0`
4 tasks
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.
Using TCP6-LISTEN instead of just TCP-LISTEN will make
socatbind to::and0.0.0.0.This simple change allows IPV6-only, IPv4-only or dual-stack connectivity for the client side, which is an improvement over the current situation.
Since
mail-api.proton.medoes not provide an AAAA record, the container will still need an IPv4 address to allow connectivity to ProtonMail API.