Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chain two Algo VPN servers (different ingress/egress point)? #1461

Closed
kilo6eight opened this issue May 31, 2019 · 4 comments
Closed

Chain two Algo VPN servers (different ingress/egress point)? #1461

kilo6eight opened this issue May 31, 2019 · 4 comments

Comments

@kilo6eight
Copy link

kilo6eight commented May 31, 2019

I am trying to figure out how to go about chaining two different Algo VPN servers I have so that my ingress point is separate from my egress point. Simply put,

User --> (ingress) Algo VPN Server Location #1 ---> Algo VPN Server Location #2 (egress) --> internet/website

I also want to ensure that if the ingress server is unable to access egress server that under this scenario no internet should be accessible for any user connected to the VPN chain.

Anyone have a recommendation on how to do this or what I should be researching to find most straight forward solution?

@TC1977
Copy link
Contributor

TC1977 commented May 31, 2019

Is this something like #1047?

@jackivanov
Copy link
Collaborator

and another answer is #1451

@AKarbas
Copy link

AKarbas commented Mar 23, 2020

Any updates/guides/tips on this?

I'm planning to try and figure out the routing needed, but would definitely appreciate any thoughts.

(I'm also following #1451)

@kilo6eight
Copy link
Author

Any updates/guides/tips on this?

I'm planning to try and figure out the routing needed, but would definitely appreciate any thoughts.

(I'm also following #1451)

Nothing but if you are able to come up with a solution please do share

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants