Prisma SD-WAN
Traditional Workflow (Without NAT)
Table of Contents
Expand All
|
Collapse All
Prisma SD-WAN Docs
-
-
-
- CloudBlade Integrations
- CloudBlades Integration with Prisma Access
-
-
-
-
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 5.6
- New Features Guide
- On-Premises Controller
- Prisma SD-WAN CloudBlades
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
Traditional Workflow (Without NAT)
This topic describes the traditional workflow without NAT Protocol
Translations.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
Without the implementation of NAT protocol translation, the workflow for inter-IP family
communication is severely constrained or entirely non-existent.
- Direct Communication Failure: An IPv6-only device attempting to reach an IPv4-only server simply fails, as the IPv6 packet structure is incomprehensible to the IPv4 network, and vice-versa.
- Fragmented Network Access: Users or applications are restricted to accessing resources only within their native IP address family, leading to a fragmented and inefficient network experience.
- Manual Workarounds: Workarounds might include dual-stack deployment on every device (running both IPv4 and IPv6 stacks simultaneously), which is resource-intensive and often not feasible for legacy devices. Alternatively, application-layer proxies can be used, adding significant latency and complexity, and requiring per-application configuration.
- Costly Infrastructure Overhauls: Organizations are forced into costly and disruptive "big bang" upgrades to move entirely to IPv6, rather than a phased approach. This can involve replacing a significant portion of network infrastructure and applications.
- Limited Scalability: Managing two entirely separate and uncommunicative networks (IPv4 and IPv6) significantly complicates network management and limits overall scalability.