> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/gremsy-tiny-series/lynx/software-configuration/web-setting-app/systems/ip-address.md).
# IP ADDRESS
### Default IP Address of LYNX Payload
{% hint style="info" %}
**Payload Address:** 192.168.144.240
**Netmask:** 255.255.255.0
**Gateway:** 192.168.144.11
Click on **“APPLY”** to save the information.
{% endhint %}
### Change IP Address via Ethernet Connection
{% stepper %}
{% step %}
**Connect LYNX via Ethernet**
Plug an Ethernet cable into the MAINBOARD Ethernet port and connect it to your computer or network switch.
{% endstep %}
{% step %}
**Access the Web Interface**
In your browser, enter the updated IP address assigned to LYNX using the following format:
```
http://192.168.144.240:8000/
```
```
http://:8000
```
{% endstep %}
{% step %}
**Navigate to Static IP Settings**
Once connected to the web interface:
* Go to the **IP Address** tab.
* Enter a new static IP address if needed.
{% endstep %}
{% step %}
**Apply the Changes**
Click **Apply and Reboot** to save the new configuration. The Lynx will restart with the updated IP settings.
{% endstep %}
{% endstepper %}
✅ **Tip:** Make sure your computer is in the same subnet (e.g., 192.168.144.x) to maintain connectivity.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.gremsy.com/gremsy-tiny-series/lynx/software-configuration/web-setting-app/systems/ip-address.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
