-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Internal Gateway Detection not working, preventing connection #377
Comments
This could be an enhancement from my understanding. Currently, it will try to connect to the last used gateway when connecting. |
I don't want to steal this thread, but I'm also curious about the internal host detection mechanism integration, is it supported at all? Whenever I perform the connection and auth to the portal, I only get internal gateways in the response (of course not working from outside). I see no trace of internal host detection being performed...
|
I am having the exact same issue, thus I can not connect to the VPN from home. I get a list of internal gateways which do not resolve from the outside. There should be a list of external gateways.
|
I'm hitting the same issue
|
The client doesn't support internal host detection. It could be a behavior of the VPN portal server if you see the internal gateways when using the internal network. I suppose it will return the outer gateways if you use the outside network. @swwolf @agriffit79 Do your company has multiple portal addresses? Does the official client for Windows or macOS work with the same portal address? |
My company only has one portal address and it works with the official client for Linux. That client shows a different list of Gateways (which are publicly resolvable). |
Reopen this issue since the changes in #384 haven't been released yet. |
Hi guys, the internal host detection has been released in 2.3.4, you could upgrade the client and give it a try. Thanks. |
yes, I can confirm it works for me now. Thanks. |
Closing it for now, feel free to reopen if it still has the issue. |
Describe the bug
When connecting to a GP server wich has a internal and external gateway, and we are on the outside (where the DNS for the internal zone won't resolve) the client tries to connect to the internal one (which will fail) instead of the external one
Expected behavior
When on the outside, connect to the external GW, when on the inside connect to the internal GW
This is, when the PTR record for the internal detection resolves it should connect to gp-internal.xxxx.pt, when it does not resolve it should connect to gp.xxxx.pt
Logs
Environment:
The text was updated successfully, but these errors were encountered: