Timeline for VPN - How does the client become a part of the private network?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2016 at 19:11 | history | edited | Ron Maupin♦ | CC BY-SA 3.0 |
added 2 characters in body
|
| Apr 6, 2016 at 19:04 | vote | accept | Jerry Meakin | ||
| Apr 6, 2016 at 18:23 | comment | added | Ron Maupin♦ | Basically, you have a route for the other network pointed to your tunnel endpoint. A tunnel interface looks like any other interface. | |
| Apr 6, 2016 at 18:19 | comment | added | Jerry Meakin | For e.g. if it's a ping command, how does it know that it needs to look for the next hop router for the destination address mentioned in the command? If it's a file share access, how does it know it needs to treat that traffic in the appropriate way to make the access happen? | |
| Apr 6, 2016 at 18:14 | comment | added | Jerry Meakin | Making a lot more sense now. Just a few more gaps in understanding. So far what I've got is: Once a VPN connection is established, a network interface will be setup on the client machine that will be dedicated to carrying over traffic destined for the target network IP range. When traffic needs to be sent via the VPN, the network interface will be used and the VPN tunnel will tunnel the traffic to the target network's VPN gateway. Once it reaches there, how does the VPN gateway decide what needs to be done with the traffic next? | |
| Apr 6, 2016 at 18:06 | comment | added | Ron Maupin♦ | The host initiating the ping would ping the address on the target network. The VPN tunnel would take the ping packets, encapsulate them in the tunnel packet header, and send them to be routed normally. the receiving network would strip off the tunnel headers, and drop the inner packets onto its network. Then, usual network functions, e.g. security, QoS, etc., can be applied to the packets. | |
| Apr 6, 2016 at 18:02 | comment | added | Jerry Meakin | Ah. That makes a bit more sense. So you're saying the inner packets resemble traffic that would normally be doing the rounds in the target network. Meaning if the remote client sends "ping 10.100.50.50" via the VPN tunnel where 10.0.0.0 is the target network, the VPN gateway would execute this ping on behalf of remote client and send back the response? Thereby making the remote client think that it's part of the target network? | |
| Apr 6, 2016 at 17:57 | comment | added | Ron Maupin♦ | The protocol specifications really deal with the outer packet headers of the tunnel. What's carried in the tunnel is normal network traffic. Functionally, a tunnel is just like connecting an ethernet cable between two networks, or a host and a network. The ethernet standard doesn't specify what ethernet carries, e.g. IPv4, IPX, IPv6, etc. | |
| Apr 6, 2016 at 17:54 | comment | added | Jerry Meakin | "The inner packets are usually addressed as if they were on the target network." This is exactly what I'm interested in. I haven't seen anything in the specs of typical VPN protocols like PPTP, L2TP, IPSec, etc that would let you achieve this. Is this feature added on top by different products as this doesn't seem like it's a part of the protocol specification. | |
| Apr 6, 2016 at 17:48 | history | answered | Ron Maupin♦ | CC BY-SA 3.0 |