Avoid routing Private Google Access traffic over v2rayA #1559
Conversation
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
We have some on-prem hosts with routes configured for Private Google Access. Unfortunately v2rayA interferes with the traffic by trying to proxy it then sends it over to the public Google endpoints. Using v2ray routing doesn't seem to help, because Private Google Access requires traffic to be sent to the private virtual IPs with Host header or SNI pointing to the public service names, and v2ray resolves them to the public IP addresses corresponding to the service names used. Ref: https://cloud.google.com/vpc/docs/configure-private-google-access-hybrid
|
I know this change is a bit invasive, but is there a way to have v2ray route based on SO_ORIGINAL_DST and ignore whatever specified in Host header or SNI (I actually just care about "redirect" mode, at this time)? The current behavior is tested as having |
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.
We have some on-prem hosts with routes configured for Private Google Access. Unfortunately v2rayA interferes with the traffic by trying to proxy it then sends it over to the public Google endpoints. Using v2ray routing doesn't seem to help, because Private Google Access requires traffic to be sent to the private virtual IPs with Host header and SNI pointing to the public service names, and v2ray resolves them to the public IP addresses corresponding to the service names used.
Ref: https://cloud.google.com/vpc/docs/configure-private-google-access-hybrid