[IMP] Switch from socat to iptables-based transparent TCP proxy#29
Draft
josep-tecnativa wants to merge 2 commits intomasterfrom
Draft
[IMP] Switch from socat to iptables-based transparent TCP proxy#29josep-tecnativa wants to merge 2 commits intomasterfrom
josep-tecnativa wants to merge 2 commits intomasterfrom
Conversation
41c4ec5 to
092aa71
Compare
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
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 PR replaces the per-port socat model with a single asyncio-based
transparent TCP proxy using iptables NAT REDIRECT and SO_ORIGINAL_DST.
The previous implementation spawned one socat process per port, which
introduced scalability and reliability issues (thread/process explosion,
resource consumption, restart complexity, DNS update handling, etc.).
The new design:
By default, all TCP ports are now allowed unless PORT is explicitly set.
Requires CAP_NET_ADMIN.