Timeline for Understanding Routing Table with OpenVPN
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2018 at 15:20 | comment | added | Chris Davies | 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. | |
| Feb 2, 2018 at 14:44 | comment | added | Vova | Which application knows to send packets to that specific IP '54.202.18.143'? Through which interface the browser's traffic is going through? | |
| Feb 2, 2018 at 14:22 | comment | added | Chris Davies | @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. | |
| Feb 2, 2018 at 14:20 | comment | added | Vova | 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? | |
| Jan 29, 2018 at 11:08 | history | edited | Chris Davies | CC BY-SA 3.0 |
Fixed a glaring misread of the question detail
|
| Jan 28, 2018 at 22:57 | history | answered | Chris Davies | CC BY-SA 3.0 |