> For the complete documentation index, see [llms.txt](https://saptarshi-sarkar.gitbook.io/notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saptarshi-sarkar.gitbook.io/notes/computer-networking/ip-address.md).

# IP Address

Every device which can connect to each other, have their own IP Addresses. It is in the format of " **X.X.X.X** ". Every single "**X**" can have values from *0* to *255.*

When you type [google.com](https://www.google.com/) in the address bar of your browser, it resolves to the IP address of Google.

To get your system's IP Address, run -

1. For **Windows System** :

   ```sh
    ipconfig
   ```

   in the **command prompt**.
2. For **Mac and Linux/Unix Systems** :

   ```
   curl ifconfig.me
   ```

   in the **terminal**.

**Internet Service Provider** (*ISP*) gives you a modem/router which has a global IP Address. The modem will give IP Addresses to each of the device connected to it using the DHCP (Dynamic Host Configuration Protocol). Those IP Addresses are called **Local IP Addresses**.

When we send request (type the website link in the browser address bar) a server (Google server in this case), it can see the **global IP Address** and **not** the *Local IP Address*. The server sends the response and the modem/router decides which device to send back the response, using **NAT (Network Address Translation) Protocol**. **IP Address** decides which *device* to send the data and **Port Number** determines which application requested the data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://saptarshi-sarkar.gitbook.io/notes/computer-networking/ip-address.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.