> For the complete documentation index, see [llms.txt](https://docs.podtorrent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podtorrent.com/running-a-node/connection-modes.md).

# Choose a connection mode

The agent can reach the network in four ways. What travels over the link is the same in all of them; only who opens the connection, and over what, changes.

| Mode                                                                          | Who connects                                | Open ports on your side | Use it when                                               |
| ----------------------------------------------------------------------------- | ------------------------------------------- | ----------------------- | --------------------------------------------------------- |
| [Outbound](/running-a-node/connection-modes/outbound.md) (default)            | Agent → network                             | none                    | Outbound HTTPS is allowed. Simplest.                      |
| [Cloudflare Tunnel](/running-a-node/connection-modes/cloudflare-tunnel.md)    | Network → agent, through your tunnel        | none                    | You want no public endpoint and don't want to run a VPN   |
| [Your own network](/running-a-node/connection-modes/own-network.md)           | Network → agent, over your WireGuard or VPN | none to the internet    | The link must stay on a network you control               |
| [Inbound with mutual TLS](/running-a-node/connection-modes/inbound-public.md) | Network → agent, over HTTPS                 | one TLS port            | You prefer to expose an endpoint behind your own firewall |

**Not sure? Use outbound.** Switch only if your security policy requires it.

In the three inbound modes the network authenticates with your node token, and the agent rejects anything else. If the link drops, the network dials again within a minute. The PodTorrent team registers your node's address on their side, so talk to them before you switch.


---

# 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.podtorrent.com/running-a-node/connection-modes.md?ask=<question>&goal=<user_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.