Comment # 16
on bug 13213
from Chuck Lever
(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.
You are receiving this mail because:
- You are watching all bug changes.