Wireshark-bugs: [Wireshark-bugs] [Bug 3950] NHRP improvements
Date: Fri, 11 Sep 2009 11:48:07 -0700 (PDT)

--- Comment #6 from Chris Maynard <[email protected]>  2009-09-11 11:48:03 PDT ---
(In reply to comment #5)
> If you could come up with a way to extend it to all protocols not just NHRP, it
> would be even better :)
Yeah, that seems to be the general consensus from various postings I've seen on
the developer's list.  I think first it requires a more generic way to create a
conversation than what we have today.  Each protocol ought to be able to define
its own semantics for what a conversation is.  For ICMP, that's likely an IP
pair plus ID.  For NHRP, it's the Request Src IP matching the Reply Dst IP, and
on and on for every protocol.

BTW, the change Didier suggests to conversation usage is probably a good idea
too.  See https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2907.

Then the second thing probably needed is a more generic way to track requests &
responses within the established conversation.  For ICMP Echo Request/Replies,
that would be a matching Seq #.  For NHRP, that would be a matching Request ID.
 And on & on for the rest. 

> I've been meaning to add such tracking to the ICMP dissector, but haven't
> gotten around to it.  I think it's a good idea too and putting it in the
> statistics API could be useful too.
Agreed.  I haven't done anything with statistics before so I'm not sure what I
would be getting myself into, but in any case, the same type of results that
"ping" provides would be useful I think, i.e., min/avg/max RTT's, Hop Count,
and % packet loss.  I wonder if in addition to any conversation change that
might be made or generic request/response API added, that a third useful thing
would be a generic way to add statistics for the request/response tracking.

Rather than continuing this discussion within the context of this now closed
bug, maybe it's better to move it to the developer's list or to a wiki page?

Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.