> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/vpn/servers/ipv6.md). # IPv6 IPv6 server configuration Pritunl offers three primary IPv6 configurations, all three will provide IPv6 internet access to Pritunl clients including clients that only have IPv4 internet connections. ### NAT This is the simplest IPv6 configuration that will NAT the primary IPv6 address of the Pritunl server. Clients will be given private IPv6 addresses. This configuration only requires enabling IPv6 in the server settings. ### Routed IPv6 Subnet This configuration will give each Pritunl client an IPv6 address from a routed IPv6 subnet. All clients will get a public routable IPv6 address that will accept ICMPv6 traffic. The IPv6 firewall can be disabled in the advanced server to allow all traffic to reach the client. This configuration requires an IPv6 block that is routed to the Pritunl server. Some providers such as Linode will provide this upon request. ### Routed IPv6 Subnet with Proxied NDP Some providers will only route IPv6 addresses once found with Neighbor Discovery Protocol. By default NDP packets wont reach the Pritunl clients. This can be fixed by enabling *Proxy NDP* in the host settings. Providers such as Vultr provide an NDP routed IPv6 subnet to all servers by default. --- # 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.pritunl.com/kb/vpn/servers/ipv6.md?ask=&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.