Suppose you're at your desk and you want to access a website like ours. To do this, your computer initiates a request by sending some packets. If you're in an office, those packets often travel through switches and routers on your LAN before they are transferred to the public internet through a router.
Once on the public internet, those packets travel through a bunch of computers. A separate request is made to a series of name servers to translate the DNS name of store.snetit.eu to an IP address. That information is sent back to your browser, which then sends the request, again, through a bunch of computers on the public internet.
Eventually, it reaches the our store infrastructure, which also routes those packets, then grabs a webpage (which is actually a bunch of separate elements), and sends all that back to you.
Eventually, it reaches the our store infrastructure, which also routes those packets, then grabs a webpage (which is actually a bunch of separate elements), and sends all that back to you.
Each internet request usually results in a whole series of communication events between multiple points. The way a VPN works is by encrypting those packets at the originating point, often hiding not only the data, but also the information about your originating IP address. The VPN software on your end then sends those packets to VPN server at some destination point, decrypting that information.
One of the most important issues in understanding the limits of VPNs is understanding where the endpoint of the VPN server resides.
