Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: [Ethereal-dev] Conversation list -> incorrect TCP connection direction

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Jean-Baptiste Marchand <Jean-Baptiste.Marchand@xxxxxx>
Date: Sat, 17 Apr 2004 23:44:59 +0200
Hello,

the attached capture contains packets part of a unique TCP connection.

Using the TCP conversation function on this capture, the EP2 address and
port are not the destination address and port but the source address and
port.

I though that in the TCP conversation, EP1 was supposed to represent the
source address and EP2 the destination address (i.e, EP1 is the host
that connects to EP2) but in the attached capture, that's not the case?

Is my understanding of the TCP conversation function wrong?

Thanks in advance,

Jean-Baptiste Marchand
-- 
Jean-Baptiste.Marchand@xxxxxx
HSC - http://www.hsc.fr/

Attachment: conv_list_tcp_connect_incorrect_direction.cap.gz
Description: application/gunzip