Linux
Tested on Ubuntu 18.04 and 20.04.4 LTS. The sensor hostname is os-991234567890.local (serial number on the sticker on top of the sensor).
Connecting the Sensor
- Connect the sensor to an available Ethernet port on the host machine or router.
- The sensor automatically obtains an IP address via link-local or DHCP, depending on network configuration.
- When connecting directly to the host machine, set the Ethernet interface to
Link-Local Onlymode via CLI or GUI. See Setting the Interface to Link-Local Only.
It can take up to 60 seconds to obtain an IP address after initial power-up.
Setting the Interface to Link-Local Only
Via Command Line:
Command
To find your connection name, run nmcli connection show.
Example — with interface name eth0:
Response: (no output)
Verify the change with ip addr. Once the sensor is reconnected, the inet line for eth0 will show the negotiated link-local address (e.g., 169.254.1.100).
Via GUI: Set the interface to Link-Local Only mode in the network manager GUI.
The Sensor Homepage
- Enter
http://os-991234567890.local/in your browser’s address bar to open the sensor homepage.
If the sensor homepage does not load, follow the steps in Determining the IPv4 Address of the Sensor to verify the sensor has a valid IP address.
Determining the IPv4 Address of the Sensor
-
Open a Terminal (Ctrl+Alt+T).
-
Ping the sensor to find its IPv4 address:
Command
Example
If this command hangs, configure your interface to link-local first (see Setting the Interface to Link-Local Only).
Response
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.
- Alternatively, browse by service type using
avahi-browse:
Command
Example
Response
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., eth0 in the example below).
-
Open a Terminal (Ctrl+Alt+T).
-
View all interface addresses:
Command
Example
Response
- In this example, the sensor is plugged into interface
eth0. - The host IPv4 address is on the
inetline — here,169.254.1.100.
An interface address of the form 169.254.x.x means Linux 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.
Unplug the cable from the interface before making changes.
Via Command Line:
Command
Example — with interface name eth0:
Response: (no output)
Verify the change with ip addr. The inet line for eth0 will be absent until a cable is connected to a device with a DHCP server.
Via GUI: Set the interface to Automatic (DHCP) mode in the network manager GUI.
Setting the Host Interface to Static IP
Assign a static IPv4 address to the interface.
Unplug the cable from the interface before making changes.
Via Command Line:
Command
Example — with interface eth0 and IPv4 address 192.0.2.1/24:
/24 is shorthand for Subnet Mask 255.255.255.0.
Response: (no output)
Verify the change with ip addr. The inet line for eth0 will show the static address, e.g., 192.0.2.1.
Via GUI: Set the interface to Manual (static) mode in the network manager GUI.
Finding a Sensor with mDNS Service Discovery
The sensor announces itself via mDNS with service type _ouster-lidar._tcp. Use avahi-browse to find all sensors on the network.
- Find all sensors and their IPv4 addresses using service type
_ouster-lidar._tcp:
Command
Example
Response
In this example, the sensor IPv4 address is 192.0.2.130.

