Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

CGNAT Implementations Feature Comparison for Junos Address Aware by Type of Interface Card

Table 1 summarizes feature differences between the Junos OS carrier-grade NAT implementations

Table 1: CGNAT Implementation—Feature Comparison by Platform

Feature

MS-DPC

MS-100

MS-400

MS-500

MS-MPC

MS-MIC

MPC Types 1, 2, 3

Inline NAT

 

Static Source NAT

yes

yes

yes

DynamicSource NAT - Address Only

yes

yes

no

Dynamic Source NAT - NAPT Port Translation with Secured Port Block Allocation

yes

no

no

Dynamic Source NAT - NAPT Port Translation with Deterministic Port Port Block Allocation

yes

no

no

Static Destination NAT

yes

yes

yes

Note: Destination NAT can be implemented indirectly. See Inline Network Address Translation Overview for MPC Types 1, 2, and 3

Twice NAT

yes

no

yes

Note: Twice NAT can be implemented indirectly. See Inline Network Address Translation Overview for MPC Types 1, 2, and 3

NAPT - Preserve Parity and Port

yes

no

no

NAPT - EIM/EIF/APP

yes

yes

no

NAT64

yes

yes

no

NAT64 with APP/EIM/EIF

no

yes

no

DS-Lite

yes

no

no

6rd

yes

no

no

Overload Pool/Overlap Address Across NAT Pool

yes

no

no

Port Control Protocol

yes

no

no

CGN-PIC

yes

no

no

AMS Support

no

yes

no

Table 2 summarizes availability of translation types by type of interface card.

Table 2: CGNAT Translation Types

Translation Type

MS-DPC

MS-100

MS-400

MS-500

MS-MPC

MS-MIC

MPC Types 1, 2, 3

Inline NAT

 

basic-nat44

yes

yes

yes

basic-nat66

yes

no

no

basic-nat-pt

yes

no

no

deterministic-napt44

yes

no

no

dnat-44

yes

yes

no

dynamic-nat44

yes

yes

no

napt-44

yes

yes

no

napt-66

yes

no

no

napt-pt

yes

no

no

stateful-nat64

yes

yes

no

twice-basic-nat-44

yes

no

no

twice-dynamic-nat-44

yes

no

no

twice-dynamic-napt-44

yes

no

no

Published: 2014-05-29

Supported Platforms

Published: 2014-05-29