RSH
RTSP
SCCP
SIP
SQLNET
TFTP
XDMCP
# Display NAT session information generated when Host A accesses the FTP server.
[Router] display nat session verbose
Initiator:
Source
Destination IP/port: 202.38.1.2/21
DS-Lite tunnel peer: -
VPN instance/VLAN ID/VLL ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/1
Responder:
Source
Destination IP/port: 202.38.1.1/1025
DS-Lite tunnel peer: -
VPN instance/VLAN ID/VLL ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/1
State: TCP_ESTABLISHED
Application: HTTP
Start time: 2012-08-15 14:53:29
Initiator->Responder:
Responder->Initiator:
Total sessions found: 1
NAT hairpin in P2P mode configuration example
Network requirements
In the P2P application, internal clients must register their IP address to the external server and the
server records the registered IP addresses and port numbers of the internal clients. An internal client
must request the IP address and port number of another client from the external server before
accessing the client.
Configure NAT hairpin so that:
•
The internal clients can register the same public address to the external server.
•
The internal clients can access each other through the IP address and port number obtained
from the server.
: Enabled
: Enabled
: Enabled
: Enabled
: Enabled
: Enabled
: Enabled
IP/port: 192.168.1.2/1694
IP/port: 192.168.1.4/21
TTL: 3597s
7 packets
308 bytes
5 packets
312 bytes
159