> 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/knowledge-base/knowledge-base-articles/entry-settings/devolutions-gateway-tunnel.md).

# Devolutions Gateway tunnel

Configure Devolutions Gateway tunnel session settings in Remote Desktop Manager, including listeners, bind and target addresses, and allow rules.

This article details the many settings and options available for ***Devolutions Gateway tunnel*** session entries in Remote Desktop Manager.

{% hint style="info" %}
The entry must use Devolutions Gateway in ***Connection*** – ***VPN/tunnel/gateway***. The status line above the listeners shows whether it does, and saving the entry without it asks for confirmation. When the workspace does not support Devolutions Gateway, a warning appears when the entry settings open.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the entry opens: <em><strong>External</strong></em>, <em><strong>Embedded (tabbed)</strong></em> or <em><strong>Undocked</strong></em>. On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</td></tr></tbody></table>

### General

**Listeners**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Listeners</strong></td><td>The local listeners opened through Devolutions Gateway, with their <em><strong>Mode</strong></em>, <em><strong>Bind address</strong></em>, <em><strong>Target</strong></em>, and <em><strong>Description</strong></em>. A listener without a target shows <em><strong>Dynamic</strong></em> in the <em><strong>Target</strong></em> column. Use the <em><strong>New</strong></em>, <em><strong>Edit</strong></em>, and <em><strong>Delete</strong></em> buttons to manage the list, or double-click a listener to edit it. <em><strong>New</strong></em> and <em><strong>Edit</strong></em> open the <em><strong>Jetsocat listener</strong></em> window, which holds the fields below. <em><strong>Delete</strong></em> asks for confirmation. At least one listener is required.</td></tr><tr><td><strong>Mode</strong></td><td><p>The type of listener:</p><ul><li><strong>SOCKS5 proxy</strong></li><li><strong>HTTP proxy</strong></li><li><strong>TCP forward</strong></li></ul><p>A new listener starts in <em><strong>TCP forward</strong></em> mode.</p></td></tr><tr><td><strong>Bind address</strong></td><td>The local address and port the listener binds to. The address defaults to <code>127.0.0.1</code> and is required.</td></tr><tr><td><strong>Target</strong></td><td>The address and port the listener forwards traffic to. Available only when the <em><strong>Mode</strong></em> is <em><strong>TCP forward</strong></em>. In that mode, the address and a port greater than 0 are both required.</td></tr><tr><td><strong>Description</strong></td><td>A description of the listener.</td></tr></tbody></table>

**Allow rules**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Allow rules</strong></td><td>The destinations that listeners without a target are allowed to reach, with their <em><strong>Target filter</strong></em> and <em><strong>Description</strong></em>. Use the <em><strong>New</strong></em>, <em><strong>Edit</strong></em>, and <em><strong>Delete</strong></em> buttons to manage the list, or double-click a rule to edit it. <em><strong>New</strong></em> and <em><strong>Edit</strong></em> open the <em><strong>JMUX rule</strong></em> window, which holds the fields below. Available only when at least one listener has no target. When every listener has a target, the rules are cleared on save. When no listener has a target, at least one rule is required.</td></tr><tr><td><strong>Target filter</strong></td><td>The host and port that the rule allows. The host is required.</td></tr><tr><td><strong>Description</strong></td><td>A description of the rule.</td></tr></tbody></table>


---

# 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/knowledge-base/knowledge-base-articles/entry-settings/devolutions-gateway-tunnel.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.
