Harald Welte
a32c769bb7
This forwards the raw DIAG messages via GSMTAP, so the receiver (e.g. wireshark) will have to do a full DIAG protocol decode. I currently prefer this idea to that of converting only the protocol payload to "native" GSMTAP messages like GSMTAP_UM. One of the problems is that the LAPDm headers are alrady stripped, and we would have to re-add fake LAPDm headers to generate GSMTAP_UM. So let's rather forward all information we have and let wireshark deal with it. I'm not entirely sure if this is the best strategy, but we can always implement both modes and switch between them at runtime. |
||
---|---|---|
doc | ||
src | ||
.gitignore | ||
COPYING | ||
HISTORY | ||
README | ||
TODO |
README
Utility to configure Qualcomm DIAG, read, decode and display the DIAG messages. It can enable logging and format/print the log messages generated by the various subsystems of the baseband. To build this software a copy of the Osmocom libosmocore library is required. Your distribution might already contain the necessary utility. In general all Qualcomm devices that export DIAG should be supported. We have tested it with the Quectel UC20, EC20 and EC25 devices.