Forum Discussion
Can't connect to AWS VPN starting this year
- Hace 7 meses
I'm able to work around this (or a similar) issue by tethering via USB from my Pixel while connecting with the AWS VPN client. I would get this error:
The VPN connection is being terminated due to a discrepancy between the IP address of the connected server and the expected VPN server IP. Please contact your network administrator for assistance in resolving this issue.
Presumably from this requirement which is relatively new:
The Client VPN service requires that the IP address the client is connected to matches the IP that the Client VPN endpoint's DNS name resolves to. In other words, if you set a custom DNS record for the Client VPN endpoint, then forward the traffic to the actual IP address the endpoint's DNS name resolves to, this setup will not work using recent AWS-provided clients. This rule was added to mitigate a server IP attack as described here: TunnelCrack.
Fuente: https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/what-is-best-practices.html
HTH!
Related to connecting to AWS EC2 Boxes?
I've been trying to ssh into my EC2 boxes. I can get to the machines when I'm on on my work's VPN, but when I'm NOT on the work VPN, it times out!
I haven't messed much at all with my T-Mobile Hotspot. It just sits there on top of my bookshelf happily routing packets (better than Frontier ever did).
I’m using:
ssh -vvv ...
and it times out. No evidence of anything but that it's trying to connect. I've tried on multiple machines.
I feel like maybe it's related. Anybody have any ideas?
Contenido relacionado
- Hace 3 años
- Hace 7 años
- Hace 2 años
- Hace 3 años
- Hace 2 años