Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Next Gen Services Stateful NAT64

 

Perform the following steps to configure Next Gen Services Stateful NAT64

  1. Configuring the Source Pool for Stateful NAT64

  2. Configuring the NAT Rules for Stateful NAT64

  3. Configuring the Service Set for Stateful NAT64

  4. Clearing the Don’t Fragment Bit

Configuring the Source Pool for Stateful NAT64

To configure the source pool for Stateful NAT64:

  1. Create a source pool.
  2. Define the addresses or subnets to which source addresses are translated.

    or

    To disable round-robin port allocation for all NAT pools that do not specify an automatic (random-allocation | round-robin) setting, configure the global setting.

  3. To configure a range of ports to assign to a pool, perform the following:Note

    If you specify a range of ports to assign, the automatic statement is ignored.

    1. Specify the low and high values for the port. If you do not configure automatic port assignment, you must configure a range of ports.
    2. Specify either random allocation or round-robin allocation. Round-robin allocation is the default.
  4. Assign a port within the same range as the incoming port—either 0 through 1023 or 1024 through 65,535. This feature is not available if you configure port-block allocation.
  5. Assign a port with the same parity (even or odd) as the incoming port. This feature is not available if you configure port-block allocation.
  6. Configure a global default port range for NAT pools that use port translation. This port range is used when a NAT pool does not specify a port range and does not specify automatic port assignment. The global port range can be from 1024 through 65,535.
  7. Configure the source pool without port translation.
  8. Configure the maximum number of ports that can be allocated for each host. The range is 2 through 65,535.
  9. If you want to allocate a block of ports for each subscriber to use, configure port-block allocation:
    1. Configure the number of ports in a block. The range is 1 through 64,512 and the default is 256.
    2. Configure the interval, in seconds, for which the block is active. After the timeout, a new block is allocated, even if ports are available in the active block. If you set the timeout to 0, port blocks are filled completely before a new port block is allocated, and the last port block remains active indefinitely. The range is 0 through 86,400, and the default is 120.
    3. If you set the active-block-timeout to 0, you can configure the amount of time before the last active port block is released. The range is 120 through 864,000 seconds, and the default is 300.
    4. Configure the maximum number of blocks that can be allocated to a user address. The range is 1 through 512, and the default is 8.
    5. Specify how often to send interim system logs for active port blocks and for inactive port blocks with live sessions. This increases the reliability of system logs, which are UDP-based and can get lost in the network. The range is 1800 through 86,400 seconds, and the default is 0 (interim logs are disabled).
  10. Specify the timeout period for endpoint independent translations that use the specified NAT pool. Mappings that are inactive for this amount of time are dropped. The range is 120 through 86,400 seconds. If you do not configure ei-mapping-timeout, then the mapping-timeout value is used for endpoint independent translations.
  11. Specify the timeout period for address-pooling paired mappings that use the NAT pool. The range is 120 through 86,400 seconds, and the default is 300. Mappings that are inactive for this amount of time are dropped.

    If you do not configure ei-mapping-timeout for endpoint independent translations, then the mapping-timeout value is used for endpoint independent translations.

  12. To allow the IP addresses of a NAT source pool to overlap with IP addresses in pools used in other service sets, configure allow-overlapping-pools.

Configuring the NAT Rules for Stateful NAT64

For Stateful NAT64, you must configure a source rule and a destination rule. To configure the NAT rules for Stateful NAT64:

  1. Configure the source NAT rule name.
  2. Specify the traffic direction to which the NAT rule set applies.
  3. Specify the IPv6 source addresses that are translated by the NAT rule.
  4. Configure the matching destination address as 0.0.0.0/0.
  5. Specify one or more application protocols to which the NAT rule applies. The number of applications listed in the rule must not exceed 3072.
  6. Specify the NAT source pool that contains the addresses for translated source addresses.
  7. Configure endpoint-independent mapping, which ensures that the same external address and port are assigned to all connections from a given host.

    1. Configure the mapping type as endpoint independent.
    2. Specify prefix lists that contain the hosts that are allowed to establish inbound connections using the endpoint-independent mapping. (Prefix lists are configured at the [edit policy-options] hierarchy level.)
    3. Specify the maximum number of inbound flows allowed simultaneously on an endpoint-independent mapping.
    4. Specify the direction in which active endpoint-independent mapping is refreshed. By default, mapping is refreshed for both inbound and outbound active flows.
  8. Configure the destination NAT rule name.
  9. Specify the traffic direction to which the destination NAT rule set applies.
  10. Specify the IPv6 prefix source addresses that are translated by the destination NAT rule. Use the same value that you used for the NAT source rule.
  11. Specify the prefix that is used to embed the IPv4 destination address in the IPv6 destination address.
  12. Configure the IPv6 destination address to match. This is the IPv4 destination address embedded in IPv6 by using the destination-prefix.
  13. Configure the generation of a syslog when traffic matches the NAT rule conditions.

Configuring the Service Set for Stateful NAT64

To configure the service set for stateful NAT64:

  1. Define the service set.
  2. Configure either an interface service, which requires a single service interface, or a next-hop service, which requires an inside and outside service interface.

    or

  3. Specify the NAT rule sets to be used with the service set.

Clearing the Don’t Fragment Bit

To prevent unnecessary creation of IPv6 fragmentation headers when translating IPv4 packets that are less than 1280 bytes, you can specify that the don’t fragment (DF) bit for IPv4 packet headers is cleared when the packet length is less than 1280 bytes.

Related Documentation