# Knowing your CloudBox IP Address

When working with the **CloudBox**, knowing its **Ethernet IP address** is essential for accessing the web interface, configuring settings, and ensuring smooth communication, especially for **TCP socket communication**. This **Ethernet IP address** remains fixed and is the one you’ll use to interact with the CloudBox for timing data and system commands, regardless of whether the device is connected via **WiFi** or **Ethernet**.

In this article, we will explore the different ways to determine the **Ethernet IP address** of your CloudBox in various scenarios.

## 1. **Checking the WiFi Access Point Name**

When the CloudBox is operating in **WiFi Access Point mode**, it generates its own access point with an SSID (network name) that directly includes its IP address. This makes it one of the easiest methods to identify the CloudBox IP.

The format of the SSID is:

```bash
CLBX_{IP_ADDRESS}
```

For example, if the CloudBox IP address is `192.168.1.10`, the WiFi access point name will be `CLBX_192_168_1_10`. Simply by looking at the network name, you can immediately know the current IP address of the CloudBox.

**Steps:**

1. Open your device’s **WiFi settings**.
2. Look for the WiFi network named `CLBX_{IP_ADDRESS}`.
3. The IP address will be embedded in the SSID (e.g., `CLBX_192_168_1_10`).

This is particularly useful when using the CloudBox in standalone mode, where it is generating its own WiFi access point.

## 2. **Checking the Router’s Device List (For External WiFi Networks)**

When the CloudBox is connected to an **external WiFi network**, the device will receive an IP address for the **WiFi interface** dynamically via **DHCP** from the router. However, this WiFi IP is not the one used for TCP socket communication. The IP address you need for communication is the **fixed Ethernet IP address**, which stays constant and is always used for TCP socket connections.

To find the **Ethernet IP address** in this case, you’ll still use the router’s device list, but you need to identify the **fixed Ethernet IP** rather than the dynamically assigned WiFi IP.

**Steps:**

1. Log into your router’s admin interface (typically accessed via `192.168.1.1` or a similar IP address).
2. Navigate to the **Connected Devices** or **Clients** section.
3. Find the CloudBox in the device list. The router will show multiple IP addresses for the CloudBox:
   * One IP for the **WiFi** interface (assigned dynamically via DHCP).
   * One **fixed IP address** for the **Ethernet port**.
4. Identify the **fixed Ethernet IP address**, which is the one you’ll use for TCP socket communication (e.g., `192.168.1.10`).

This method is useful when the CloudBox is connected to a larger network via WiFi but still uses the **Ethernet IP** for TCP communication.

## **3. Using the CloudBox Interface Directly**

If you’re already connected to the CloudBox via **Ethernet** or the **WiFi Access Point**, you can directly access the **Network Configuration** section of the CloudBox interface to view the current IP addresses.

**Steps:**

1. Open a web browser and go to the CloudBox’s interface using`cloudbox.local`
2. In the **Network Configuration** section, the **Ethernet IP** **address** will be displayed. 
3. You can also modify the Ethernet IP here if needed.

This method is useful for verifying or changing network settings when you already have access to the interface.

## 4. **Using the Ping Command**

If you are on the same network as the CloudBox, you can use the **ping** command to locate the device.

**Steps:**

1. Open the **Command Prompt** (Windows) or **Terminal** (Mac/Linux).
2. Type the following command:

   ```bash
   ping cloudbox.local
   ```
3. The system will return the CloudBox’s IP address if it’s reachable on the network, but this may return the **WiFi IP** instead of the **Ethernet IP**.

This method works best when there is only one CloudBox on the network and you want to verify connectivity.

## Important Considerations

* **Ethernet IP Address for TCP Communication**: The **Ethernet IP address** is the fixed IP address you should always use for **TCP socket communication**, regardless of whether the CloudBox is connected via **WiFi** or **Ethernet**.
* **WiFi IP Address (For External Networks)**: When the CloudBox is connected to an external WiFi network, the **WiFi IP address** is dynamically assigned via **DHCP**, but this is not the IP you need for direct communication. Always look for the **fixed Ethernet IP** for TCP communication.
* **Multiple CloudBox Devices on the Same Network**: If you are working with multiple CloudBox devices on the same network, ensure that each device has a **unique Ethernet IP address** to avoid conflicts. In such cases, accessing by IP is more reliable than using `cloudbox.local`.

## Summary

When working with the CloudBox, the most critical IP address to know is the **Ethernet IP address**, as this is the one used for **TCP socket communication**. Whether you’re connected via **Ethernet** or **WiFi**, the Ethernet IP remains constant, ensuring reliable connectivity for timing data and commands. Use the **WiFi Access Point name**, **router’s device list**, or directly check the **Network Configuration** in the CloudBox interface to find this address.