Hello
I use SImtrace for developing and debugging Java SIM Applet.
The device is pretty good, but there are some APDU errors while SIM
sniffing.
is it possible to fix APDU errors sniffing errors?
I am attaching example dump with errors.
Some times, simtrace stop receiving APDU and continue just after
restart simtrace process.
--
Fedorov Alexander
Head of IT-solution department
LLC "Svyazcom"
Mobile: +7-908-212-98-05http://www.svyazcom.ru/en/E-mail:wind3style@gmail.com
<http://www.svyazcom.ru>
Dear Osmocom,
I have a question about the latest build of the simtrace2 based on the AT91SAM3..
Currently we have assembled some boards based on the v1.5 design of the Simtracer received from the git repository git.osmocom.org/simtrace (branch v1.5)
If have tried to compile the firmware of the repository git.osmocom.org/simtrace2 But I run in to some issue after the firmware is loaded.
Also I am not able to find the simtrace2 tool to do simtracing after compilation in the host directory ..
Is this firmware working already ? (The website @sysmocom says "SIMtrace 2" will be available from late March 2018)
Or am I missing something ?
Thanks in advance..
Met vriendelijke groet/С наилучшими пожеланиями/With kind regards,
[V-Tell]
Gerard Bakker | ICT / Voice Engineer
V-Tell Netherlands
Glotell Telecom B.V.
NL-Office +31 63 513 51 23
Willem Dreeslaan 37
NL-Mobile +31 64 202 21 06
2729 ND Zoetermeer, NL
RU-Mobile +7 958 964 19 98
www.v-tell.nl<http://www.v-tell.nl/>
US-Mobile +1 202 370 70 38
gerard.bakker(a)v-tell.nl<mailto:gerard.bakker@v-tell.nl>
This message contains confidential information and is intended only for the individual named. Its content may not be disclosed, copied or transferred to any (third) party in whole or in part without the prior written permission of Glotell B.V. Please notify the sender immediately if you have received this email by mistake and delete this email from your system.
Please do not print this email unless it is necessary. It helps to keep the environment forested and litter-free.
Dear all,
I've just merged changes that will automatically build the latest (tagged version)
packages and nightly packages for simtrace2.git for firmware and host utilities.
The "latest" have already been triggered:
https://build.opensuse.org/package/show/network:osmocom:latest/simtrace2
"nightly" will be available after the next automatic build (7:49 PM UTC)
For more information about osmocom nightly and latest binary packages, see
https://osmocom.org/projects/cellular-infrastructure/wiki/Binary_Packages
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear Osmocom community,
the first schedule of the 2018 incarnation of OsmoCon 2018 has been announced,
see http://osmocom.org/news/99 for the announcment and
https://pretalx.sysmocom.de/osmocon2018/schedule/ for the actual schedule.
At OsmoCon, we are not targetting developers, but more the wider community
and Osmocom users. It would be great to meet many of you and hear more
about your relation to Osmocom.
Tickets are available from https://pretix.sysmocom.de/sysmocom/osmocon2018/,
and until August 31st the early bird discount still applies.
For those with a community / "just for fun" background and no employer
that would cover the ticket, we have a number of subsidized community discount
vouchers available. See the OsmoCon 2018 wiki page at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018
for more information.
Looking forward to meeting as many of you as possible in roughly two
months from now,
Harald Welte
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
I've got my hands on a simtrace2 device - first of all thanks for your
great work and thanks for making this project open source!
So far I've tried out the sniffing functionality which is working
flawlessly - however I struggle to get the remote-sim functionality working.
I've built (make BOARD=simtrace APP=cardem) the cardemulation-firmware of
the current master-branch (0.4.131-8f70) and flashed the resulting
simtrace-cardem-dfu.bin using dfu-util.
Furthermore I compiled the host binaries, triggered a reset on my simtrace2
device to make sure it's in runtime mode and then executed the remote-sim
program (sudo ./simtrace2-remsim -V 1d50 -P 60e3 -C 1 -I 0 -A `sudo
./simtrace2-list | cut -d = -f 2 | cut -d , -f 1 | tail -1`). The simtrace2
device, as well as an USB-CCID compliant omnikey cardreader are attached to
my linux computer as described in the QMOD manual. During runtime mode the
red LED on the simtrace2 is blinking, while the green LED is off.
I noticed that when the simtrace2-remsim program tries to send an ATR to
the simtrace2 device via usb (cardem_request_set_atr), the
libusb_bulk_transfer function is blocking, before returning
LIBUSB_ERROR_TIMEOUT. The serial debugging-output I got on the simtrace2
doesn't show any futher information (last state is "-I- USB is now
configured").
When I reset the usb-modem that is connected to the simtrace2 device I get
the following messages on the debug-serial:
-I- Changed to ISO 7816-3 state 1
reset de-asserted
-I- WT updated to 9600
-I- Changed to ISO 7816-3 state 0
reset asserted
-I- Changed to ISO 7816-3 state 1
reset de-asserted
[...]
while the simtrace2-remsim program is also receiving some garbage:
URB:
-> 03 00 00 00 00 00 0c 00 04 00 00 00
unknown simtrace msg type 0x00
URB:
-> 03 00 00 00 00 00 0c 00 08 00 00 00
unknown simtrace msg type 0x00
URB:
-> 03 00 00 00 00 00 0c 00 04 00 00 00
unknown simtrace msg type 0x00
[...]
I've also tried several older versions/commits - however I didn't get any
of them working properly.
When using version 0.4.13-ba2a (from this commit:
https://git.osmocom.org/simtrace2/commit/?id=ba2ad563cc0e389213a3f6f6ebe79d…)
I was able to send the ATR to the simtrace and directly entered the main
loop on the host program.
The serial debugging-output (after a manual modem-reset) also looked
somehow more promising, but didn't work either:
-I- 0: VCC activated
-I- 0: CLK activated
-I- 0: RST released
-I- 0: computed Fi(1) Di(1) ratio: 372
-I- 0: send_tpdu_header: 00 a4 00 04 02
-I- 0: VCC deactivated
-I- 0: CLK deactivated
-I- 0: VCC activated
-I- 0: CLK activated
-I- 0: VCC deactivated
-I- 0: CLK deactivated
[...]
I've also tried a few different modems/dongles (Huawei, ZTE) which also
didn't really change anything.
Am I missing something? Is the remote-sim functionality supposed to work on
the current master branch? If not, could anyone hint me to a version/commit
that should work?
Would love to get some feedback - thanks in advance and keep up the good
work!
Greetings from Vienna,
Gabriel
