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: Thu, 08 Dec 2016 16:55:42 +0000

Comment # 10 on bug 13213 from 
(In reply to Parav Pandit from comment #9)
> (In reply to Chuck Lever from comment #7)
> > The current logic in packet-rpc.c treats PT_TCP and PT_IBQP the same, and
> > expects that the pinfo will be set up so that:
> > 
> >   In the client-to-server direction: < addr A, port A, addr B, port B >
> > 
> >   In the server-to-client direction: < addr B, port B, addr A, port A >
> > 
> > But for PT_IBQP, we have:
> > 
> >   In the client-to-server direction: < addr A, -1, addr B, dest QPN B >
> > 
> >   In the server-to-client direction: < addr B, -1, addr A, dest QPN A >
> > 
> 
> My patch has src_qp instead of -1 for srcport.

I assume "My patch" == the packet-infiniband.c hunk from change 19107

I don't know what "src_qp" is. Only destination QPNs appear on the wire.
Perhaps we should stick with calling these destination QPNs. Where are you
getting these QPNs?

How does 19107's packet-infiniband.c hunk behave with packet-rpc.c and, say,
the sample wire capture excerpt attached to this bug?

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