> 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/own-network.md).

# Your own network

Use this when the link must stay on a private network you control, such as WireGuard.

The network's gateway runs on Cloudflare, which can't join a WireGuard network directly. So a small `cloudflared` connector runs on a machine inside your network (it can be the same machine as the agent) and carries the network's connection in. You decide what that connector can reach.

## Steps

1. **Run the agent in inbound mode** on a private address, with TLS, and ideally requiring the network's client certificate:

   ```bash
   podtorrent-agent -listen 10.8.0.2:8443 \
     -tls-cert node.crt -tls-key node.key \
     -client-ca podtorrent-network-ca.pem \
     -engine http://127.0.0.1:8000 -manifest manifest.json
   ```

   Get `podtorrent-network-ca.pem` from the PodTorrent team.
2. **Tell the team** the agent's private address and how your network is joined. They set up the connector details with you.
3. **The team registers the link**, and the network connects within a minute.

A WireGuard hub run by PodTorrent might be offered later if a connector doesn't fit your policy. It doesn't exist yet.


---

# 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/own-network.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.