forked from osmocom/wireshark
technically speaking rpc duplicate replies are not retransmissions
only the request is tecnically a restransmission the reply is technically not a retransmission (since it is a new reply to the retransmitted request) mark duplicated replies as RPC duplicate ... instead of as RPC retransmission thanks to Cal for pointing this out. svn path=/trunk/; revision=10725
This commit is contained in:
parent
a250c638a9
commit
53d2b88279
|
@ -2,7 +2,7 @@
|
|||
* Routines for rpc dissection
|
||||
* Copyright 1999, Uwe Girlich <Uwe.Girlich@philosys.de>
|
||||
*
|
||||
* $Id: packet-rpc.c,v 1.143 2004/04/07 03:57:34 sahlberg Exp $
|
||||
* $Id: packet-rpc.c,v 1.144 2004/04/29 11:58:00 sahlberg Exp $
|
||||
*
|
||||
* Ethereal - Network traffic analyzer
|
||||
* By Gerald Combs <gerald@ethereal.com>
|
||||
|
@ -2255,7 +2255,7 @@ dissect_rpc_message(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
|
|||
Mark it as such. */
|
||||
if (check_col(pinfo->cinfo, COL_INFO)) {
|
||||
col_prepend_fstr(pinfo->cinfo, COL_INFO,
|
||||
"[RPC retransmission of #%d]", rpc_call->rep_num);
|
||||
"[RPC duplicate of #%d]", rpc_call->rep_num);
|
||||
}
|
||||
proto_tree_add_item(rpc_tree,
|
||||
hf_rpc_dup, tvb, 0,0, TRUE);
|
||||
|
|
Loading…
Reference in New Issue