13. Skip to content

13. Destination NAT (DNAT)

Destination NAT, or DNAT in short, is used when there is a server on the INSIDE network that should be exposed to the OUTSIDE clients.

A typical use case may be there is a web server at the HQ, but the clients from the public Internet need to access the web server using the standard ports. This would then require opening the relevant ports on the CPE device.

ChiefNET's DNAT feature can be used for that purpose.

13.1 DNAT from Internet Ports

ChiefNET's DNAT feature can be abled on the WAN ports that are connected to your ISPs. Anyone on the Internet can be allowed to access certain servers. Note that this is not always secure. For internal use however, DNAT within the Secure SDWAN network, described below, may be used.

NOTE

Destination NAT is supposed to be used only as a last resort. Exposing an inside server to the outside clients is typically NOT done these days using DNAT. We highly recommend that the server be moved to the cloud and enforce strict content rules to isolate the servers from the rest of your INSIDE network.

13.2 DNAT within Secure SDWAN Network

All ChiefNET devices are connected together using the secure SDWAN network. It is still possible for some sites to have private or overlapping address spaces. Those are essentially non-routable or NAT'ed sites. It is still possible to house servers inside such private networks, and use ChiefNET's DNAT inside the SDWAN interface.

This allows for your sites with private address spaces to be connected to the other sites, and still support DNAT with full security within your corporate network.