From: Todd Sabin [mailto:tas@xxxxxxxxxxx]
Sent: Friday, July 20, 2001 2:21 PM
> Next issue: conversation support for SMB. The dcerpc dissector needs
> to keep track of some things per conversation.
.....
> Now, without some support for SMB in the conversation stuff, dcerpc is
> going to think it's all one TCP conversation, when it's really two SMB
> conversations. I think that we might be able to use the SMB file/pipe
> number as the 'port' of the conversation, but I haven't looked into
> the conversation stuff too deeply. Anyone more familiar with it care
> to render advice?
This will work if you create a new conversation "port_type" for the
SMB file/pipe number. Check packet_info.h for the declaration of the
port_type enum. I don't know if there are other issues with the SMB
protocol that will cause problems.
Jeff Foster
jfoste@xxxxxxxxxxxx
***
The information in this e-mail is confidential and intended solely for the
individual or entity to whom it is addressed. If you have received this
e-mail in error please notify the sender by return e-mail, delete this
e-mail, and refrain from any disclosure or action based on the information.
****