I too was just looking for this feature today. I thought that I stumbled
upon it with -O. However, that doesn't *only* print detailed information
for the specific protocol. It also prints the summary lines for other
protocols. Maybe that's a jumping off point?
Thanks,
Rick
On Tue, Aug 7, 2012 at
I'm playing around with a customized diameter profile with respect to the
columns. I'm getting different results between the command code and the
result code.
If I add a new custom column for the result code, it gets presented as its
enumerated value. So instead of 2001 it prints
I'm trying to pre-package some MIB files for the company here and smi.dll is
causing an error. I created a directory variable in config.nmake that holds
the MIB files. I edited Makefile.nmake below '!IFDEF SMI_DIR...!ENDIF' and
added the following:
!IFDEF MY_DIR
if not exist
Suppose I've got a protocol that is simply XML running over TCP. I know that
Wireshark is capable of dissecting XML data from HTTP packets, etc. What's
the shortest/easiest way to dissect a conversation just as XML? Does it
require a new XML dissector?
Rick
I wanted to second the issue of crashing with DNS Wireshark compiled with
MS005EE. I have similar symptoms where captures without name resolution went
fine. However, when name resolution was enabled, it would crash after a few
packets were captured. If there's a potential solution that needs
