Step 2: What’s Happening on your Device (with a normal connection)

In this scenario, you are requesting a webpage with your browser. You click on a link and wait for the page to load. Meanwhile, your request is “routed” to the web-server that “hosts” the page you’ve requested. The server then sends you the content of that webpage, and your browser displays it for you.

Internet Protocol (IP) Addresses

Each Internet-connected device has a public IP address, assigned by its ISP, that it uses to send and receive data. This includes personal computers, Internet-connected smartphones, printers, game consoles, web-pages and Online services such as email providers and social networking sites.
•The ISPs that most people use hand out new public IP addresses from time to time (but they also maintain records of who had which address at any given moment).
•The ISPs that most *servers *use, on the other hand, assign public IP addresses for longer periods, which makes them easier to find.
That said, you will rarely request content using a server’s IP address directly. Instead, your Web browser will typically ask a domain name service (DNS) server to look up the domain name of the URL in the link you clicked (say, level-up.cc) and translate it into a public IP address (say, 88.80.189.190). Your browser will then request the specific content you want (say, “leading-training/training-curriculum/input/circumvention”) from the server at that public IP address. Local Area Networks & Local IP Addresses

Most of the devices you will use directly, such as laptops and smartphones, have local IP addresses that are unreachable from the public Internet. Devices on the same Local Area Network (LAN) frequently share the same public IP address.
•The router (sometimes called a gateway or an access point) in your home (or office, school, internet cafe, etc.) hands out local IP addresses, sends your devices’ requests off to the Internet, and then manages the process of directing each response to the appropriate device.
•Your local IP addresses is a little bit like your name, as it appears on the first line of an envelope that someone has mailed to you. It is the rest of the address that allows the postal service to deliver your envelope to the right house. (After all, your delivery person wouldn’t know what to do with a letter addressed simply to “Alice.”)
Assuming you share a home with other people, however, your name becomes important once the envelope arrives at your door.

Your Internet Traffic
Depending on where you live and what type of Internet connection you have, both your request and the corresponding response will pass through a number of different computers along their respective “routes.”
Internet traffic makes its way from one IP address to another as a series of “packets,” which are small units of data that travel according to a physical path determined by the various routers they encounter along the way.
Different packets may travel along different routes even if they are part of the same request, response or data submission (such as a when you submit a Web search or an email message).

Routing
These routes will vary depending on where you live and where the webpage you’re requesting is located, among other factors. Your request will typically pass through your local router, then on to your ISP. After that, things get a bit complicated.
Your local ISP can talk to other ISPs, any one of which might provide Internet connectivity for the server hosting the webpage at the IP address you have requested.
Most likely, your request will pass through several ISP networks before reaching its destination. And, if that server is located outside of your country, then your request might even pass through an undersea cable to a large ISP in another country. It might then be routed through a number of smaller ISPs before arriving at the IP address you requested.
Assuming all goes according to plan, the server at that IP address will then answer your request by sending the specified webpage back to your public IP address (by way of one or more equally complex paths).
When it arrives at your local router, it will be forwarded to your local IP address, then (finally) displayed in your Web browser.