Hi Michal, On Fri, Sep 28, 2012, Michal.Labedzki@xxxxxxxxx wrote: > I am trying to add full Bluetooth support to a Wireshark. Wireshark can be > used as replacement for "hcidump" or other GUI applications for displaying > Bluetooth frames/packets. > > Currently Wireshark support: > 1. Sniffing via Bluetooth dongle > 2. Protocols/Profiles: > HCI (without BLE) > L2CAP > SDP (little broken) > RFCOMM 1.1 > OBEX (so all OBEX profiles can be treat as supported) > AMP > HID 1.0 > SAP 1.1 > BNEP 1.0 > AVCTP 1.4 > AVRCP 1.5 > > At this moment I am working on: (finishing) > 1. ATT > 2. HCRP > 3. MCAP > 4. AVDTP/A2DP/VDP Have you looked into supporting the new HCI_CHANNEL_MONITOR available in recent kernels? There's a very simple "btmon" command-line tool for it in bluez.git (see e.g. monitor/control.c) but it can't do any kind of high-level decoding (e.g. profiles). It'd be interesting to know if it could be easily supported in wireshark since right now there doesn't seem to be a viable way of porting decoders from hcidump to btmon due to their very different ways of handling buffers etc. One of the big benefits of the monitor channel compared traditional HCI sockets is that you get dynamic notifications of added and removed adapters including the very early HCI traffic that occurs. In the long run I think the idea is to add also "replay" connection events for existing ACL and L2CAP links so that you'd get the right protocol decoded even if you start logging when the connection already exists. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
