Wireshark-bugs: [Wireshark-bugs] [Bug 13213] RPC dissector doesn't match Replies to Calls with R
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 20 Dec 2016 22:49:12 +0000

Comment # 17 on bug 13213 from 
(In reply to Chuck Lever from comment #16)
> (In reply to Michael Mann from comment #15)
> (In reply to Chuck Lever from
> comment #13)
> > I may have prematurely confirmed this fix. I'm finding that
> this is still a
> > problem in TShark (Wireshark) 2.3.0
> (v2.3.0rc0-1823-gef92e9f).
> 
> Did you ensure you used -2 option in TShark
> (request/reply data typically
> needs 2 passes to work)?

I've never had to
> use -2 with NFS/TCP, didn't even know that option was there. However, the
> problem seems to be intermittent. Still investigating.

Wireshark always does 2 passes over every packet (first pass is every packet in
order, 2 pass isn't guaranteed to be in that order).
TShark defaults to a single pass before output, which can affect dissectors
that have state processing involving multiple packets, because not all packets
are guaranteed to arrive in order.  So when you want request/response data,
always pass -2 to TShark.

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