protocols running atop ACL/L2CAP needs to be able to track pdus based on
authorsahlberg <sahlberg@f5534014-38df-0310-8fa8-9805f1628bb7>
Fri, 26 May 2006 08:30:56 +0000 (08:30 +0000)
committersahlberg <sahlberg@f5534014-38df-0310-8fa8-9805f1628bb7>
Fri, 26 May 2006 08:30:56 +0000 (08:30 +0000)
commite55c9c2e55cd04b6dc11f627fc85f7a387817c82
treec49f9891ab2c184d7517f0a66858c7ea1e210ef1
parent8b4f95d66d99e01c8e9c0831bfe564856910db41
protocols running atop ACL/L2CAP needs to be able to track pdus based on
acl chandle + direction + l2cap-CID    to uniquely identify a single specific
flow of PDU packets.

So we need to pass the chandle upp from acl to l2cap at least.

It would have been nice to handle this using "conversations" but the bluetooth
stack does not eaily map to the idiom host:port<->host:port

instead in bluetooth you have unidirectional flows that are identified by ACL-chandle:L2CAP-CID:direction     and additional state held inside l2cap  would attach two such flows together into a "conversation".
Bluetooth packets themself    only indentify "half" of the two way conversation.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@18218 f5534014-38df-0310-8fa8-9805f1628bb7
epan/dissectors/Makefile.common
epan/dissectors/packet-bthci_acl.c
epan/dissectors/packet-bthci_acl.h [new file with mode: 0644]