Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Translation Types

    The Multiservices PIC interfaces support the following types of translation:

    • Static-source translation—Allows you to hide a private network without using NAPT (Network Address Port Translation). It features one-to-one mapping between the original address and the translated address, and mapping is configured statically. For more information, see Basic NAT.
    • Dynamic-source translation—Includes two options: dynamic address-only source translation and Network Address Port Translation (NAPT).
      • Dynamic address-only source translation—A NAT address is picked up dynamically from a source NAT pool and the mapping from the original source address to the translated address is maintained as long as there is at least one active flow that uses this mapping. For more information, see Dynamic NAT.
      • NAPT—Both the original source address and the source port are translated. The translated address and port are picked up from the corresponding NAT pool. For more information, see NAPT.
    • Static destination translation—Allows you to make selected private servers accessible. It features one-to-one mapping between the translated address and the destination address, and mapping is configured statically. For more information, see Static Destination NAT.

    Junos OS supports NAT functionality described in the following RFCs and Internet drafts:

    • RFC 2663, IP Network Address Translator (NAT) Terminology and Considerations
    • RFC 4787, NAT Behavioral Requirements for Unicast UDP
    • RFC 5382, NAT Behavioral Requirements for TCP
    • RFC 5508, NAT Behavioral Requirements for ICMP

    Published: 2012-07-02