Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Thanks for your answer, but I still don't understand why I need both routes (1st tun0 and 2nd 54.202.18.143). Why can't I use only one? Commented Feb 2, 2018 at 14:20
  • @Vova as I said in my answer, you need a route to the VPN endpoint so that OpenVPN traffic can get to that endpoint, and you appear to want a route through the VPN tunnel for all your other traffic. Commented Feb 2, 2018 at 14:22
  • Which application knows to send packets to that specific IP '54.202.18.143'? Through which interface the browser's traffic is going through? Commented Feb 2, 2018 at 14:44
  • This is a kernel routing table. Applications neither know nor care how their traffic gets to an end-point as long as it gets there. Traffic for 54.202.18.143 goes there outside the VPN. Traffic for anywhere else goes through the VPN and out of the VPN server's end-point to the true destination. Commented Feb 2, 2018 at 15:20