Put the code to handle NDS ping replies and NDS replies into routines of
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 25 Oct 2005 06:20:46 +0000 (06:20 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 25 Oct 2005 06:20:46 +0000 (06:20 +0000)
commit6a7c485a17af951e38ab87e8d3a51ec287bafe62
treefc7189e7b7d2fe3b35b3925e04580927ca35e4a2
parentbccc0fcb980c950c2ff43e5d8e1448c4be3315ef
Put the code to handle NDS ping replies and NDS replies into routines of
their own.

Do the tapping as early as possible, so it's done even if exceptions are
thrown - and do it regardless of whether the tree argument is null or
not, because a tap might be run without generating protocol trees.

Generate the expert info regardless of whether the tree arugment is null
or not, as that's also used with taps.

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