Project

General

Profile

Actions

Support #4223

closed

Simtrace2-sniff fails to run

Added by josh2751 over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
host software
Target version:
-
Start date:
10/09/2019
Due date:
% Done:

100%

Spec Reference:

Description

When running simtrace2-sniff I get back

simtrace2-sniff - Phone-SIM card communication sniffer
(C) 2010-2017 by Harald Welte <>
(C) 2018 by Kevin Redon <>

Using USB device 1d50:60e3 Addr=3, Path=2-2, Cfg=1, Intf=0, Alt=0: 255/1/0 (SIMtrace Sniffer)
Entering main loop
preventing USB buffer overflow: Resource temporarily unavailable

The device is recognized properly by simtrace2-list, I’m running it on ubuntu 18.04 installed from the lastest build package of simtrace2-utils on opensuse.

Just looking for troubleshooting ideas.


Related issues

Has duplicate SIMtrace 2 - Support #4459: As for the problem of #4223, it still exists on the Rpi, could you provide some detailed guidance? Thank you!Rejected03/19/2020

Actions
Actions #1

Updated by roh over 4 years ago

are you running in some kind of virtual machine? (e.g. forwarding the usb device)

also it would be interesting to know which exact kernelversion you did try this on.

did you add the udev rule to allow access as regular user?

https://osmocom.org/projects/simtrace2/wiki#Accessing-it

kind regards

Actions #2

Updated by josh2751 over 4 years ago

roh wrote:

are you running in some kind of virtual machine? (e.g. forwarding the usb device)

also it would be interesting to know which exact kernelversion you did try this on.

did you add the udev rule to allow access as regular user?

https://osmocom.org/projects/simtrace2/wiki#Accessing-it

kind regards

Thanks for the reply! Answers below:

Yes, I'm running it under virtual box.

kernel version is 4.18.0-25

Yes, udev rules were installed.

Is there a known issue with running in a vm?

Actions #3

Updated by josh2751 over 4 years ago

roh wrote:

are you running in some kind of virtual machine? (e.g. forwarding the usb device)

also it would be interesting to know which exact kernelversion you did try this on.

did you add the udev rule to allow access as regular user?

https://osmocom.org/projects/simtrace2/wiki#Accessing-it

kind regards

I switched over to a Raspberry Pi, since I don't have another linux machine to test in front of me, installed it using apt there, and it does not crash running on that machine. However, it simply hangs when it's opened, it seems as though it's not taking control of the device. Simtrace2-list shows that the device is attached, but simtrace2-sniff outputs:

pi@raspberrypi:~ $ simtrace2-sniff
simtrace2-sniff - Phone-SIM card communication sniffer
(C) 2010-2017 by Harald Welte <>
(C) 2018 by Kevin Redon <>

and hangs at that point.

I should also note that it appears the Simtrace is working as the device I am attaching it to can communicate with the sim installed in it.

Actions #4

Updated by josh2751 over 4 years ago

Ok we can close this issue.

I pulled the source on the Rpi, commented out the while(1) argument loop in the main function and rebuilt it, and it does what I need it to now.

thanks!

Actions #5

Updated by roh over 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by laforge about 4 years ago

  • Status changed from Resolved to New
  • % Done changed from 100 to 70
Actions #7

Updated by laforge about 4 years ago

  • Has duplicate Support #4459: As for the problem of #4223, it still exists on the Rpi, could you provide some detailed guidance? Thank you! added
Actions #8

Updated by laforge about 4 years ago

  • Status changed from New to In Progress

I presume thsi was

josh2751 wrote:

Ok we can close this issue.

I pulled the source on the Rpi, commented out the while(1) argument loop in the main function and rebuilt it, and it does what I need it to now.

I presume this was referring to

       while (1) {
                int option_index = 0;

                char c = getopt_long(argc, argv, "hi:kV:P:C:I:S:A:", opts, &option_index);
                if (c == -1)
                        break;

What strikes me as odd is the 'char' type for 'c': getopt_long() returns an 'int'. So maybe changing that will do the trick?

Can any of you raspi users check?

Actions #10

Updated by gray_T about 4 years ago

Thank you very much!

Modified into

int c = getopt_long(argc, argv, "hi:kV:P: c :I:S:A:", opts, &option_index);

Now on the Rpi, I can use it.

Actions #11

Updated by laforge about 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

the patch has been merged. nightly packages from tomorrow onwards will have the fix.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)