There can be more than one DCE RPC call per frame, e.g. there can be

multiple NetBIOS-over-TCP session service messages in a TCP segment, and
they can contain the final portions of different DCERPC calls.  Don't
assume a frame number is sufficient to identify DCE RPC calls.


git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@7777 f5534014-38df-0310-8fa8-9805f1628bb7

1 files changed, 1 insertions, 6 deletions

diff --git a/smb.h b/smb.h
index 25afc94fdc..e3fe57a3b9 100644
--- a/smb.h
+++ b/smb.h
@@ -2,7 +2,7 @@
  * Defines for smb packet dissection
  * Copyright 1999, Richard Sharpe <rsharpe@ns.aus.com>
  *
- * $Id: smb.h,v 1.52 2003/04/13 23:58:37 guy Exp $
+ * $Id: smb.h,v 1.53 2003/06/04 05:41:37 guy Exp $
  *
  * Ethereal - Network traffic analyzer
  * By Gerald Combs <gerald@ethereal.com>
@@ -289,11 +289,6 @@ typedef struct conv_tables {
 	/* these two tables are used to match requests with responses */
 	GHashTable *unmatched;
 	GHashTable *matched;
-	/* this tables is used by DCERPC over SMB reassembly*/
-	GHashTable *dcerpc_fid_to_frame;
-	/* this table is to keep track of which frames we saw which dcerpc
-	   pdu in */
-	GHashTable *dcerpc_frame_to_dcerpc_pdu;	  
 
 	/* This table is used to track TID->services for a conversation */
 	GHashTable *tid_service;