> For the complete documentation index, see [llms.txt](https://mapir.gitbook.io/daq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mapir.gitbook.io/daq/daq-e/network-setup.md).

# Network Setup

The DAQ-E is an Ethernet (IPv4) device. This page explains how it appears on your network and the options available; the exact commands to change these settings live in the Chloros Manual.

<figure><img src="/files/lFuvN19YjoAXC39ZSotH" alt=""><figcaption><p>A single PoE Ethernet cable passes through the waterproof gland to carry both power and data</p></figcaption></figure>

## IP Addressing

Out of the box the DAQ-E uses **automatic** addressing — DHCP with link-local fallback — so it will obtain an address on most networks without any configuration. For fixed installations you can assign a **static IP** (address, subnet mask, gateway) so the device is always reachable at a known address.

## Discovery

The DAQ-E advertises itself over **mDNS** (service type `_daq-e._tcp`), so Chloros can find it automatically without you knowing its IP address. Each device has a hostname of the form `daq-e-<id>.local` (for example `daq-e-def330.local`). You can give each unit a friendly name to make fleets easy to identify.

{% hint style="warning" %}
mDNS does not cross routers. The computer running Chloros must be on the same local network (broadcast domain) as the DAQ-E. If discovery fails, you can also reach the device directly by its IP address or `.local` hostname.
{% endhint %}

## Streaming Modes

The DAQ-E offers two ways to deliver its spectral data:

* **Multicast (default)** — the DAQ-E broadcasts each measurement to a multicast group on the network. Any number of consumers on the same network can receive the same stream at once, and each datagram is CRC-validated. This is the best choice for permanent installations and for sharing one sensor with several applications.
* **Raw** — a single client connects directly to the device over TCP. This stream is byte-compatible with the DAQ-U, and access is exclusive (one client at a time).

## Auto-Stream at Boot

For unattended installations, the DAQ-E can be set to begin streaming automatically as soon as it powers on, so it starts sending data without a client having to initiate the connection.

## Firmware Updates (OTA)

DAQ-E firmware can be updated over the network (OTA). Updates are protected by a password, which you can change from its default.

## Firewall & Multi-NIC Notes

{% hint style="info" %}
On **Windows**, the first time Chloros listens for the DAQ-E you will see a Windows Defender Firewall prompt — accept it. The DAQ-E and time sync use multicast traffic on **UDP 5002** (sensor data), **UDP 5353** (mDNS), and **UDP 319/320** (PTP). On **Linux** this is silent.

On computers with more than one network adapter, bind Chloros to the adapter that is on the DAQ-E's network so multicast discovery uses the correct interface.
{% endhint %}

{% hint style="info" %}
For the exact commands to set a static IP, rename a unit, enable auto-stream, change the OTA password, reboot, factory-reset, and perform a firmware update, see the Chloros Manual at [docs.chloros.com](https://docs.chloros.com) *(link coming soon)*.
{% endhint %}