- Newest
- Most votes
- Most comments
Hi,
It looks like in AWS VPC-->ClientVPN endpoint -->Route table , Please make sure you do not have route added for 0.0.0.0.
By looking at the route table, I could see split tunnel is enabled thats reason i see you have two routes received for 10.10.0.0 /16 and also 0.0.0.0/0 points to tunnel ip .
It is not recommended to add a 0.0.0.0/0 route to the Client VPN endpoint's route table when using split-tunnel mode.
When split-tunneling is enabled on a Client VPN endpoint, only routes that are configured on the endpoint route table will be pushed to connecting clients. Any traffic destined for addresses that do not match these routes will be routed directly to the internet rather than through the VPN tunnel.
https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/split-tunnel-vpn.html
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
Have you managed to get this resolved at all ? I have been working with the vpn client for some time and created multiple of them and all working fine. Once I switched to work from home i created a new one for testing and as soon as its up and running I can no longer access the internet, even though I have split tunnel enabled. Older client configs in other VPCs are still working fine and I can no longer see why this new one is acting this way.