If you're experiencing issues with your AWS services, then please refer to the AWS Health Dashboard. You can find the overall status of ongoing outages, the health of AWS services, and the latest updates from AWS engineers.
Losing internet access with split tunnel on in aws client VPN
I have client VPN set up with split tunnel enabled and have just one route i.e. to target subnet in a VPC. I have gone throug other similar question on AWS re:Post and have made sure that I do not have 0.0.0.0 route in Routes associated with Cvpn endpoint. Also I am not supplying and DNS servers at the moment.
I can see why I am loosing the internet access which is because a route entry is being pushed down to my local route table (i am using Linux Mint 21 and default openvpn client inbuilt into it to connect) for 0.0.0.0 -> 10.54.0.161 which does not make sense. That route entry should not be pushed by Cvpn to my host machine as I have split tunnel enabled.
Not sure what am I doing wrong.
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hope this helps others having issues with CVPN on debian clients.
I had got in touch with AWS Business support about this and they have suggested a workaround in form of using the AWS Client VPN GUI that is available for Linux. When connecting through that software, the default route does not get added but if you use the default open vpn client that gets shipped with linux mint that the issue pops up again.
This should not be happening but they aren't sure about when AWS will prioritize fixing this. So the current solution is using the AWS CVPN GUI. Also the GUI is not supported for newer ubuntu versions but you will need to manually add a few dependencies and then it does work.
Thanks
In case it helps anyone in the future: we fixed this on our end after an hour of research using this extra line of configuration in the ovpn file:
pull-filter ignore redirect-gateway
I had the same problem on macOS, to fix that I used the following two commands to tackle the overwritten gateway:
- sudo route delete <DESTINATION>
- sudo route add <DESTINATION> <ADDR_GATEWAY_ROUTER>
Some guys of our team have the same issue. The weird thing is we all have MacOS and the same AWS VPN Client version. And only a few guys have the same issue. Please you have to fix that. We cannot work properly!!!
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
pull-filter ignore redirect-gateway 100% worked for me. I use fedora as my main OS. AWS only has a vpn client for Ubuntu. Plus, we should NOT have to resort to ONLY being able to use the AWS client. That is dumb. So, add "pull-filter ignore redirect-gateway" to the config, and my split tunneling works now.
Thank you Niels