> This page is for Firmware, version 3.2.
> For other versions, use one of these documentation indexes:
> - 4.0 (default): https://docs.ouster.com/sensor-docs/firmware/4.0/llms.txt
> - 3.2: https://docs.ouster.com/sensor-docs/firmware/3.2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ouster.com/sensor-docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ouster.com/sensor-docs/_mcp/server.

# Sensor Networking

> Configure the sensor's own IPv4 addressing, gateway, and static network overrides.

Use this guide to configure the sensor's own network behavior. For host machine setup, see [Host Networking](/sensor-docs/firmware/host-networking).

By default, the sensor requests an IPv4 address with DHCP and also supports link-local addressing. Use DHCP or link-local addressing unless your network requires a fixed sensor address or a default gateway.

## Networking Terminology

**Gateway**
A router address on the same subnet as the sensor static IPv4 address. When configured, the sensor uses the gateway as its default route.

**Static IPv4 Override**
A persistent sensor setting that disables dynamic IPv4 configuration and assigns the sensor a fixed IPv4 address with a subnet prefix, such as `192.0.2.123/24`.

**Multicast TTL**
The Time To Live value placed on multicast UDP packets. A value of `1` keeps packets on the local network segment. Higher values allow multicast packets to traverse multicast routers, if the network is configured to route them.

**T1 Ethernet Speed Override**
A sensor setting for automotive Ethernet models that forces the link speed to `100` Mbps. The default speed is `1000` Mbps.

**MTU Override**
A persistent setting for the maximum transmission unit (MTU) of the sensor's ethernet interface. The default is 1500 bytes.

## Static IPv4 Override

Set a static IPv4 override only when the sensor must use a fixed address. After the override is applied, the sensor resets its network configuration after a short delay and must be reached at the new address.

> **Note**
>
> If the sensor becomes unreachable after setting a static IPv4 override, reconnect using the sensor's link-local address or delete the override from a host that can still reach the sensor.

### Web Interface

1. Open the sensor web interface.
2. Go to **System Configuration**.
3. In **Static IPv4 Network Settings**, enter the **IPv4 Address with Subnet Mask**, such as `192.0.2.123/24`.
4. Optionally enter a **Gateway**, such as `192.0.2.1`.
5. Select **Apply**.
6. Reconnect to the sensor using the new address.

To return the sensor to DHCP/link-local behavior, delete the network override from the same page.

### HTTP API

Get the current [static IPv4 override](/sensor-docs/firmware/api-reference#system):

**Command**

```shell
curl http://os-991234567890.local/api/v1/system/network/ipv4/override
```

**Response**

```json
null
```

Set a [static IPv4 address](/sensor-docs/firmware/api-reference#system) without a gateway:

**Command**

```shell
curl -X PUT http://os-991234567890.local/api/v1/system/network/ipv4/override \
  -H 'Content-Type: application/json' \
  --data '{"addr": "192.0.2.123/24"}'
```

**Response**

```json
"192.0.2.123/24"
```

Set a [static IPv4 address](/sensor-docs/firmware/api-reference#system) with a gateway:

**Command**

```shell
curl -X PUT http://os-991234567890.local/api/v1/system/network/ipv4/override \
  -H 'Content-Type: application/json' \
  --data '{"addr": "192.0.2.123/24", "gateway": "192.0.2.1"}'
```

**Response**

```json
{
  "addr": "192.0.2.123/24",
  "gateway": "192.0.2.1"
}
```

Delete the [static IPv4 override](/sensor-docs/firmware/api-reference#system) and return to DHCP/link-local behavior:

**Command**

```shell
curl -X DELETE http://os-991234567890.local/api/v1/system/network/ipv4/override
```

**Response:** (no output)

> **Note**
>
> The gateway can only be set with a static IPv4 override and must be reachable from the configured subnet. The sensor rejects invalid override addresses, including link-local, multicast, loopback, network, and broadcast addresses.

## UDP Multicast TTL

The `udp_multicast_ttl` configuration parameter controls the multicast TTL for lidar and IMU UDP packets. The default value is `1`. Valid values are integers from `1` to `255`.

Only change this value when sending lidar or IMU UDP data to a multicast destination that must cross multicast routers. Set it with the [`POST /api/v1/sensor/config`](/sensor-docs/firmware/api-reference#sensor-configuration) endpoint.

**Command**

```shell
curl -X POST http://os-991234567890.local/api/v1/sensor/config \
  -H 'Content-Type: application/json' \
  --data '{"udp_multicast_ttl": 2}'
```

**Response:** (no output)

> **Note**
>
> The `udp_multicast_ttl` setting affects lidar and IMU UDP packets. Zone Monitor multicast TTL is configured separately with `udp_multicast_ttl_zm`.

## T1 Ethernet Speed Override

The [`speed_override`](/sensor-docs/firmware/api-reference#system) endpoint is only valid for sensors with automotive Ethernet (T1). Use it only when the link partner is configured to match the selected speed. If the link partner does not match, communication with the sensor can be lost.

Set the T1 Ethernet speed override to `100` Mbps:

**Command**

```shell
curl -X PUT http://os-991234567890.local/api/v1/system/network/speed_override \
  -H 'Content-Type: application/json' \
  --data '100'
```

**Response**

```json
100
```

Reset the T1 Ethernet speed to the default `1000` Mbps with the [`DELETE /api/v1/system/network/speed_override`](/sensor-docs/firmware/api-reference#system) endpoint:

**Command**

```shell
curl -X DELETE http://os-991234567890.local/api/v1/system/network/speed_override
```

**Response:** (no output)

> **Note**
>
> The speed override is not supported on all platforms. Unsupported sensors return an error for this endpoint.

## MTU Override for Ethernet Jumbo Frames

The [`mtu_override`](/sensor-docs/firmware/api-reference/ouster-http-api/system/put-network-mtu-override) endpoint allows users to configure the maximum transmission unit (MTU) of the sensor's ethernet interface to an integer value from 1024 to 9000 bytes. 1500 bytes is the default MTU, and 9000 bytes is standard for jumbo frames.

Set the MTU to `9000` bytes:

**Command**

```shell
curl http://os-991234567890.local/api/v1/system/network/mtu_override \
  --request PUT \
  --header 'Content-Type: application/json' \
  --data '9000'
```

**Response**

```json
9000
```

Reset the MTU to the default `1500` bytes with the [`DELETE /api/v1/system/network/mtu_override`](/sensor-docs/firmware/api-reference/ouster-http-api/system/delete-network-mtu-override) endpoint:

**Command**

```shell
curl -X DELETE http://os-991234567890.local/api/v1/system/network/mtu_override
```

**Response:** (no output)

> **Note**
>
> If the network is not configured to support jumbo frames, enabling an MTU greater than 1500 bytes can lead to sensor connectivity issues. Use this feature with caution.

> **Note**
>
> Lidar UDP packets can exceed 9000 bytes, leading to packet fragmentation. Use the [Columns Per Packet](docs/sensor-features/columns-per-packet) setting to reduce packet size and remove fragmentation altogether.