Conversation
31217ac to
bef44dd
Compare
Closed
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 closes #498 , adding a feature to vpnguin where users can specify a source address for services that expect a particular source ip. We accomplish this by configuring one of the dummy devices on the system with that address and then have the client side of vpnguin bind to that address.
We use the
guest_cmdfeature to stand up the interface if it is not configured.Example usage:
Tested with TCP and UDP services that process the incoming source address, as well as various firmware that we've seen stand up multiple network services.
Note: this PR should be merged after rehosting/vpnguin#19 , with the correct
VPN_VERSIONin the penguin Dockerfile. The currentVPN_VERSIONin this branch is a guess and build will fail for now.