No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C00 Feature Description - NAT and IPv6 Transition 01

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
NAT64 Logs

NAT64 Logs

Purpose

When users access an IPv4 network through a NAT64 device, the source IP addresses of users are translated addresses. It is difficult to accurately locate the hosts or users who access the network, which reduces network security.

NAT64 logs can address this problem. NAT64 logs record information about NAT64 flows so that administrators can learn addresses before NAT64 translation to query and trace network activities and operations. This improves network availability and security.
NOTE:

Logs record information about only NAT64 flows from the IPv6 intranet to the IPv4 extranet and do not record information when external users access internal users.

Types

NAT64 logs are classified into binary logs and Syslogs:
  • Binary logs apply to dynamic port allocation mode. In this scenario, allocation and reclaim of each port is recorded in logs; therefore, a large number of logs are recorded. Binary logs improve the transmit and transmission efficiencies and save memory space.
  • Syslogs apply to port pre-allocation mode and semi-dynamic port allocation mode. In these scenarios, getting online and offline of users or allocation and reclaim of a number of ports are recorded in logs; therefore, a small number of logs are recorded. Syslogs are in the standard format, allowing Huawei log servers to connect to those of different vendors.

Implementation

  • NAT64 binary logs are implemented as follows:

    1. The device classifies IP packets according to the source IPv6 address, source port number, destination IP address, translated source IPv4 address, translated source port number, and protocol number.
    2. IP packets of each type are added to a NAT64 flow and cached in the NAT64 session table.
    3. When a flow in the session table is created or ages out, the flow is encapsulated into UDP packets in binary format and sent to the specified log host.
  • NAT64 Syslogs are implemented as follows:

    When a user gets online or offline, the online and offline information, IP address, and port range are encapsulated into UDP packets in Syslog format and sent to the specified log host.

    When a flow in the session table is created or ages out, the flow is encapsulated into UDP packets in Syslog format and sent to the specified log host.

Exporting

NAT64 logs are exported using UDP packets. A UDP packet contains original information about a maximum of 13 NAT64 flows and is composed of a header and a maximum of 13 records. Each record corresponds to a NAT64 flow.
  • Binary logs record the type of the protocol over IP, reason for the flow end, IP packet version, ToS field of the IPv4 packet, source/destination IP addresses before and after translation, source/destination port numbers before and after translation, start and end times of the flow, received and sent packet quantity, received and sent byte quantity, and ID of the NAT64 instance.
  • Syslogs record the vendor ID, version number, module number, information level, source/destination IP addresses before and after translation, and source/destination port numbers before and after translation.
Download
Updated: 2018-07-04

Document ID: EDOC1100027155

Views: 19794

Downloads: 67

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next