> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/win-gateway-installation-manual/node-information.md).
# Node information
Once a node is linked and communicates with the gateway, its settings can be checked and potentially modified in the gateway web interface. Making the node modifications directly in the gateway interface is not recommended because some changes made directly in the gateway may result in the node being out of sync with the node settings set in Boomerang and these settings will be overwritten by the Boomerang server if changes are made on the server.
The gateway web interface provides infromation that may be used for debugging of the WIN radio network.
To check the nodes' settings:
* Connect to the gateway as described in [Connect to the gateway](/win-gateway-installation-manual/gateway-configuration/connect-to-the-gateway.md).
* Click on “Advanced”->”Details” to open the view of the gateway and linked nodes details.
This form presents detailed information about each node connected to the gateway.
Most of these fields can be ignored by an installer, but there are some fields that contain data necessary during installation.
The text from the page can be selected and copied to the clipboard but the page is auto updating which makes copying text from the page difficult. To stop auto updating, untick the “Enable auto update” box in the top right corner.
---
# 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://help.boomerang3.com/win-gateway-installation-manual/node-information.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.
