At least some versions of the OS X NFS client (and possibly some if not
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 20 Oct 2004 23:38:31 +0000 (23:38 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 20 Oct 2004 23:38:31 +0000 (23:38 +0000)
commit32f449a0da4fc913f36fbbcbc413c100f477b6be
tree7545d1345ffc6b1c129c8cd6b0b51cda9cd08994
parenteb2010149df1955ad83b03cb17b6efdb36be6e68
At least some versions of the OS X NFS client (and possibly some if not
all other BSD NFS clients) retransmit on different ports from the port
on which the original request was set, so have the RPC "conversation"
for connectionless protocols use only the source address and destination
port.

Use NO_ADDR_B and NO_PORT_B when looking up the conversation in those
cases, and use NO_ADDR2 and NO_PORT2 when creating the conversation in
those cases, to make it clearer that we're only using one address and
port.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@12362 f5534014-38df-0310-8fa8-9805f1628bb7
epan/dissectors/packet-rpc.c