# Network Configuration The **CloudBox** offers flexible network configuration options, allowing users to connect to the system through **Ethernet**, **WiFi**, or **4G**. The most common and reliable method for communication with the CloudBox is through its **Ethernet IP address**, especially for **TCP socket connections**. In this article, we’ll dive deeper into the details of configuring and understanding the CloudBox network setup, reserved IP ranges, subnets, and available ports. ## Ethernet IP Configuration The **Ethernet IP address** on the CloudBox is a **fixed IP address** that users can configure in the **Network Configuration** section of the CloudBox interface. This fixed IP address ensures that the CloudBox can be accessed consistently, without the IP changing as it might with a DHCP-assigned address. By default, the CloudBox uses port **8080** for **TCP socket communication**. Users can open a TCP client to communicate with the CloudBox at its Ethernet IP and port **8080**, or a custom port if configured. **How to Configure the Ethernet IP Address:** 1. Navigate to the **Network Configuration** section in the CloudBox interface. 2. Enter the desired **Ethernet IP address**, **port**, and **subnet**. 3. Save the changes, and the CloudBox will restart to apply the new configuration. ## Gateway Configuration The **Gateway** setting in the Network Configuration determines how the CloudBox accesses the wider internet when connected via Ethernet. * If your CloudBox is connected **directly to a local device** (such as a laptop) or is only being used for **local LAN communication**, you can leave the Gateway field empty. The CloudBox will still be fully accessible at its fixed IP address for timing operations. * If your CloudBox is connected to a **router or switch with internet access**, configuring the Gateway allows the CloudBox to reach external services such as: * The **Cloud Timing Service** (for transmitting passings). * **NTP servers** (for precise date/time synchronization). * **Firmware update servers**. **Example**\ If your router has the IP address `192.168.1.1`, set this as the Gateway in the CloudBox configuration. The CloudBox will then use this router to access the internet while keeping its fixed IP (e.g., `192.168.1.10`). **Important Notes** * Configuring the Gateway requires a reboot of the CloudBox. * The Gateway is only needed for internet connectivity. For local-only setups (e.g., timing with no cloud or internet dependency), it can remain unset. * If multiple CloudBox units are connected in the same network, each one should share the same Gateway (router address) but must have **unique fixed IP addresses**. ## Reserved IP Ranges When configuring your CloudBox, it’s essential to avoid assigning an IP address that falls within reserved ranges. These ranges are used for special purposes (such as internal network use, multicast, or reserved addresses) and should not be assigned to your CloudBox. * **Loopback**: * `127.0.0.0` to `127.255.255.255` * Used for internal device communication (loopback). * **Reader IP Address Range**: * `10.0.0.0` to `10.255.255.255` * Reserved for connecting to RFID readers. Make sure the RFID reader is on the **10.0.0.2** address. * **Link-Local**: * `169.254.0.0` to `169.254.255.255` * Used for self-assigned addresses (automatic IP address assignment when no DHCP server is available). * **Multicast**: * `224.0.0.0` to `239.255.255.255` * Used for multicast groups, typically for media or data streaming applications. * **Reserved for Future Use**: * `240.0.0.0` to `255.255.255.254` * Reserved for future applications. * **Broadcast**: * `255.255.255.255` * Used for network-wide broadcasting. Be sure to configure the CloudBox with an IP address that doesn’t conflict with these ranges to ensure smooth network operations. ## Available Subnets When configuring your CloudBox, you can choose from different subnet masks depending on the size of your network. The subnet defines the size of the network by specifying how many devices can be connected within that network. * **255.0.0.0 (/8)**: Large networks with many devices. * **255.255.0.0 (/16)**: Medium-sized networks. * **255.255.255.0 (/24)**: Small networks with up to 254 devices. **Example:** If you are setting the CloudBox on an IP range of `192.168.1.x` and you want to limit the network to 254 devices, you would use the **255.255.255.0** subnet. ## Available Ports The CloudBox offers flexibility when choosing the port number for TCP communication. However, there are a few reserved ports that should not be used. * The CloudBox supports port numbers between **1024** and **65535**. * **Reserved Ports**: * **Port 2999**: Reserved for backup file downloads. * **Port 6379**: Reserved for internal system use. * **Port 5000**: Reserved for internal system use. When setting up TCP connections or any other network services, make sure to avoid these reserved ports. ## Summary The CloudBox provides robust network configuration options, allowing users to connect via **Ethernet**, **WiFi**, or **4G**. With its **fixed Ethernet IP address**, the CloudBox ensures consistent access for **TCP socket communication**. By understanding reserved IP ranges, available subnets, and port numbers, users can effectively configure their CloudBox for seamless network integration. To ensure your CloudBox operates smoothly: * Configure the **Ethernet IP address** appropriately using available subnets. * Avoid using **reserved IP addresses** and **reserved ports** for system integrity. * Use the correct **port (8080)** for TCP communication or customize as needed. By following these guidelines, you’ll ensure your CloudBox is ready for network operations, providing reliable communication for race timing and other system tasks. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.runonrufus.com/rufus-cloudbox/advanced-operations/network-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.