Ethereal-dev: [Ethereal-dev] Re: [Ethereal-cvs] rev 13827: /trunk/epan/dissectors/: packet-sct
Hi Guy,
I missed to commit that file...
however this brings up a question I raised before but did not get an
answer.
If a tap needs port numbers and addresses of a packet should these be
provided by the data passed to the tap or should the tap code get the
data from the pinfo variable?
Another question related to the last commit:
What is a 'conversation'?
For TCP a conversation seems to be a TCP connection. But what is a
conversation
for SCTP? An SCTP association (=connection) has one port number on each
side (like
TCP) but a list of IP-addresses. So does one SCTP association with n
and m addresses
at each side correspond to one conversation or n*m conversations?
Best regards
Michael
On Mar 20, 2005, at 19:59 Uhr, guy@xxxxxxxxxxxx wrote:
User: guy
Date: 2005/03/20 12:59 PM
Log:
Put the ports and addresses into "struct _sctp_info", as the dissector
fills them in.
Directory: /trunk/epan/dissectors/
Changes Path Action
+6 -1 packet-sctp.h Modified
http://anonsvn.ethereal.com/viewcvs/viewcvs.py?rev=13827&view=rev
_______________________________________________
Ethereal-cvs mailing list
Ethereal-cvs@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-cvs