<div dir="ltr"><div dir="ltr"><div>Helli,</div><div><br></div><div dir="ltr">I also tried the compiling and accessing instructions as described in <a href="https://osmocom.org/projects/simtrace2/wiki">https://osmocom.org/projects/simtrace2/wiki</a>, but I am facing following issues there too.</div><div dir="ltr"><br></div><div>1) I am unable to download the packages libosmocore-dev libpcsclite-dev.</div><div>Err:1 <a href="http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_18.04">http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_18.04</a> ./ libosmocore12 1.1.0.12.1850<br> 404 Not Found [IP: 195.135.221.134 80]</div><div>2) I am not able to compile. make does'nt run.<br></div><div>3) Un able to detect the simtracer2 with <br clear="all"><pre>./simtrace2-list<br><br></pre><pre>Could any one please guide and help me to set this up.<br></pre><pre><br></pre></div><div dir="ltr"><div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span>Best regards,<br><div>M.Sc. Sunil Hebbur Srikantamurthy</div><div>Chair of Communication Networks<br></div><div>Electrical Engineering and Information Technology</div><div>
Chemnitz University of Technology </div></span></div></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 14, 2019 at 4:47 PM Sunil Hebbur Srikantamurthy <<a href="mailto:sunil.srikantamurthy1990@gmail.com">sunil.srikantamurthy1990@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hello,</div><div><br></div><div>I would like to just use the simtracer 2. Could you please provide me detailed steps to sniff the traffic. Should I download all the files? <br></div><div>Would the command simtrace2-sniff work on the go.</div><div><br></div><div>Thank you.</div><div><br></div><div><div><div><div><div dir="ltr" class="gmail-m_9120166766189036778gmail_signature"><div dir="ltr"><div><div dir="ltr"><span>Best regards,<br><div>M.Sc. Sunil Hebbur Srikantamurthy</div><div>Chair of Communication Networks<br></div><div>Electrical Engineering and Information Technology</div><div>
Chemnitz University of Technology </div></span></div></div></div></div></div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 14, 2019 at 4:11 PM Harald Welte <<a href="mailto:laforge@gnumonks.org" target="_blank">laforge@gnumonks.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi J. Felix and Sunil,<br>
<br>
I'm wondering: Are you actually intending to do development on the SIMtrace2<br>
software, or do you just want to use it?<br>
<br>
If you just want to use it, why not simply use the osmocom packages provided<br>
for Ubuntu 18.04 at<br>
<a href="http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_18.04/" rel="noreferrer" target="_blank">http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_18.04/</a><br>
as explained at<br>
<a href="https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds" rel="noreferrer" target="_blank">https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds</a><br>
<br>
Building from source should generally only be done by developers who want<br>
to contribute to development/extension of the software. And for those, I would<br>
sort-of expect that they know how to do system-level C development on Linux,<br>
including auto-tools, pkg-config, etc.<br>
<br>
Regards,<br>
Harald<br>
-- <br>
- Harald Welte <<a href="mailto:laforge@gnumonks.org" target="_blank">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/" rel="noreferrer" target="_blank">http://laforge.gnumonks.org/</a><br>
============================================================================<br>
"Privacy in residential applications is a desirable marketing option."<br>
(ETSI EN 300 175-7 Ch. A6)<br>
</blockquote></div>
</blockquote></div>