aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-bthci_acl.c
AgeCommit message (Collapse)AuthorFilesLines
2008-02-03From Shane Kearns (bug 2237):Stig Bjørlykke1-0/+1
Added support for Symbian OS btsnoop. The bluetooth HCI layer in Symbian OS can be configured to log all packets to a file. The log format, "btsnoop" is based on the RFC1761 "snoop" format - but differences in the header make it incompatible. The btsnoop format supports logging of these formats: "H1" (raw HCI packets without framing) "H4" (HCI UART packets including packet type header) "H5" (HCI 3 wire UART packets including framing) "BCSP" (HCI bluecore serial protocol including framing) "H1" and "H4" are section numbers in the original v1 bluetooth specifications, but still used colloquially - wireshark's existing support for Linux bluez HCI logs uses the "H4" name. In practice, the "H1" format is used for H5,BCSP and USB HCI logs, as the HCI packet logs are mainly useful for debugging higher layers, bluetooth profiles and bluetooth applications. From me: Deleted some unused prototypes. Mark an unused parameter. svn path=/trunk/; revision=24263
2007-03-26From Sebastien Tandel Ronnie Sahlberg1-3/+3
fixes for various compiler warnings svn path=/trunk/; revision=21210
2006-12-07As ponted out by Stig Bjørlykke change a whole bunch of dissector_handle_t ↵Anders Broman1-1/+1
to static. svn path=/trunk/; revision=20062
2006-08-14rename some structures and defines from the se_tree to the emem_tree prefixRonnie Sahlberg1-4/+4
svn path=/trunk/; revision=18894
2006-05-27add reassembly of bluetooth ACL packetsRonnie Sahlberg1-105/+102
doing the reassembly internally in acl instead of calling reassembly.c since the fragmentation is so simple and packets are so small anyway so full reassembly.c support would be overkill. svn path=/trunk/; revision=18223
2006-05-26protocols running atop ACL/L2CAP needs to be able to track pdus based onRonnie Sahlberg1-0/+7
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. svn path=/trunk/; revision=18218
2006-05-21change a whole bunch of ethereal into wiresharkRonnie Sahlberg1-3/+3
svn path=/trunk/; revision=18196
2006-05-14add bluetooth acl dissectionRonnie Sahlberg1-0/+294
the fragment reassembly from the old patch is commented out since it has to be redone completely using emem and se_trees the proper way. but to do this i would need example captures of fragmented bluetooth traffic first. svn path=/trunk/; revision=18149