Wireshark-bugs: [Wireshark-bugs] [Bug 8581] NFS Dissector : More intuitive and less ambiguous va
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 15 Apr 2013 12:20:15 +0000

changed bug 8581

What Removed Added
CC   mmann78@netscape.net

Comment # 11 on bug 8581 from 
(In reply to comment #10)
> - The
> "<field_name> duplicates PROTOABBREV of nfs" errors are true in the
> case
>
> of nfs.nfsstat3, nfs.nfsstat4, and hf_nfs_nfsstat all of which set 
>  
> PROTOABBREV to "Reply status" but there is nothing wrong with that. 
>  
> Shouldn't we just ignore those warnings (or remove that check from the 
>  
> script?) =)   

I think it's just that nfs.stat3 makes more sense than
> nfs.nfsstat3 or nfs.nfs.nfsstat3 etc. unless those names make more sense
> with reference to the protocol (I don't know a whole lot about NFS internals
> to be honest). They're not a big deal, I just thought they might be worth
> fixing while we're doing cleanup.

I keep running into this (when running the script on all dissectors) and keep
coming to the conclusion that nfs.nfsstat3 (and similar) is appropriate despite
my ignorance of the protocol.  It appears there are different types of "status"
and one of the "status types" is "nfs".  While there isn't an official list of
known false positives from the script, these certainly fall in that category.

You are receiving this mail because:
  • You are watching all bug changes.