By using AWS re:Post, you agree to the Terms of Use

VPN Client Endpoint - losing internet access even with split tunnel enabled


Hi, I have been working with aws vpn client for some time and I have enough understanding of how it works and its config. The only thing Im having issues with right now is even when I have the split tunnel feature enabled, I lose internet access from my computer, at home. If I understand this correctly the whole idea behind the split tunnel is to make sure AWS traffic is only what goes through the vpn tunnel, to avoid extra charges,...etc.

I have older endpoints created previously and are working as expected, both at home and at the office. All clients have the same configs with the CIDR being the only difference, and the new one was created using AWS CDK. My local routing seems ok, but when trying to access "" for example I get DNS resolution error in my browser, simply nothing works.

Following is my routing when connected to the vpn client im having issues with. I use for my vpc.

Destination        Gateway            Flags           Netif Expire
default             UGScg             en0       
10/24              link#15            UCS               en0      !        link#15            UCS               en0      !           f4:c1:14:8e:ad:16  UHLWIir           en0   1190         a4:93:3f:60:53:84  UHLWI             en0    668         f8:28:19:3d:bb:b6  UHLWI             en0      !      link#15            UCS               en0      !         e:bf:67:db:69:3    UHLWI             en0      !         ff:ff:ff:ff:ff:ff  UHLWbI            en0      !
127                UCS               lo0          UH                lo0       
169.254            link#15            UCS               en0      !
192.168.0/16      UGSc            utun3       
192.168.100/27      UGSc            utun3      UH              utun3       

2 Answers

Your route table looks fine but I think the problem here is DNS. What is your DNS server set to?

You can check that the split tunnel is working correctly by doing a ping to a working external IP address. That's easy to find - when the VPN isn't running do ping and take note of the IP address. With the VPN running do ping <IP address> and see if you get a response. If you do then DNS is definitely the issue.

Make sure that you can reach your DNS server when on the VPN. If the DNS server is in the VPC then it needs to be able to resolve IP addresses and return responses to your computer via the VPN tunnel.

profile picture
answered a month ago
profile picture
reviewed a month ago
  • Thank you! I was able to resolve the issue. The idea behind using split tunnel for me is to avoid having non-aws traffic going through the vpn tunnel, as I have a private subnet with no internet access. I wanted to take advantage of the endpoint route table copied on the client side. Note that I have 3 different vpn client endpoints with split tunnel and they all work. After reviewing my work and some trial and error apparently having the client cidr overlap with the VPC, where the client is configured will cause this issue. Overlap documented but didn't realize will cause such issue.

  • I'm having this exact issue. In order to get internal DNS resolution to work, I utilized AWS Route53 Resolver. In configuring the Client VPN Endpoint, I specified the IP addresses of the AWS Resolver Inbound Endpoint. That enabled me to resolve internal hostnames while on the VPN. However, I am now not able to resolve external DNS queries. I have split tunnel enabled. I can resolve the issue by adding an Authorization Rule on the VPN Client to allow traffic to, but I don't want to do that for security reasons, and don't think I should have to with the split tunnel solution. Do you have any advice?

  • Honestly I think AWS support need to look into this issue and do enough testing to understand the reason behind such an intermittent problem. Today suddenly everything is working fine. I was doing some testing with different vpn endpoints, and I haven't figured out the reason this is happening, yet. I would say first thing is avoid the entry, since it will copy the client route table to your local machine, as with that you might have issues trying to figure out whats going on. I had to delete my answer below as now the CIDR overlap is no longer to be the issue I guess.


When you enable split-tunnel mode, all the routes in the Client VPN endpoint's route table are added to the client's route table when the VPN connection is established. This operation is different from the default behavior, which overwrites the client's route table with the entry to route all traffic over the VPN.

I am assuming the above route table is on your on-premise end. It is not recommended to add a route to the Client VPN endpoint's route table when using split-tunnel mode.

Can you confirm if you have added the same ? If yes, can you remove and try ?

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions