> For the complete documentation index, see [llms.txt](https://docs.ceruleansonar.com/c/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ceruleansonar.com/c/omnitrack/standard-blue-robotics-ecosystem-internet-protocol-ip-addresses.md).

# Standard Blue Robotics Ecosystem Internet Protocol (IP) Addresses

The following addresses include default addresses defined by Blue Robotics for their BlueROV and BlueBoat systems as well as default addresses for Cerulean  equipment defined by Cerulean Sonar. You are free to change them as needed, such as to accommodate multiple systems in a signal operating area or to co-exist with other systems that are in the same address space.

<table><thead><tr><th width="133.4444580078125">IP Address</th><th width="460.08642578125">Description</th><th>Assigned By</th></tr></thead><tbody><tr><td>192.168.2.1</td><td>User computer running software ROV control software such as QGroundControl</td><td>Blue Robotics</td></tr><tr><td>192.168.2.2</td><td>Raspberry Pi embedded in BlueROV or BlueBoat running BlueOS and/or MAVLink REST server for autopilot</td><td>Blue Robotics</td></tr><tr><td>192.168.2.3</td><td>Radio in BlueBoat BaseStation Wi-Fi radio (formerly default address for Cerulean Tracker-650 DVL)</td><td>Blue Robotics</td></tr><tr><td>192.168.2.4</td><td>Radio in BlueBoat Wi-Fi radio [note 2]</td><td>Blue Robotics</td></tr><tr><td>192.168.2.5</td><td>reserved</td><td>Cerulean</td></tr><tr><td>192.168.2.6</td><td>Extra laptop interface in network</td><td>Cerulean</td></tr><tr><td>192.167.2.7</td><td>Reserved</td><td>Cerulean</td></tr><tr><td>192.168.2.8</td><td>Tracker-650 [note 1] [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.9</td><td>ROV Locator Receiver/Transceiver (-e models only) [note 1] [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.10</td><td>ROV Locator Transmitter/Transponder (-e models only) [note 1] [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.11</td><td>Access point/radio in Cerulean Omnitrack Wi-Fi module radio if used as an access point [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.12</td><td>Client in Cerulean Omnitrack Wi-Fi module radio if BaseStation or BaseStation Plus is used as the Wi-Fi access point [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.13</td><td>Radio in Cerulean Omnitrack BaseStation Plus [note 2]</td><td>Cerulean</td></tr><tr><td>192.168.2.21</td><td>Omniscan Compute Module </td><td>Cerulean</td></tr><tr><td>192.168.2.230<br>  thru<br>192.168.2.250</td><td>Reserved for DHCP assignment by Omnitrack Wi-Fi access point.</td><td>Cerulean</td></tr><tr><td><p>192.168.2.210</p><p> thru 192.168.2.229</p></td><td>Reserved for DHCP assignment by Omniscan compute module when set up to be a DHCP server.</td><td>Cerulean</td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

\[note 1] Cerulean Sonar devices IP addresses are discoverable using our SonarView application.

\[note 2] This is the address recommended for the first device of this type on the network. Only one device per network can use any given IP address. If additional devices are added you must choose a unique IP address for those devices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ceruleansonar.com/c/omnitrack/standard-blue-robotics-ecosystem-internet-protocol-ip-addresses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.