Hi Michal, On Wed, Oct 03, 2012, Michal.Labedzki@xxxxxxxxx wrote: > > 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. > > Johan, I guess Wireshark support decoding what do you need (expect > ongoing tasks). If you have another idea how do decoding, please share > it. Power of Wireshark is: I think you must have misunderstood what I was trying to say. Did you actually look into what the monitor socket we talked about is? I wasn't trying to say wireshark shouldn't be used (so no point in iterating it's benefits - you've already convinced me) but that its Bluetooth decoding support be ported from traditional HCI sockets to use monitor sockets instead. This wouldn't give us any new decoders to wireshark but it would allow early HCI traffic decoding (e.g. on plugged in USB dongles) which isn't possible with current wireshark or hcidump and context discovery when tracing is started after there already exists connections. Considering these benefits monitor sockets compared to HCI ones is it something you might be interested in implementing? 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
