Stephen Fisher wrote:
> On Fri, Mar 28, 2008 at 11:06:25AM -, Keith French wrote:
>
>> In recent versions of Wireshark this behaviour seems to have changed,
>> in that it tries to resolve the source port of the SYN as well. The
>> name it resolves it to (on my PC anyway) is often misleading:
On Fri, Mar 28, 2008 at 11:06:25AM -, Keith French wrote:
> In recent versions of Wireshark this behaviour seems to have changed,
> in that it tries to resolve the source port of the SYN as well. The
> name it resolves it to (on my PC anyway) is often misleading:-
>
> qsnet-trans > http [SY
Keith French wrote:
> When a TCP session is initialised or closed, the TCP SYN & FIN
> handshakes shows the port numbers at the start of the Info column in the
> Summary view within Wireshark. This always used to take the format (in
> the case of a SYN) of the unresolved source port followed by the
