> For the complete documentation index, see [llms.txt](https://docs.earthdefenderstoolkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthdefenderstoolkit.com/device-usage/first-steps/connecting-to-the-internet.md).
# Connecting to the internet
The recomended and easiest way to connect any Offline Toolkit device to the Internet is through ethernet cable, directly from the router to the device.
Just don't plug into the router's WAN port, which is usually blue.
Your device can connect to a local WiFi hotspot in order to gain access to the internet, but this feature hasn't been well tested as of yet.
To test it out go to the admin panel, and to the **Networking** tab, usually located at:
The device will scan for nearby wifi hotspots. You can then select the one to connect to, enter the password and connect.
---
# 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.earthdefenderstoolkit.com/device-usage/first-steps/connecting-to-the-internet.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.
