Summary
Here’s a summary table of FortiADC’s Layer 4 deployment modes with their features and differences.
| Traffic Flow - Incoming | |
| DNAT | Client ⟶ FortiADC ⟶ Server |
| FULLNAT | Client ⟶ FortiADC ⟶ Server |
| Direct Routing | Client ⟶ FortiADC ⟶ Server |
| NAT46 | IPv4 Client ⟶ FortiADC ⟶ IPv6 Server |
| Tunneling | Client ⟶ FortiADC ⟶ Server |
| Traffic Flow - Outgoing | |
| DNAT | Server ⟶ FortiADC ⟶ Client |
| FULLNAT | Server ⟶ FortiADC ⟶ Client |
| Direct Routing | Server ⟶ Client |
| NAT46 | IPv6 Server ⟶ FortiADC ⟶ IPv4 Client |
| Tunneling | Server ⟶ Client |
| VIP Handling | |
| DNAT | VIP configured only on FortiADC |
| FULLNAT | VIP configured only on FortiADC |
| Direct Routing | VIP configured on both FortiADC and real servers (as loopback, no ARP) |
| NAT46 | VIP configured only on FortiADC |
| Tunneling | VIP configured on both FortiADC and real servers (as loopback, no ARP) |
| Client IP Preservation | |
| DNAT | Yes |
| FULLNAT | No, but FortiADC supports client IP insertion via TCP Application Profile settings |
| Direct Routing | Yes |
| NAT46 | No |
| Tunneling | Yes |
| Key Requirements | |
| DNAT |
|
| FULLNAT |
|
| Direct Routing |
|
| NAT46 |
|
| Tunneling |
|
| Use Cases | |
| DNAT | Standard data center deployments |
| FULLNAT | Environments needing full control over both directions |
| Direct Routing | Performance-driven environments needing true client IP |
| NAT46 | Bridging IPv4 clients to IPv6-only back-ends |
| Tunneling | Multi-site, remote DC, or cloud deployments |