This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom Tools for Qualcomm Diag". The branch, master has been updated via 4e5338bc4963efe31609db5e7fdaf0cd96c600ec (commit) via 9e02b556d79ee4153f9ea2ffa59ca32270ac945d (commit) via 78b8bda6f6ad12fbbed8238e4783c9561b1a2a04 (commit) via 7e6d71ea74d4c1d9f628dfcf1289180e50ceabca (commit) via b8a70980b691e19661840529b2c6b2c28db0aa1f (commit) via 5fa552cbd386b7e32f219648ae7a4e46bededa43 (commit) via a32c769bb7c71c71376cfb934082c07272cfe0c3 (commit) via a115fbb1bbfeec9c6a10ac2ea2999e23be77336a (commit) from 4ae09361234ef6dff29548a528b9dfeba0329da6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-qcdiag/commit/?id=4e5338bc4963efe31609db5e7fda… commit 4e5338bc4963efe31609db5e7fdaf0cd96c600ec Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jan 8 16:03:06 2017 +0100 WIP: SIM Card logging I'm getting related messages from the modem, but I somehow cannot decode the traces so far at all :/ http://cgit.osmocom.org/osmo-qcdiag/commit/?id=9e02b556d79ee4153f9ea2ffa59c… commit 9e02b556d79ee4153f9ea2ffa59ca32270ac945d Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jan 8 14:43:45 2017 +0100 fix diag_umts_rrc_chtype and add more diag_log_code_wcdma http://cgit.osmocom.org/osmo-qcdiag/commit/?id=78b8bda6f6ad12fbbed8238e4783… commit 78b8bda6f6ad12fbbed8238e4783c9561b1a2a04 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jan 8 14:03:04 2017 +0100 fix gen_log_config_set_mask() We were missing the last byte in the log config mask, resulting in unintended behavior. http://cgit.osmocom.org/osmo-qcdiag/commit/?id=7e6d71ea74d4c1d9f628dfcf1289… commit 7e6d71ea74d4c1d9f628dfcf1289180e50ceabca Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jan 8 13:47:13 2017 +0100 also log config request/response messages via GSMTAP http://cgit.osmocom.org/osmo-qcdiag/commit/?id=b8a70980b691e19661840529b2c6… commit b8a70980b691e19661840529b2c6b2c28db0aa1f Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jan 8 13:45:54 2017 +0100 patch %s out of format strings received from phone %s can obviously not work, as we have no access to the targets memory space on the host PC. I guess the programmers adding those log lines have done so in error. Let's replace %s with %p in the format string. http://cgit.osmocom.org/osmo-qcdiag/commit/?id=5fa552cbd386b7e32f219648ae7a… commit 5fa552cbd386b7e32f219648ae7a4e46bededa43 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jan 7 21:21:35 2017 +0100 separate diag_log_umts to diag_log_wcdma Qualcomm differentiates between WCDMA (the access stratum) and UMTS (the non access stratum). Let's reflect that here. As an added bonus, we get working NAS protocol traces. http://cgit.osmocom.org/osmo-qcdiag/commit/?id=a32c769bb7c71c71376cfb934082… commit a32c769bb7c71c71376cfb934082c07272cfe0c3 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jan 7 16:01:09 2017 +0100 Generate GSMTAP messages from raw received DIAG frames 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. http://cgit.osmocom.org/osmo-qcdiag/commit/?id=a115fbb1bbfeec9c6a10ac2ea299… commit a115fbb1bbfeec9c6a10ac2ea2999e23be77336a Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jan 7 16:27:50 2017 +0100 diag_read_msg(): Discard any messages shorter than 3 bytes The 16bit CRC and the FLAG octet together are 3 bytes. If a message is shorter than that, something is going wrong, for sure. ----------------------------------------------------------------------- Summary of changes: src/Makefile | 2 +- src/diag_io.c | 23 ++++++++++++++++++++ src/diag_io.h | 1 + src/diag_log.c | 14 ++++++++++-- src/diag_log_gprs.c | 5 +++++ src/{diag_log_gsm.c => diag_log_simcard.c} | 34 +++++++++++++++--------------- src/diag_log_umts.c | 19 ++++++----------- src/{diag_log_umts.c => diag_log_wcdma.c} | 8 +------ src/diag_msg.c | 6 ++++++ src/osmo-qcdiag-log.c | 1 + src/protocol/diag_log_1x.h | 6 ++++++ src/protocol/diag_log_umts.h | 29 +++++++++++++++++++++++++ src/protocol/diag_log_wcdma.h | 12 +++++++---- 13 files changed, 116 insertions(+), 44 deletions(-) copy src/{diag_log_gsm.c => diag_log_simcard.c} (54%) copy src/{diag_log_umts.c => diag_log_wcdma.c} (73%) create mode 100644 src/protocol/diag_log_umts.h hooks/post-receive -- Osmocom Tools for Qualcomm Diag