Forum Discussion
Can't connect to AWS VPN starting this year
I use AWS VPN to connect to my work. There are times when I'm on the road and need to connect to work. I used to be able to just use my T-mobile hotspot from my Mac and work anywhere I had T-mobile c...
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:
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!
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:
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!
