> 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/infrastructure.md).
# Infrastructure
The WIN sensors are connected to nodes which communicate via radio with WIN gateway. WIN gateway uses Ethernet interface to communicate with Boomerang 3 server and works as a communication channel between the sensors and Boomerang system. One gateway can handle up to 10 nodes and every node can have multiple sensors.
An example infrastructure may look as shown below:
All data is sent in XML format via a POST at port 80. The server needs to acknowledge the received POST by sending a POSTBack reply confirming the reception. The server can also send other commands to the gateway, such as changing the transmission intervals for the nodes, changing the NTP server, etc. Note that the server can only do this immediately after the gateway has sent its POST to the server, so changing a parameter may take some time before it has been implemented on the gateway/node side.
---
# 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/infrastructure.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.
