> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/clients/client-networking.md).

# Client Networking

When users are attempting to connect to a resource through StrongDM, they are not entering the address and credentials for the resource, but rather an address that maps to the resource in StrongDM. During the request, if they are authorized to connect to the resource, StrongDM routes their traffic on and injects the correct credentials.

There are two available options for the routing of traffic locally on client machines. StrongDM, by default, uses a loopback interface, which uses a single local IP with different ports for various resources (and can be [expanded to a local IP block](https://docs.strongdm.com/admin/clients/client-networking/loopback-ip-ranges.md)). This means that when a user opens their client and connects to a resource, that connection is being routed through a local IP address and a preconfigured port that the StrongDM listener is listening for connections on. The other option is [Virtual Networking Mode](https://docs.strongdm.com/admin/clients/client-networking/virtual-networking-mode.md), which uses DNS names to route traffic locally on the client machine rather than specific IPs.

You can also [override the ports](https://docs.strongdm.com/admin/resources/port-overrides.md) that clients access resources through, on their local machine, just as you can alter local IPs or DNS names.


---

# 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.strongdm.com/admin/clients/client-networking.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.
