Appendix A: NAT router requirements for NAT Traversal feature Page 855 of 910
IP Line Description, Installation and Maintenance
Request 14 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 15 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 16 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 17 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 18 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 19 of 20...
Loopback packet from 69.156.96.28 port 57285
Request 20 of 20...
Loopback packet from 69.156.96.28 port 57285
TCP RESULTS:
TCP consistent translation: YES (GOOD for peer-to-peer)
TCP simultaneous open: YES (GOOD for peer-to-peer)
TCP loopback translation: YES (GOOD for peer-to-peer)
TCP unsolicited connections filtered: NO (BAD for security)
UDP RESULTS:
UDP consistent translation: YES (GOOD for peer-to-peer)
UDP loopback translation: YES (GOOD for peer-to-peer)
UDP unsolicited messages filtered: NO (BAD for security)
The important information is highlighted in red.
In order for the NAT router to support the NAT Traversal feature, natcheck
must print the following to the screen:
UDP consistent translation: YES (GOOD for peer-to-peer)
YES indicates that Cone NAT is being used. NO indicates that Symmetric
NAT is present. Symmetric NAT is not supported.
Note: Near the beginning of the printout, the PUBLIC port seen by
various servers is printed out. In this case, all three servers receive the
packets from the same PUBLIC port of 57283. This Private-to-Public
port mapping is seen in Figure 275 on page 856.