> 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.

# macOS

> Host network setup for connecting to an Ouster sensor on macOS.

Tested on macOS 10.15.4. The sensor hostname is `os-991234567890.local` (serial number on the sticker on top of the sensor).

## Connecting the Sensor

1. Connect the sensor to an available Ethernet port on the host machine or router.
2. The sensor automatically obtains an IP address via link-local or DHCP, depending on network configuration.

> **Note**
>
> It can take up to 60 seconds to obtain an IP address after initial power-up.

## The Sensor Homepage

1. Enter `http://os-991234567890.local/` in your browser's address bar to open the sensor homepage.

> **Note**
>
> If the sensor homepage does not load, follow the steps in [Determining the IPv4 Address of the Sensor](#determining-the-ipv4-address-of-the-sensor) to verify the sensor has a valid IP address.

## Determining the IPv4 Address of the Sensor

1. Open **Terminal** (**Cmd+Space**, type `Terminal`, press Enter).

2. Ping the sensor to find its IPv4 address:

**Command**

```shell
ping -c3 [sensor_hostname]
```

**Example**

```shell
Mac-Computer:~ username$ ping -c3 os-991234567890.local
```

> **Note**
>
> If this command hangs, configure your interface to link-local first.

**Response**

```text
PING os-991234567890.local (192.0.2.130): 56 data bytes
64 bytes from 192.0.2.130: icmp_seq=0 ttl=64 time=0.644 ms
64 bytes from 192.0.2.130: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 192.0.2.130: icmp_seq=2 ttl=64 time=0.299 ms

--- os-991234567890.local ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.299/0.520/0.644/0.157 ms
```

> **Note**
>
> In this example, the sensor IPv4 address is `192.0.2.130`. An address of the form `169.254.x.x` means it is connected via link-local.

3. Alternatively, resolve the sensor IP using `dns-sd`:

**Command**

```shell
dns-sd -G v4 [sensor_hostname]
```

**Example**

```shell
Mac-Computer:~ username$ dns-sd -G v4 os-991234567890.local
```

**Response**

```text
DATE: ---Tue 28 Apr 2020---
11:40:43.228  ...STARTING...
Timestamp     A/R  Flags  if  Hostname                     Address         TTL
11:40:43.414  Add  2      18  os-991234567890.local.  192.0.2.130      120
```

> **Note**
>
> An address of the form `169.254.x.x` means the sensor is connected via link-local.

## Determining the IPv4 Address of the Interface

Identify the IPv4 address of the interface the sensor is connected to (e.g., `en1` in the example below).

1. Open **Terminal** (**Cmd+Space**, type `Terminal`, press Enter).

2. View the IPv4 address of your interfaces:

**Command**

```shell
ifconfig
```

**Example**

```shell
Mac-Computer:~ username$ ifconfig
```

**Response**

```text
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
   options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
   inet 127.0.0.1 netmask 0xff000000
   inet6 ::1 prefixlen 128
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
   nd6 options=201<PERFORMNUD,DAD>
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   options=400<CHANNEL_IO>
   ether 02:00:00:aa:bb:cc
   inet6 fe80::1c30:1246:93a2:9f68%en0 prefixlen 64 secured scopeid 0x7
   inet 192.0.2.7 netmask 0xffffff00 broadcast 192.0.2.255
   nd6 options=201<PERFORMNUD,DAD>
   media: autoselect
   status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   options=400<CHANNEL_IO>
   ether 02:00:00:dd:ee:ff
   inet6 fe80::c27:1917:47ed:bcfe%en1 prefixlen 64 secured scopeid 0x12
   inet 169.254.1.100 netmask 0xffff0000 broadcast 169.254.255.255
   nd6 options=201<PERFORMNUD,DAD>
   media: autoselect (1000baseT <full-duplex>)
   status: active
```

* In this example, the sensor is plugged into interface `en1`.
* The host IPv4 address is on the `inet` line — here, `169.254.1.100`.

> **Note**
>
> An interface address of the form `169.254.x.x` means macOS self-assigned a link-local address in the absence of a DHCP server.

## Setting the Host Interface to DHCP

Set the interface to obtain an IP address automatically via DHCP.

**Command**

```shell
sudo ipconfig set [interface_name] DHCP
```

**Example** — with interface name `en1`:

```shell
Mac-Computer:~ username$ sudo ipconfig set en1 DHCP
```

**Response:** (no output)

> **Note**
>
> Verify the change with `ifconfig`. The `inet` line for `en1` will show the DHCP or link-local self-assigned address once a cable is connected.

## Setting the Host Interface to Static IP

Assign a static IPv4 address to the interface.

**Command**

```shell
sudo ipconfig set [interface_name] MANUAL [ip_address] [subnet_mask]
```

**Example** — with interface `en1`, IPv4 `192.0.2.1`, subnet mask `255.255.255.0`:

```shell
Mac-Computer:~ username$ sudo ipconfig set en1 MANUAL 192.0.2.1 255.255.255.0
```

> **Note**
>
> `/24` is shorthand for Subnet Mask `255.255.255.0`.

**Response:** (no output)

> **Note**
>
> Verify the change with `ifconfig`. The `inet` line for `en1` will show the static address, e.g., `192.0.2.1`.

## Finding a Sensor

**With mDNS Service Discovery (`dns-sd`):**

1. Browse for all sensors and their service details:

**Command**

```shell
dns-sd -Z [service type]
```

**Example**

```shell
Mac-Computer:~ username$ dns-sd -Z _ouster-lidar._tcp
```

**Response**

```text
Browsing for _ouster-lidar._tcp
DATE: ---Thu 30 Apr 2020---
17:27:52.242  ...STARTING...

_ouster-lidar._tcp                                   PTR
Ouster Sensor 991234567890._ouster-lidar._tcp
Ouster Sensor 991234567890._ouster-lidar._tcp    SRV     0 0 80 os-991234567890.local.
Ouster Sensor 991234567890._ouster-lidar._tcp    TXT     "path=/api/v1" "pn=840-102145-B"
                                                         "sn=991234567890" "fw=ousteros-image-prod-bootes-v3.2.0"
```

2. Resolve the sensor IPv4 address by hostname:

**Command**

```shell
dns-sd -G v4 [sensor_hostname]
```

**Example**

```shell
Mac-Computer:~ username$ dns-sd -G v4 os-991234567890.local
```

**Response**

```text
DATE: ---Thu 30 Apr 2020---
17:37:33.155  ...STARTING...
Timestamp     A/R  Flags  if  Hostname                     Address         TTL
17:37:33.379  Add  2      7   os-991234567890.local.  192.0.2.130      120
```

> **Note**
>
> In this example, the sensor IPv4 address is `192.0.2.130`.

**With Discovery App:**

Step 1: Download [Discovery DNS-SD Browser](https://apps.apple.com/us/app/discovery-dns-sd-browser/id1381004916?mt=12).

![Downloading Discovery DNS-SD Browser](/sensor-docs/_fern-files/_img/5316650c30af54fe4c02d0b6d659bd2fe40783e63e97fab68b4fdc11a3a85e33.webp)

Step 2: Use Finder to locate and launch *Discovery*.

![Finding the Discovery app in Finder](/sensor-docs/_fern-files/_img/94c74f237e0ebb6f99531a36c775aa0116493c4c10dbd97112ce722c51494c8d.webp)

Step 3: The sensor appears under `_ouster-lidar._tcp`. Click it to view all sensor details.