> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/knowledge-base/how-to-articles/vpn-routing.md).

# VPN-routing

Automatiser VPN-routing i Remote Desktop Manager ved at køre kommandoer efter forbindelse og før afbrydelse, så ruter tilføjes automatisk.

Det er enkelt at oprette en VPN-forbindelse med Remote Desktop Manager. Det er desværre nødvendigt at tilføje ruter manuelt. Vent på, at adapteren opretter forbindelse, find IP-adressen, og tilføj derefter de ønskede ruter. Selv hvis De bruger et script (f.eks. et PowerShell-script), forbliver det en overflødig og tidskrævende opgave.

### Løsning

Denne funktion er en del af et større begreb, der kaldes VPN-kommandoer. Den giver Dem mulighed for at køre enhver type script eller eksekverbar fil efter VPN-forbindelse og før VPN-afbrydelse.

### Arbejdsflow

1. Konfigurer VPN'en til at vente, indtil adapteren opretter forbindelse og får tildelt en IP-adresse (vi bruger adapterens IP-adresse til at definere ruterne).
2. Klik på ***Tilføj*** for at vise dialogboksen ***Kommandoer***.
3. Opret en definition af ruten ved at vælge alternativknappen ***Rute (tilføj/fjern)***.
4. Angiv IP-adressen og eventuelle andre påkrævede oplysninger.


---

# 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.devolutions.net/rdm/da/knowledge-base/how-to-articles/vpn-routing.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.