Wireshark-bugs: [Wireshark-bugs] [Bug 4169] New: wireshark doesn't recognize NFS4 callbacks

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 27 Oct 2009 03:25:02 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4169

           Summary: wireshark doesn't recognize NFS4 callbacks
           Product: Wireshark
           Version: 1.2.2
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: guillomovitch@xxxxxxxx


Build Information:
Hello.

The attached capture file show 6 attempt to recall a NFSv4 callback, as
attested by the client logs:
Oct 27 10:48:12 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27838
NFSv4 callback!
Oct 27 10:48:13 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27839
NFSv4 callback!
Oct 27 10:48:15 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27840
NFSv4 callback!
Oct 27 10:48:18 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27841
NFSv4 callback!
Oct 27 10:48:22 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27842
NFSv4 callback!
Oct 27 10:48:27 stalingrad nfs_callback_authenticate: 193.55.250.11, port=27843
NFSv4 callback!

However, wireshark wrongly identifies those packets as STUN2 protocol.
--


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