NAT based on IP address and port translation belongs to many-to-one IP address translation, that is, multiple private IP addresses can be converted into one public IP address.
NAT based on IP address and port translation converts server IP addresses and ports at the same time to implement many-to-one IP address translation.
For NAT mapping, you can select internal server port numbers based on service scenarios. Table 1 describes the current port numbers that can be mapped. For detailed port number information, see the Communication Matrix.
Internal Server Port | Description | Port Mapping Scenario and Supported Service Function |
|---|---|---|
9900 | Port for the CU to access the SMU through NSS. | If the C/S client and server are not in the same network (assume that the client is in the public network and the server is in the private network):
The following functions are supported after you configure NAT mapping:
|
9910 | Port for the CU to access the SMU through NSS TLS. | |
9932 | Port for the OMU to listen on the SDK. The SDK is mainly used for querying alarms and reports and pushing alarms. | |
554 | Media stream control protocol listening port. | |
322 | Media stream control protocol listening port, RTSP OVER TLS standard protocol. | |
8481 | Port for uploading and downloading electronic maps, downloading upgrade packages, and uploading snapshots taken on PUs on the C/S client. | If the C/S client and server are not in the same network (assume that the client is in the public network and the server is in the private network), this port needs to be mapped if functions related to the electronic map need to be used on the C/S client. |
The internal server port numbers of the master and slave servers are different. Therefore, the ports to be mapped for the master and slave servers are different. Table 2 describes the details.
Server Work Mode | Port that the VCN Needs to Map | Mandatory or Optional (Mandatory Indicates that the Port Must Be Configured for the Live and Recorded Video Browse Function) |
|---|---|---|
Master server | 9900 | Mandatory (when the default RTSP protocol is used for data transmission between the client and server). |
9932 | ||
554 | ||
9910 | Mandatory (when the RTSP OVER TLS protocol is used for data transmission between the client and server). | |
9932 | ||
322 | ||
8481 | Optional. This port needs to be configured if functions related to the electronic map need to be used. | |
Slave server | 554 | Mandatory (when the default RTSP protocol is used for data transmission between the client and server). |
322 | Mandatory (when the RTSP OVER TLS protocol is used for data transmission between the client and server). | |
8481 | Optional. This port needs to be configured if functions related to the electronic map need to be used. |
Assume that the stack network is used. The client (10.10.10.200) is in the public network and needs to access the VCN on the private network. Figure 1 shows the NAT mapping.
http://localhost:7890/pages/CEH0706J/03/CEH0706J/03/resources/en-us_image_0100927743.png
Table 3 describes the mapping between IP addresses and port numbers after NAT mapping.
Public IP Address and NAT Port | Private IP Address and Server Port | Description |
|---|---|---|
10.10.10.10 9900 | 192.168.10.10 9900 |
|
10.10.10.10 9932 | 192.168.10.10 9932 | |
10.10.10.10 554 | 192.168.10.10 554 | |
10.10.10.10 8481 | 192.168.10.10 8481 | |
10.10.10.10 1554 | 192.168.10.11 554 | |
10.10.10.10 18481 | 192.168.10.11 8481 | |
10.10.10.10 2554 | 192.168.10.12 554 | |
10.10.10.10 28481 | 192.168.10.12 8481 |
