Upon request of a SmartTrace, PT command, of a TCP/IP stack, placing a port on field Foreign Ports, having fields Foreign Host, Local Host, and Local Ports a value or not, Foreign Ports is not respected for packet filtering,
as the trace result shows other packets with other ports that have not been specified.
On the SmartTrace help screen, Foreign Ports applies to both TCP and UDP, and not only to UDP, as follows:
Foreign Ports is the port name or number used by the remote endpoint in a TCP/UDP connection. The
following formats are supported:
There are 2 exceptions where Foreign Ports for TCP is recognized:
Foreign Ports for TCP is recognized if the "Create Multiple TCP Connection Trace?" is set to YES.
"PT" traces initiated via the connection list panels (/CONN*) uses the Foreign Ports because connection lists are based on whatever values are found on the connection list entry.