The lack of _WITH_PHDR in WTAP_ENCAP_BLUETOOTH_H4 means there's no
authorGuy Harris <guy@alum.mit.edu>
Sat, 12 Feb 2011 19:59:41 +0000 (19:59 -0000)
committerGuy Harris <guy@alum.mit.edu>
Sat, 12 Feb 2011 19:59:41 +0000 (19:59 -0000)
commita595f69ce4ed6114beefc5d9e753c11ff7be1918
tree8f369db2ef33d817abf53f91afd6e9ce962db7b1
parentb83634d5a93cfda6f94ea2defe1940fd50f05c61
The lack of _WITH_PHDR in WTAP_ENCAP_BLUETOOTH_H4 means there's no
pseudo-header, and hence there's no direction indication. Don't set
pinfo->p2p_dir for it.  Use WTAP_ENCAP_BLUETOOTH_H4_WITH_PHDR, not
WTAP_ENCAP_BLUETOOTH_H4, for capture files where we have the direction.

Don't assume pinfo->p2p_dir is either P2P_DIR_SENT or P2P_DIR_RECV when
setting the info column in various Bluetooth dissectors; it might be
unknown.

In the HCI H4 dissector, put the direction into the info column
regardless of whether we have a type match or not; the dissectors for
HCI packet types appear to assume it's been set (as they put a blank at
the beginning of the stuff they append to the direction).

svn path=/trunk/; revision=35933
epan/dissectors/packet-btamp.c
epan/dissectors/packet-btl2cap.c
epan/dissectors/packet-btobex.c
epan/dissectors/packet-btrfcomm.c
epan/dissectors/packet-frame.c
epan/dissectors/packet-hci_h4.c
wiretap/btsnoop.c
wiretap/hcidump.c