> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/home/network-services/nat-gateway/overview/limitations.md).

# Limitations

Known limitations of IONOS CLOUD Managed NAT Gateway: LAN restrictions, no DNAT, no IPv6 SNAT, and firewall independence

## LAN restrictions

Only private LANs can be connected to the Managed NAT Gateway. The Managed NAT Gateway cannot be connected to a public LAN. Furthermore, you cannot change a LAN attribute from "private" to "public" if the LAN is connected to a Managed NAT Gateway.

## Unsupported capabilities

The NAT gateway does not support the following capabilities:

* **No port forwarding (Destination Network Address Translation (DNAT)):** You cannot expose a VM behind the NAT gateway on a specific public port. Use a Network Load Balancer or attach a public IP address directly to the VM for inbound services.
* **No unsolicited inbound connections:** Return traffic on established outbound sessions works normally. New inbound connections initiated from the Internet are dropped.
* **No IPv6 SNAT:** The NAT gateway currently translates IPv4 addresses only.
* **Not a firewall replacement:** The Cloud Firewall on each VM Network Interface Controller (NIC) still applies independently. A rule that denies inbound TCP/22 on a NIC will drop Secure Shell (SSH) even if routing through the NAT gateway is otherwise correct.

## Next steps

* [<mark style="color:blue;">Configure a NAT Gateway</mark>](/cloud/home/network-services/nat-gateway/how-tos/configure-nat-gateway.md)
* [<mark style="color:blue;">FAQ</mark>](/cloud/home/network-services/nat-gateway/nat-gateway-faq.md)


---

# 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.ionos.com/cloud/home/network-services/nat-gateway/overview/limitations.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.