Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092024-03-09T21:34:47ZOpen Source Mobile Communications
Redmine pySim - Bug #6398 (New): Add helper for SwMatchErrorhttps://osmocom.org/issues/63982024-03-09T21:34:47Zn4n5
<p>Hello</p>
<p>Here is a tiny patch to add the error interpreter to SwMatchError()</p>
<p>Btw I have another question :<br />What can we do when we have "Expected 9000 and got 6983: Command not allowed - Authentication/PIN method blocked" ?</p>
<p>Thanks</p> Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall) - Bug #6291 (New): 2024 event bringing tog...https://osmocom.org/issues/62912023-12-06T14:31:01Zlaforge
<p>I've been considering this for a number of years, but never actually got aroun to acting on it:</p>
<p>Have an event where the various FOSS mobile communications projects meet, get to know each other and exchange status, plans and ideas.</p>
<p>Matthias Kirschner of the FSFE suggested to <em>attach</em> that event to sfscon (<a class="external" href="https://www.sfscon.it/">https://www.sfscon.it/</a>) and do it a few days ahead (or after) the 2024 incarnation, which is likely happning again in November 2024. The FSFE could help with funding of the related expenses from a donation made by sysmocom to FSFE earmarked to help FOSS in mobile communications.</p>
<p>Let's use this issue to collect a list of projects we'd want to invite, and to generally keep track on status.</p>
<p>For now, I am thinking of the following potential projects:</p>
<a name="cellular-infrastructureprotocol-stacks"></a>
<h2 >cellular infrastructure/protocol stacks<a href="#cellular-infrastructureprotocol-stacks" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://osmocom.org/" class="external">Osmocom</a></li>
<li><a href="https://open5gs.org/" class="external">open5gs</a></li>
<li><a href="https://www.srslte.com/" class="external">srsRAN/srsUE</a></li>
<li><a href="https://free5gc.org/" class="external">free5gc</a></li>
<li><a href="https://github.com/edgecomllc/eupf" class="external">eupf</a></li>
<li><a href="https://github.com/travelping/ergw" class="external">ergw</a></li>
<li><a href="https://magmacore.org/" class="external">Magma</a> + <a href="https://github.com/magma/S1APTester" class="external">S1APTester</a></li>
<li><a href="https://github.com/omec-project" class="external">OMEC</a></li>
<li><a href="https://github.com/wmnsk" class="external">wmnsk</a> and his various go-{gtp,pfcp,m3ua,sccp,tcap} projects</li>
</ul>
<a name="SIM-card-related-projects"></a>
<h2 >SIM card related projects<a href="#SIM-card-related-projects" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://github.com/tomasz-lisowski/swsim" class="external">swsim</a> + <a href="https://github.com/tomasz-lisowski/swicc" class="external">swicc</a></li>
</ul>
<a name="Development-Debugging"></a>
<h2 >Development + Debugging<a href="#Development-Debugging" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://github.com/fgsect/scat" class="external">SCAT</a></li>
<li><a href="https://github.com/P1sec/QCSuper" class="external">QCsuper</a></li>
<li><a href="https://github.com/PentHertz/Modmobmap" class="external">Modmobmap</a></li>
<li><a href="https://github.com/SysSec-KAIST/LTESniffer" class="external">LTESniffer</a></li>
<li><a href="https://github.com/falkenber9/falcon" class="external">FALCON</a></li>
<li><a href="https://github.com/aligungr/UERANSIM" class="external">UERANSIM</a></li>
<li><a href="https://github.com/HewlettPackard/PacketRusher" class="external">PacketRusher</a></li>
<li>the various projects by <a href="https://github.com/fasferraz" class="external">fasferraz</a> (Swu-IKEv2, ...)</li>
<li><a href="https://github.com/P1sec/pycrate" class="external">pycrate</a></li>
</ul>
<a name="FOSS-software-stacks-on-mobile-devices"></a>
<h2 >FOSS software stacks on mobile devices<a href="#FOSS-software-stacks-on-mobile-devices" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://postmarketos.org/" class="external">postmarketos</a></li>
<li><a href="https://replicant.us/" class="external">replicant</a></li>
<li><a href="https://ubuntu-touch.io/" class="external">Ubuntu touch</a></li>
</ul>
<p>I'm very happy to accept further suggestions for projects/people to add to the invite list.</p> OsmoBSC - Bug #6019 (New): "PCU version PCU socket has LOST connection connected"https://osmocom.org/issues/60192023-04-28T12:17:03Zfixeria
<p>This is what I see in the output of <code>show bts</code> command:</p>
<pre>
OsmoBSC> show bts 0
BTS 0 is of osmo-bts type in band GSM900, has CI 0 LAC 1, BSIC 63 (NCC=7, BCC=7) and 1 TRX
Description: (null)
ARFCNs: 85
PCU version PCU socket has LOST connection connected
...
</pre>
<p>what means that somehow <code>bts->pcu_version[]</code> contains <code>PCU socket has LOST connection</code>. I am also seeing this in logging:</p>
<pre>
апр 28 19:14:07 DELL osmo-bsc[543401]: DNM NOTICE abis_nm.c:348 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version 1.2.0.31-33a1bf3
...
апр 28 19:14:10 DELL osmo-bsc[543401]: DNM NOTICE abis_nm.c:348 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version PCU socket has LOST connection
</pre>
<p>This looks a bit confusing, maybe we should just say "PCU state"?</p> osmo-fl2k - Bug #5918 (New): -flto broken in releasehttps://osmocom.org/issues/59182023-02-22T15:34:15Zzero_chaos
<p>Hi! It's been a while since your last tag, and some notable fixes have gone in. I know there isn't a ton of active development lately, but that seems like all the more reason for a fresh tag. I am currently testing link time optimization stuff in Gentoo, and came across this bug:<br /><a class="external" href="https://bugs.gentoo.org/861959">https://bugs.gentoo.org/861959</a><br />It seems to be fixed by <a class="external" href="https://gitea.osmocom.org/sdr/osmo-fl2k/commit/d56968352c626dda51552bb469ac23a8964d6d29">https://gitea.osmocom.org/sdr/osmo-fl2k/commit/d56968352c626dda51552bb469ac23a8964d6d29</a> , however, there seem to be a lot of additional desirable fixes.<br />Please consider tagging a new release.</p> OsmoMGW - Bug #5726 (New): AMR octet-align in SDP: lack of 'octet-align' fmtp should imply octet-...https://osmocom.org/issues/57262022-10-24T21:26:29Zneelsnhofmeyr@sysmocom.de
<p>OsmoMGW makes decisions for AMR octet-align vs bandwidth-efficient alignment depending on whether a fmtp parameter 'octet-align' is explicitly present or not.</p>
<p>IIUC the situation arises from the fact that until today, osmo-bsc and osmo-msc fail to set 'octet-align=1' in their MGCP.<br />It seems that osmo-mgw is trying to make amends for this error, that should instead be fixed in osmo-bsc and osmo-mgw.</p>
<p>In SDP, per spec, lack of the octet-align parameter must imply 'octet-align=0'. So if we now fix osmo-mgw to properly handle the 'octet-align' setting, we may suddenly break interworking with osmo-bsc and osmo-msc.</p>
<p>IIUC the intention is to convert between OA and BE only if the 'octet-align' parameter is explicitly present:</p>
<ul>
<li>"AMR" <-> "AMR": do not convert alignment</li>
<li>"AMR:octet-align=0" <-> "AMR:octet-align=1": convert alignment</li>
</ul>
<p>This seems like a good hack / legacy compat shim, but the effects are potentially catastrophic.<br />These are the problems:</p>
<ul>
<li>By allowing AMR OA on a conn where there is no fmtp configured, we are inviting confusion.<br /> For example, in the case "AMR" <-> "AMR:octet-align=1": do not convert alignment?<br /> Current code actually looks like we will only convert alignment in one direction, but not the other.</li>
</ul>
<ul>
<li>the lack of a fmtp for AMR is, per spec, <strong>identical</strong> to having 'octet-align=0' present.<br /> By handling the presence or absence of the fmtp as an indicator to change osmo-mgw's behavior, we are not compliant.</li>
</ul>
<ul>
<li>On each MGCP conn, there may be any number of different AMR configurations on either side.<br /> So depending on the PT number, we may receive / forward AMR OA or AMR BE interchangeably.<br /> For example, if osmo-msc forwards SDP from SIP that allows both OA and BE in two distinct payload type nrs,<br /> where OA has 'octet-align=1' and BE has no fmtp according to spec in the SDP from SIP,<br /> then osmo-mgw might interpret the AMR without fmtp as OA, even though it should be BE,<br /> and patch the wrong payload type number into outgoing RTP packets.<br /> (We could explicitly check whether both are featured, but that is another level of nightmare.)</li>
</ul>
<p>So I think we need to reach a situation where osmo-mgw behaves strictly conforming to spec,<br />not assuming OA as compat behavior if there is no fmtp with the AMR codec.<br />We need to teach osmo-bsc and osmo-msc to appropriately send 'octet-align=1' in the MGCP,<br />and we should switch osmo-mgw to handle these instructions accurately.<br />Maybe we need switch osmo-mgw to strict AMR behavior with a .cfg VTY option.</p> gr-osmosdr - Bug #5448 (New): a bug related to gqrx using gr-osmosdr for sdrplay rsp1 through soa...https://osmocom.org/issues/54482022-02-09T02:56:35Zagerasageras@tutanota.com
<p>There is a bug in gqrx with sdrplay rsp1 that it probably has to do with gr-osmosdr.<br />i have posted the issue on gqrx github <a class="external" href="https://github.com/gqrx-sdr/gqrx/issues/970">https://github.com/gqrx-sdr/gqrx/issues/970</a><br />and came in to the conclusion the it is probably on gr-osmosdr.</p>
<p>I use arch linux and the same problem consists for a year or more.<br />I am using gqrx v2.15.2-20-gdadc20b and gr-osmosdr 0.2.3-8.</p>
<p>In gqrx the input rate is only 0.2 MHz available in the 5, 6, 8 MHz, or whatever rate i choose.<br />It renders all the 8 MHz as an example but all of it is noise only for a 0.2 MHz hump in the middle.<br />Everything out of the hump is muted, you can only receive signal in the middle of the hump.</p>
<p>Every other software that i use through soapy has no problem but it is not through gr-osmosdr.</p> SIMtrace 2 - Bug #5423 (New): "trace" firmware continuous test setuphttps://osmocom.org/issues/54232022-01-27T12:24:54Zlaforge
<p>Similar to <code>cardem</code> in <a class="issue tracker-2 status-2 priority-2 priority-default" title="Feature: "cardem" continuous testing setup (In Progress)" href="https://osmocom.org/issues/5422">#5422</a>, we should also create a continuous test setup for passing SIM protocol tracing. The IUT is the simtrace2 firmware.</p>
<p>We can use diffeent modems / CCID readers accessing a SIM card via a SIMtrace2 device while tracing the communication.</p> OsmocomDECT - Bug #5396 (New): TcpDump/WireShark will not build with libpcap(dect) https://osmocom.org/issues/53962022-01-09T12:56:49Z
<p>Wireshark problem:</p>
<pre>
capture-pcap-util.c:274: error: static declaration of ‘pcap_datalink_name_to_val’ follows non-static declaration
/usr/local/include/pcap/pcap.h:380: note: previous declaration of ‘pcap_datalink_name_to_val’ was here
capture-pcap-util.c:289: error: static declaration of ‘pcap_datalink_val_to_name’ follows non-static declaration
/usr/local/include/pcap/pcap.h:381: note: previous declaration of ‘pcap_datalink_val_to_name’ was here
TcpDump? problem:
./../libpcap/libpcap.a(pcap.o): In function `pcap_datalink_name_to_val':
/root/libpcap/./pcap.c:855: multiple definition of `pcap_datalink_name_to_val'
dlnames.o:dlnames.c:(.text+0x90): first defined here
./../libpcap/libpcap.a(pcap.o): In function `pcap_datalink_val_to_name':
/root/libpcap/./pcap.c:868: multiple definition of `pcap_datalink_val_to_name'
dlnames.o:dlnames.c:(.text+0x0): first defined here
./../libpcap/libpcap.a(pcap.o): In function `pcap_datalink_val_to_description':
/root/libpcap/./pcap.c:880: multiple definition of `pcap_datalink_val_to_description'
dlnames.o:dlnames.c:(.text+0x40): first defined here
./../libpcap/libpcap.a(pcap.o): In function `pcap_list_datalinks':
/root/libpcap/./pcap.c:553: multiple definition of `pcap_list_datalinks'
datalinks.o:datalinks.c:(.text+0x0): first defined here
./../libpcap/libpcap.a(sf-pcap.o): In function `pcap_dump_ftell':
/root/libpcap/./sf-pcap.c:590: multiple definition of `pcap_dump_ftell'
pcap_dump_ftell.o:pcap_dump_ftell.c:(.text+0x0): first defined here
./../libpcap/libpcap.a(pcap-dect-linux.o): In function `dect_platform_finddevs':
/root/libpcap/./pcap-dect-linux.c:79: undefined reference to `nl_dect_cell_alloc_cache'
./../libpcap/libpcap.a(pcap-dect-linux.o): In function `add_cell_cb':
/root/libpcap/./pcap-dect-linux.c:52: undefined reference to `nl_dect_cell_get_name'
</pre> E1/T1 Hardware Interface (including icE1usb) - Bug #5382 (New): icE1usb: detect all-1 pattern an...https://osmocom.org/issues/53822022-01-02T12:17:29Zlaforge
<p>This applies to both DAHDI and e1d.</p> Osmocom Analog - Bug #5247 (New): AMPS Segmentation faulthttps://osmocom.org/issues/52472021-10-04T23:45:33Zfoxrf
<p>I have built osmocom analog as described in the documentation with the latest git release and amps seg faults as soon as it opens the SDR via soapySDR. <br />I do not have any logs or documents to show at this time as I am unable to obtain a core dump. I have tried this on both an x86 system and ARM (raspberry pi)</p>
<p>There were some build issues related to Devices.h in SoapySDR however I was able to resolve that by replacing the file with the most current version in their git repo.</p> OsmocomBB - Bug #5202 (New): [Assert failed rc >= 0 l1ctl.c:83] cell_log crashes (mostly) when mo...https://osmocom.org/issues/52022021-07-25T13:38:10Zantfarmer
<p>Upon execution of <strong>./cell_log -A 117 -i 127.0.0.1</strong>, the program crashes after a while with:</p>
<pre>
Assert failed rc >= 0 l1ctl.c:83
backtrace() returned 13 addresses
/usr/local/lib/libosmocore.so.17(osmo_generate_backtrace+0x18) [0x7f10d726684f]
/usr/local/lib/libosmocore.so.17(+0x24557) [0x7f10d7266557]
/usr/local/lib/libosmocore.so.17(osmo_panic+0xdc) [0x7f10d7266638]
./cell_log() [0x407f4a]
./cell_log() [0x40821d]
/usr/local/lib/libosmocore.so.17(osmo_wqueue_bfd_cb+0x3a) [0x7f10d7259e3d]
/usr/local/lib/libosmocore.so.17(+0xf2c4) [0x7f10d72512c4]
/usr/local/lib/libosmocore.so.17(+0xf3ba) [0x7f10d72513ba]
/usr/local/lib/libosmocore.so.17(osmo_select_main+0x15) [0x7f10d72513d8]
./cell_log() [0x402f2c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f10d66db840]
./cell_log() [0x4030b9]
Aborted
</pre>
<p>Line 83 in l1ctl.c:</p>
<pre><code class="c syntaxhl"><span class="cm">/* if FN is negative, we were called for something that's not CCCH! */</span>
<span class="n">OSMO_ASSERT</span><span class="p">(</span><span class="n">rc</span> <span class="o">>=</span> <span class="mi">0</span><span class="p">);</span>
</code></pre>
<p>The problem exists mostly when specifying an ARFCN manually, although i have seen the same type of crash even when no ARFCN is specified and an active scan is in place, but it is a very rare occasion and takes much more time to occur.</p>
<p>I have tried with different cells of different network carriers, so this is very unlikely to be a network issue.</p>
<p>Using the latest revision to date of master branch.</p> OsmoBTS - Bug #4985 (New): AMR RTP CMR of downlink frames not used to influence CMChttps://osmocom.org/issues/49852021-01-28T13:35:16Zlaforge
<p>Every AMR RTP frame the BTS receives in downlink contains a CMR (codec mode request) field, indicating what kind of codec mode the remote peer wishes to receive.</p>
<p>As per 3GPP TS 45.009 Section 3.1.2, we should use this CMR field, compare it with the CMC the local rate adaptation would normally choose and then forward the <em>lower</em> of both as actual CMC to the MS.</p> osmo-clock-gen - Bug #4814 (New): alignment of DC barrel with face platehttps://osmocom.org/issues/48142020-10-16T17:30:40Zlaforge
<p>Check if <a class="issue tracker-2 status-1 priority-1 priority-lowest" title="Feature: alignment of DC barrel with face plate (New)" href="https://osmocom.org/issues/4809">#4809</a> also applies here.</p> SDR (Software Defined Radio) - Bug #4653 (New): cannot import name 'fosphor'https://osmocom.org/issues/46532020-07-05T14:34:54Zsystemd
<p>I am using Linux Mint 19.3 with a NVIDIA Corporation GM107GL [Quadro K620] (rev a2), runnin GNU Radio 3.8.</p>
<p>I followed the instructions on the installation page (<a class="external" href="https://osmocom.org/projects/sdr/wiki/fosphor">https://osmocom.org/projects/sdr/wiki/fosphor</a>) but I receive an error when I try to use fosphor. The error says "from gnuradio import fosphor<br />ImportError: cannot import name 'fosphor'"</p>
<p>my installation went as</p>
<p>First installed GLFW3 and it did install great.</p>
<p>then, sudo apt-get install nvidia-opencl-dev opencl-headers and sudo apt-get install nvidia-modprobe</p>
<p>Afterwards, gr-fosphor which too installed correctly.</p>
<p>Would someone be nice enough to advice what solutions I may try?</p> OsmoBTS - Bug #4579 (New): add IPv6 supporthttps://osmocom.org/issues/45792020-06-03T16:59:04Zlynxis
<p>Add support to use OsmoBTS in a IPv6 environment. All connections has to support IPv6.<br />GB IPv6 and PCU related changes are in a seperate ticket.</p>
<a name="OML-content"></a>
<h2 >OML content<a href="#OML-content" class="wiki-anchor">¶</a></h2>
<ul>
<li>rx_oml_ipa_rsl_connect()
<ul>
<li>NM_ATT_IPACC_DST_IP contains IPv4-only address by BSC</li>
</ul></li>
</ul>
<a name="RSL-content"></a>
<h2 >RSL content<a href="#RSL-content" class="wiki-anchor">¶</a></h2>
<ul>
<li>rsl_tx_ipac_XXcx_ack()
<ul>
<li>assumes RSL_IE_IPAC_REMOTE_IP is IPv4-only address by BSC</li>
<li>uses osmo_rtp_get_bound_ip_port() -> migrate to osmo_rtp_get_bound_addr()</li>
</ul></li>
</ul>
<ul>
<li>tx_ipac_XXcx_nack() + rsl_tx_ipac_XXcx_ack()
<ul>
<li>uses RSL_IE_IPAC_REMOTE_IP / RSL_IE_IPAC_LOCAL_IP and assumes content is v4-only</li>
</ul></li>
</ul>
<a name="TTCN3-tests-for-IPv6-have-to-be-created-for-all-parts-messages-IEs"></a>
<h2 >TTCN3 tests for IPv6 have to be created for all parts / messages / IEs<a href="#TTCN3-tests-for-IPv6-have-to-be-created-for-all-parts-messages-IEs" class="wiki-anchor">¶</a></h2>
<ul>
<li>write tests with dual stack and connect to a single stack BSC.</li>
<li>write tests for a only IPv6 setup.</li>
</ul> OsmoMGW - Bug #4447 (New): DSCP value should be a 6 bit fieldhttps://osmocom.org/issues/44472020-03-09T09:11:24Zosmith
<p>TOS was 8bits, but only the upper 6 bits became DSCP. The VTY command for DSCP in OsmoMGW accepts an 8 bit value. We are setting the setsockopt for TOS with that value without bit-shifting.</p>
<p>This came up while writing a <a href="https://gerrit.osmocom.org/c/osmo-bts/+/17401" class="external">similar patch</a> for setting DSCP for OsmoBTS.</p>
<p>Should we</p>
<p>a) shift it two bits up and adjust the command syntax (and config template) to restrict to 0..63 (backwards incompatible)</p>
<p>or</p>
<p>b) change the description of the VTY command, so it is obvious that we are actually setting the TOS? (probably confusing)</p>
<p>CC: <a class="user active" href="https://osmocom.org/users/7">laforge</a></p> libosmocore - Bug #4265 (New): --enable-embedded doesn't work as expectedhttps://osmocom.org/issues/42652019-11-12T11:18:36Zlaforge
<p>--enable-embedded is supposed to automatically set flags like --disable-libsctp. In theory that<br /> is implemented, but in practise it doesn't work, as the actual <strong>check</strong> is still performed, even if later down the configure[.ac] script we set ENABLE_LIBSCTP to "false". So we perform the check (and abort in case it isn't present), but later would discard the result.</p>
<p>Re-ordering the blocks in configure.ac to first have the embedded handling doesn't help. I guess we would need to take the "$embedded" variable into account somehow in each of the enable/disable clauses?</p>
<p>Unless somebody knows a quick fix, it's not worth spending time on right now, but just for the record...</p> osmo-fl2k - Bug #4174 (New): After the latest commits, the fl2k tools do not exit on first SIGINThttps://osmocom.org/issues/41742019-08-25T16:57:13Zparkerlreed
<p>It hangs after the first and then exits on the second.</p>
<pre><code>
[parker@stealth ~]$ fl2k_test -s 157e6
Allocating 6 zero-copy buffers
libusb: error [op_dev_mem_alloc] alloc dev mem failed errno 12
Failed to allocate zero-copy buffer for transfer 4
Falling back to buffers in userspace
Requested sample rate 157000000 not possible, using 157142851.000000, error is 142851.000000
Reporting PPM error measurement every 10 seconds...
Press ^C after a few minutes.
real sample rate: 157153750 current PPM: 69 cumulative PPM: 69
real sample rate: 157153688 current PPM: 69 cumulative PPM: 69
real sample rate: 157153733 current PPM: 69 cumulative PPM: 69
real sample rate: 157151996 current PPM: 58 cumulative PPM: 66
^CSignal caught, exiting!
User cancel, exiting...
^CSignal caught, exiting!
</code></pre> OsmoMGW - Bug #4153 (New): 3G voice broken with ALu 9361 femtohttps://osmocom.org/issues/41532019-08-15T15:04:11Zdev_zzo
<p>Hello,</p>
<p>I am trying to create a setup with various Osmocom components to get the Alcatel-Lucent 9361 femtocells I have to function as a small 3G network. Currently, I am experiencing issues with 3G voice calls, quite similar to the ones described in <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: 3G voice broken, CS RAB Assignment is not working (Resolved)" href="https://osmocom.org/issues/3411">#3411</a> / <a class="issue tracker-2 status-3 priority-2 priority-default closed behind-schedule" title="Feature: remove nano3G IuUP "Initialization ACK" hack when IuUP proxy is in place (Resolved)" href="https://osmocom.org/issues/2459">#2459</a> / <a class="issue tracker-2 status-3 priority-2 priority-default closed behind-schedule" title="Feature: Implement way how to handle IuUP on RTP endpoints (Resolved)" href="https://osmocom.org/issues/1937">#1937</a>: the voice call is dropped.</p>
<p>I have traced the issue to the following code: <a class="external" href="https://github.com/osmocom/osmo-mgw/blob/9aaaab6b3b5a541a6c17077f5f1f8bc00ba77152/src/libosmo-mgcp/mgcp_network.c#L873">https://github.com/osmocom/osmo-mgw/blob/9aaaab6b3b5a541a6c17077f5f1f8bc00ba77152/src/libosmo-mgcp/mgcp_network.c#L873</a></p>
<p>The femtocell rejects the IuUP message due to a CRC mismatch and indeed, when the bytes are patched, the header CRC is not updated and therefore cannot match.</p> gr-osmosdr - Bug #4098 (New): [BladeRF micro] Arguments set in osmocom Sink and Source are not pa...https://osmocom.org/issues/40982019-07-11T14:04:23Zlukeekul
<p>For Gnuradio, Device Arguments that are set in osmocom Sink or Source are not executed. As far as I understand the code, these arguments are ignored in sink_impl.cc and source_impl.cc.<br />A patch, the only addresses the bladeRF micro, can be found here:<br /><a class="external" href="https://github.com/Lukeekul/gr-osmosdr/commit/20d1a3618b9e81975d55b05e6f98d969db755aaf">https://github.com/Lukeekul/gr-osmosdr/commit/20d1a3618b9e81975d55b05e6f98d969db755aaf</a><br />Regards,<br />lukeekul</p> OsmoBSC - Bug #3737 (New): abort because unused lchan has non-null conn pointer, after AMR config...https://osmocom.org/issues/37372018-12-18T02:23:42Zneelsnhofmeyr@sysmocom.de
<p>I was just establishing a call and osmo-bsc crashes on me. Log follows.</p> OsmoMSC - Bug #2698 (New): Add more tests to jenkins job testing osmo-msc against NG40testerhttps://osmocom.org/issues/26982017-12-01T12:36:00Zpespin
<p>So far, in sysmocom's jenkins instance job (ng40-test-core-network), we only run 1 test which checks that LU works for 300 MS connecting to osmo-msc.</p>
<p>We need to find a list of screnarios we want to test and implement them using NG40.</p> OsmoBTS - Bug #2675 (New): /usr/bin/lc15bts-mgr can't find GPS 3D fix to for calibrationhttps://osmocom.org/issues/26752017-11-22T16:42:02Zrshack
<p>Hi,</p>
<p>We have a Litecell 1.5 unit. It is updated to the latest packages on the nightly build and configured to an osmo-bsc set up on an another machine.</p>
<p>On mobile phones, the network does not show the short or long name set, instead it shows just numbers "09070" and calls can not be made.</p>
<p>This has happened to us before when there was problem with the clock calibration on the BTS.</p>
<p>A GPS device is attached to the BTS, and when running cgps, there is a 3D Fix and a correct GPS location coordinates show up.</p>
<p>The lc15 bts should be able to calibrate automatically using the lc15bts-mgr package, however, it seems like it is failing to do so.</p>
<p>When we tried stopping the lc15bts-mgr service and start it manually to log the output by running:</p>
<pre>
/usr/bin/lc15bts-mgr -s -c /etc/osmocom/lc15bts-mgr.cfg
</pre>
<p>We notice the following errors:</p>
<pre>
Failed to open /mnt/storage/var/run/lc15bts-mgr/volt-supply-max due to 'No such file or directory' error
<0000> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_misc.c:315 Total hours of Operation: 393
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:271 Going to calibrate the system.
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:121 Last GPS 3D fix can not read (-2). Last GPS 3D fix sets to zero
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:126 GPS has no fix
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002e,m:0x000000000000007f
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002f,m:0x000000000000007f
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:271 Going to calibrate the system.
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:121 Last GPS 3D fix can not read (-2). Last GPS 3D fix sets to zero
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:126 GPS has no fix
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002f,m:0x000000000000007f
</pre>
<p>It seems the lc15bts_mgr service can not read the values from the GPS device for some reason, can someone please advise what might be causing this issue?</p>
<p>Best Regards,<br />Rayan</p> OsmoGSMTester - Bug #2615 (New): Add API to check GPS lock in BTShttps://osmocom.org/issues/26152017-11-03T17:00:23Zpespin
<p>We should make sure that all BTS are always correctly calibrated.</p>
<p>For sysmocell5000, ssh+ccli can be used:</p>
<p>Ensure GPS_AUTO_SET_DATE_TIME_ENABLE is enabled<br /><pre>
> mib.get GPS_AUTO_SET_DATE_TIME_ENABLE
OK
GPS_AUTO_SET_DATE_TIME_ENABLE 1 (0x1
</pre></p>
<p>Other interesting commands to check for fix:<br /><pre>
> gps.get-location
OK
lat=0, long=0, alt=0m, age=4294967295s
> gps.get-time
OK
time=023016.33, date=1970-01-11, unixtime=873016, age=4294967295s
</pre></p>
<p>For OCTPHY it's even part of the DSP API.</p>
<p>For b-200, there no way to check afaik.</p>
<p>For sysmobts: gps related:"gpsmon", "gpsdate", "gpsctl", "cgps /dev/ttyS2" <br />To calibrate use sysmobts-calib -m calibrate with any available source (gps or other networks).</p> OsmoBTS - Bug #1744 (New): 1-way voice between sysmobts and nanobts if DTX is enabledhttps://osmocom.org/issues/17442016-06-03T16:23:39Zmsuraev
<p>Not sure if it's osmobts or openbsc to blame but in following setup there's 1-way audio:</p>
<p>ms1 <-> sysmobts <-> openbsc <-> nanobts <-> ms2</p>
<p>The audio ms2 -> ms1 can be heard (if -P option is used for openbsc than some stattering in voice is audible, not sure if it's a separate issue) but the audio ms1 -> ms2 is nonexistent. In some test 1-2 words could be heard before audio is gone. Switching phones change nothing.</p>
<p>OpenBSC is configured for full-rate channels with AMR codec in the attached .pcap although the same effect could be observed with other codecs too.</p> OsmoPCU - Bug #1624 (New): add CRBB support to write_packet_ack_nack_desc_egprshttps://osmocom.org/issues/16242016-02-25T17:23:58Zmsuraev
<p>According to TS 44.060 §12.3.1 EGPRS Ack/Nack Description can use compressed block bitmaps.<br />At the moment there is todo code plug which forces use of URBB makes coverity unhappy (CID 1351734).<br />Note: this would require extending osmo_t4_encode() into proper encoder with backtracking instead of current "best guess" approach.</p> Mobile (in)Security - Bug #1480 (New): A5/3 is not deployed in GSM networkshttps://osmocom.org/issues/14802016-02-19T22:51:58Zlaforge
<p>The 3GPP has specified the Kasumi-derived A5/3 cipher for use in GSM networks. This would significantly increase the confidentiality and security of the GSM network, since it avoids the known-weak and known-broken A5/1 cipher. The passive A5/1 key-cracking attacks would no longer work.</p>
<p>In order to use A5/3, both the MS and the BTS will have to implement the A5/3 cipher, and the BSC will have to configure the BTSs to actually use it.</p>
<p>Many modern phones (whether 3G or not) support A5/3 operation on GSM and indicate this capability in their CLASSMARK.</p>
<p>However, none of the networks we have seen are using A5/3 on GSM.</p>
<p>Thus, the operators and/or equipment manufacturers are actively preventing a higher level of security and confidentiality.</p> OsmocomBB - Bug #1462 (New): ../../src/utils.c:182:7: error: only weak aliases are supported in t...https://osmocom.org/issues/14622016-02-19T22:48:42Z
<p>Build fails on OSX Lion</p>
<p>bash-3.2# make<br />mkdir shared/libosmocore/build-target<br />cd shared/libosmocore/build-target && ../configure \<br /> --host=arm-elf --enable-embedded --disable-shared \<br /> --disable-tests ac_cv_header_sys_select_h=no \<br /> --disable-tests ac_cv_header_sys_socket_h=no \<br /> CFLAGS="-Os <del>ffunction-sections -I/Users/blombo/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" <br />configure: WARNING: if you wanted to set the --build type, don't use --host.<br /> If a cross compiler is detected then cross compile mode will be used<br />checking for a BSD-compatible install... /usr/bin/install -c<br />checking whether build environment is sane... yes<br />checking for arm-elf-strip... arm-elf-strip<br />checking for a thread-safe mkdir -p... ../install-sh -c -d<br />checking for gawk... no<br />checking for mawk... no<br />checking for nawk... no<br />checking for awk... awk<br />checking whether make sets $(MAKE)... yes<br />checking whether make sets $(MAKE)... (cached) yes<br />checking for arm-elf-gcc... arm-elf-gcc<br />checking whether the C compiler works... yes<br />checking for C compiler default output file name... a.out<br />checking for suffix of executables... <br />checking whether we are cross compiling... yes<br />checking for suffix of object files... o<br />checking whether we are using the GNU C compiler... yes<br />checking whether arm-elf-gcc accepts -g... yes<br />checking for arm-elf-gcc option to accept ISO C89... none needed<br />checking for style of include used by make... GNU<br />checking dependency style of arm-elf-gcc... gcc3<br />checking build system type... x86_64-apple-darwin11.2.0<br />checking host system type... arm-unknown-elf<br />checking how to print strings... printf<br />checking for a sed that does not truncate output... /usr/bin/sed<br />checking for grep that handles long lines and -e... /usr/bin/grep<br />checking for egrep... /usr/bin/grep -E<br />checking for fgrep... /usr/bin/grep -F<br />checking for ld used by arm-elf-gcc... /Volumes/Speicher/opt/local/arm-elf/bin/ld<br />checking if the linker (/Volumes/Speicher/opt/local/arm-elf/bin/ld) is GNU ld... yes<br />checking for BSD</del> or MS-compatible name lister (nm)... /opt/local/bin//arm-elf-nm <del>B<br />checking the name lister (/opt/local/bin//arm-elf-nm -B) interface... BSD nm<br />checking whether ln -s works... yes<br />checking the maximum length of command line arguments... 196608<br />checking whether the shell understands some XSI constructs... yes<br />checking whether the shell understands "+="... yes<br />checking how to convert x86_64-apple-darwin11.2.0 file names to arm-unknown-elf format... func_convert_file_noop<br />checking how to convert x86_64-apple-darwin11.2.0 file names to toolchain format... func_convert_file_noop<br />checking for /Volumes/Speicher/opt/local/arm-elf/bin/ld option to reload object files... -r<br />checking for arm-elf-objdump... arm-elf-objdump<br />checking how to recognize dependent libraries... unknown<br />checking for arm-elf-dlltool... no<br />checking for dlltool... no<br />checking how to associate runtime and link libraries... printf <span>s\n<br />checking for arm-elf-ar... arm-elf-ar<br />checking for archiver <code>FILE support... </code><br />checking for arm-elf-strip... (cached) arm-elf-strip<br />checking for arm-elf-ranlib... arm-elf-ranlib<br />checking command to parse /opt/local/bin//arm-elf-nm -B output from arm-elf-gcc object... ok<br />checking for sysroot... no<br />checking for arm-elf-mt... no<br />checking for mt... no<br />checking if : is a manifest tool... no<br />checking how to run the C preprocessor... arm-elf-gcc -E<br />checking for ANSI C header files... yes<br />checking for sys/types.h... yes<br />checking for sys/stat.h... yes<br />checking for stdlib.h... yes<br />checking for string.h... yes<br />checking for memory.h... yes<br />checking for strings.h... yes<br />checking for inttypes.h... yes<br />checking for stdint.h... yes<br />checking for unistd.h... yes<br />checking for dlfcn.h... no<br />checking for objdir... .libs<br />checking if arm-elf-gcc supports -fno-rtti -fno-exceptions... no<br />checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC<br />checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes<br />checking if arm-elf-gcc static flag -static works... yes<br />checking if arm-elf-gcc supports -c -o file.o... yes<br />checking if arm-elf-gcc supports -c -o file.o... (cached) yes<br />checking whether the arm-elf-gcc linker (/Volumes/Speicher/opt/local/arm-elf/bin/ld) supports shared libraries... yes<br />checking dynamic linker characteristics... no<br />checking how to hardcode library paths into programs... immediate<br />checking whether stripping libraries is possible... yes<br />checking if libtool supports shared libraries... no<br />checking whether to build shared libraries... no<br />checking whether to build static libraries... yes<br />checking for ANSI C header files... (cached) yes<br />checking execinfo.h usability... no<br />checking execinfo.h presence... no<br />checking for execinfo.h... no<br />checking for sys/select.h... (cached) no<br />checking for sys/socket.h... (cached) no<br />checking syslog.h usability... no<br />checking syslog.h presence... no<br />checking for syslog.h... no<br />checking ctype.h usability... yes<br />checking ctype.h presence... yes<br />checking for ctype.h... yes<br />checking for size_t... yes<br />checking for working alloca.h... yes<br />checking for alloca... yes<br />checking for library containing dlopen... no<br />checking for doxygen... false<br />checking if arm-elf-gcc supports -fvisibility=hidden... yes<br />configure: creating ./config.status<br />config.status: creating libosmocore.pc<br />config.status: creating libosmocodec.pc<br />config.status: creating libosmovty.pc<br />config.status: creating libosmogsm.pc<br />config.status: creating include/osmocom/Makefile<br />config.status: creating include/osmocom/vty/Makefile<br />config.status: creating include/osmocom/codec/Makefile<br />config.status: creating include/osmocom/crypt/Makefile<br />config.status: creating include/osmocom/gsm/Makefile<br />config.status: creating include/osmocom/gsm/protocol/Makefile<br />config.status: creating include/osmocom/core/Makefile<br />config.status: creating include/Makefile<br />config.status: creating src/Makefile<br />config.status: creating src/vty/Makefile<br />config.status: creating src/codec/Makefile<br />config.status: creating src/gsm/Makefile<br />config.status: creating tests/Makefile<br />config.status: creating tests/timer/Makefile<br />config.status: creating tests/sms/Makefile<br />config.status: creating tests/msgfile/Makefile<br />config.status: creating tests/ussd/Makefile<br />config.status: creating tests/smscb/Makefile<br />config.status: creating tests/bits/Makefile<br />config.status: creating utils/Makefile<br />config.status: creating Doxyfile.core<br />config.status: creating Doxyfile.gsm<br />config.status: creating Doxyfile.vty<br />config.status: creating Doxyfile.codec<br />config.status: creating Makefile<br />config.status: creating config.h<br />config.status: executing depfiles commands<br />config.status: executing libtool commands<br />cd shared/libosmocore/build-target &x%x</span> make<br />make all-recursive<br />Making all in include<br />Making all in osmocom<br />Making all in codec<br />maker5: Nothing to be done for @all'.<br />Making all in crypt<br />maker5: Nothing to be done for @all'.<br />Making all in gsm<br />Making all in protocol<br />maker6: Nothing to be done for @all'.<br />maker6: Nothing to be done for @all-am'.<br />Making all in core<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc8gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc16gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc32gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc64gen.h<br />maker5: Nothing to be done for @all-am'.<br />maker4: Nothing to be done for @all-am'.<br />Making all in src<br />Making all in .<br /> CC timer.lo<br /> CC select.lo<br /> CC signal.lo<br /> CC msgb.lo<br /> CC bits.lo<br /> CC bitvec.lo<br /> CC statistics.lo<br />../../src/statistics.c: In function 'osmo_counter_get_by_name':<br />../../src/statistics.c:72:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]<br /> CC write_queue.lo<br /> CC utils.lo<br />../../src/utils.c: In function 'get_value_string':<br />../../src/utils.c:33:2: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' [-Wformat]<br />../../src/utils.c: In function 'get_string_value':<br />../../src/utils.c:49:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration]<br /> CC socket.lo<br /> CC logging.lo<br />../../src/logging.c: In function 'log_parse_category_mask':<br />../../src/logging.c:168:2: warning: implicit declaration of function 'strdup' [-Wimplicit-function-declaration]<br />../../src/logging.c:168:15: warning: incompatible implicit declaration of built-in function 'strdup' [enabled by default]<br />../../src/logging.c:175:2: warning: implicit declaration of function 'strtok' [-Wimplicit-function-declaration]<br />../../src/logging.c:175:17: warning: assignment makes pointer from integer without a cast [enabled by default]<br />../../src/logging.c:178:4: warning: implicit declaration of function 'strstr' [-Wimplicit-function-declaration]<br />../../src/logging.c:178:18: warning: incompatible implicit declaration of built-in function 'strstr' [enabled by default]<br />../../src/logging.c:203:27: warning: assignment makes pointer from integer without a cast [enabled by default]<br />../../src/logging.c: In function '_file_output':<br />../../src/logging.c:433:2: warning: implicit declaration of function 'fprintf' [-Wimplicit-function-declaration]<br />../../src/logging.c:433:2: warning: incompatible implicit declaration of built-in function 'fprintf' [enabled by default]<br />../../src/logging.c:434:2: warning: implicit declaration of function 'fflush' [-Wimplicit-function-declaration]<br />../../src/logging.c: In function 'log_target_create_file':<br />../../src/logging.c:506:2: warning: implicit declaration of function 'fopen' [-Wimplicit-function-declaration]<br />../../src/logging.c:506:23: warning: assignment makes pointer from integer without a cast [enabled by default]<br />../../src/logging.c: In function 'log_target_find':<br />../../src/logging.c:530:4: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]<br />../../src/logging.c: In function 'log_target_destroy':<br />../../src/logging.c:552:4: warning: implicit declaration of function 'fclose' [-Wimplicit-function-declaration]<br />../../src/logging.c: In function 'log_target_file_reopen':<br />../../src/logging.c:565:23: warning: assignment makes pointer from integer without a cast [enabled by default]<br /> CC logging_syslog.lo<br /> CC rate_ctr.lo<br />../../src/rate_ctr.c: In function 'rate_ctr_get_group_by_name_idx':<br />../../src/rate_ctr.c:153:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]<br /> CC gsmtap_util.lo<br /> CC crc16.lo<br /> CC panic.lo<br /> CC backtrace.lo<br /> CC conv.lo<br /> CC application.lo<br /> CC rbtree.lo<br /> SED ../../src/crcXXgen.c.tpl -> crc8gen.c<br /> CC crc8gen.lo<br /> SED ../../src/crcXXgen.c.tpl -> crc16gen.c<br /> CC crc16gen.lo<br /> SED ../../src/crcXXgen.c.tpl -> crc32gen.c<br /> CC crc32gen.lo<br /> SED ../../src/crcXXgen.c.tpl -> crc64gen.c<br /> CC crc64gen.lo<br /> CCLD libosmocore.la<br />Making all in vty<br />maker4: Nothing to be done for @all'.<br />Making all in codec<br /> CC gsm610.lo<br /> CC gsm620.lo<br /> CC gsm660.lo<br /> CC gsm690.lo<br /> CCLD libosmocodec.la<br />Making all in gsm<br /> CC a5.lo<br /> CC rxlev_stat.lo<br /> CC tlv_parser.lo<br /> CC comp128.lo<br /> CC gsm_utils.lo<br />../../../src/gsm/gsm_utils.c: In function 'gsm_7bit_encode':<br />../../../src/gsm/gsm_utils.c:253:13: warning: variable 'z' set but not used [-Wunused-but-set-variable]<br /> CC rsl.lo<br /> CC gsm48.lo<br />../../../src/gsm/gsm48.c: In function 'gsm48_mi_to_string':<br />../../../src/gsm/gsm48.c:348:4: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' [-Wformat]<br /> CC gsm48_ie.lo<br /> CC gsm0808.lo<br /> CC sysinfo.lo<br /> CC gprs_cipher_core.lo<br /> CC gsm0480.lo<br />../../../src/gsm/gsm0480.c: In function 'parse_process_uss_req':<br />../../../src/gsm/gsm0480.c:405:7: warning: pointer targets in passing argument 1 of 'gsm_7bit_decode' differ in signedness [-Wpointer-sign]<br />../../../include/osmocom/gsm/gsm_utils.h:59:5: note: expected 'char <strong>' but argument is of type 'uint8_t *'<br /> CC abis_nm.lo<br /> CC gsm0502.lo<br /> CC gsm0411_utils.lo<br /> CC gsm0411_smc.lo<br /> CC gsm0411_smr.lo<br /> CC lapd_core.lo<br />../../../src/gsm/lapd_core.c: In function 'lapd_acknowledge':<br />../../../src/gsm/lapd_core.c:710:38: warning: variable 't200_start' set but not used [-Wunused-but-set-variable]<br />../../../src/gsm/lapd_core.c: In function 'lapd_rx_u':<br />../../../src/gsm/lapd_core.c:835:5: warning: implicit declaration of function 'memcmp' [-Wimplicit-function-declaration]<br /> CC lapdm.lo<br /> CCLD libosmogsm.la<br />Making all in tests<br />maker4: Nothing to be done for @all-am'.<br />Making all in utils<br />maker3: Nothing to be done for @all'.<br />maker3: Nothing to be done for @all-am'.<br />mkdir shared/libosmocore/build-host<br />cd shared/libosmocore/build-host && ../configure <br />checking for a BSD-compatible install... /usr/bin/install -c<br />checking whether build environment is sane... yes<br />checking for a thread-safe mkdir -p... ../install-sh -c -d<br />checking for gawk... no<br />checking for mawk... no<br />checking for nawk... no<br />checking for awk... awk<br />checking whether make sets $(MAKE)... yes<br />checking whether make sets $(MAKE)... (cached) yes<br />checking for gcc... gcc<br />checking whether the C compiler works... yes<br />checking for C compiler default output file name... a.out<br />checking for suffix of executables... <br />checking whether we are cross compiling... no<br />checking for suffix of object files... o<br />checking whether we are using the GNU C compiler... yes<br />checking whether gcc accepts -g... yes<br />checking for gcc option to accept ISO C89... none needed<br />checking for style of include used by make... GNU<br />checking dependency style of gcc... gcc3<br />checking build system type... x86_64-apple-darwin11.2.0<br />checking host system type... x86_64-apple-darwin11.2.0<br />checking how to print strings... printf<br />checking for a sed that does not truncate output... /usr/bin/sed<br />checking for grep that handles long lines and -e... /usr/bin/grep<br />checking for egrep... /usr/bin/grep -E<br />checking for fgrep... /usr/bin/grep -F<br />checking for ld used by gcc... /usr/bin/ld<br />checking if the linker (/usr/bin/ld) is GNU ld... no<br />checking for BSD</del> or MS-compatible name lister (nm)... /usr/bin/nm<br />checking the name lister (/usr/bin/nm) interface... BSD nm<br />checking whether ln -s works... yes<br />checking the maximum length of command line arguments... 196608<br />checking whether the shell understands some XSI constructs... yes<br />checking whether the shell understands "+="... yes<br />checking how to convert x86_64-apple-darwin11.2.0 file names to x86_64-apple-darwin11.2.0 format... func_convert_file_noop<br />checking how to convert x86_64-apple-darwin11.2.0 file names to toolchain format... func_convert_file_noop<br />checking for /usr/bin/ld option to reload object files... -r<br />checking for objdump... no<br />checking how to recognize dependent libraries... pass_all<br />checking for dlltool... no<br />checking how to associate runtime and link libraries... printf <span>s\n<br />checking for ar... ar<br />checking for archiver @FILE support... no<br />checking for strip... strip<br />checking for ranlib... ranlib<br />checking command to parse /usr/bin/nm output from gcc object... ok<br />checking for sysroot... no<br />checking for mt... no<br />checking if : is a manifest tool... no<br />checking for dsymutil... dsymutil<br />checking for nmedit... nmedit<br />checking for lipo... lipo<br />checking for otool... otool<br />checking for otool64... no<br />checking for -single_module linker flag... yes<br />checking for -exported_symbols_list linker flag... yes<br />checking for -force_load linker flag... yes<br />checking how to run the C preprocessor... gcc -E<br />checking for ANSI C header files... yes<br />checking for sys/types.h... yes<br />checking for sys/stat.h... yes<br />checking for stdlib.h... yes<br />checking for string.h... yes<br />checking for memory.h... yes<br />checking for strings.h... yes<br />checking for inttypes.h... yes<br />checking for stdint.h... yes<br />checking for unistd.h... yes<br />checking for dlfcn.h... yes<br />checking for objdir... .libs<br />checking if gcc supports -fno-rtti -fno-exceptions... no<br />checking for gcc option to produce PIC... -fno-common -DPIC<br />checking if gcc PIC flag -fno-common -DPIC works... yes<br />checking if gcc static flag -static works... no<br />checking if gcc supports -c -o file.o... yes<br />checking if gcc supports -c -o file.o... (cached) yes<br />checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes<br />checking dynamic linker characteristics... darwin11.2.0 dyld<br />checking how to hardcode library paths into programs... immediate<br />checking whether stripping libraries is possible... yes<br />checking if libtool supports shared libraries... yes<br />checking whether to build shared libraries... yes<br />checking whether to build static libraries... yes<br />checking for ANSI C header files... (cached) yes<br />checking execinfo.h usability... yes<br />checking execinfo.h presence... yes<br />checking for execinfo.h... yes<br />checking sys/select.h usability... yes<br />checking sys/select.h presence... yes<br />checking for sys/select.h... yes<br />checking sys/socket.h usability... yes<br />checking sys/socket.h presence... yes<br />checking for sys/socket.h... yes<br />checking syslog.h usability... yes<br />checking syslog.h presence... yes<br />checking for syslog.h... yes<br />checking ctype.h usability... yes<br />checking ctype.h presence... yes<br />checking for ctype.h... yes<br />checking for size_t... yes<br />checking for working alloca.h... yes<br />checking for alloca... yes<br />checking for library containing dlopen... none required<br />checking for doxygen... false<br />checking if gcc supports -fvisibility=hidden... yes<br />configure: creating ./config.status<br />config.status: creating libosmocore.pc<br />config.status: creating libosmocodec.pc<br />config.status: creating libosmovty.pc<br />config.status: creating libosmogsm.pc<br />config.status: creating include/osmocom/Makefile<br />config.status: creating include/osmocom/vty/Makefile<br />config.status: creating include/osmocom/codec/Makefile<br />config.status: creating include/osmocom/crypt/Makefile<br />config.status: creating include/osmocom/gsm/Makefile<br />config.status: creating include/osmocom/gsm/protocol/Makefile<br />config.status: creating include/osmocom/core/Makefile<br />config.status: creating include/Makefile<br />config.status: creating src/Makefile<br />config.status: creating src/vty/Makefile<br />config.status: creating src/codec/Makefile<br />config.status: creating src/gsm/Makefile<br />config.status: creating tests/Makefile<br />config.status: creating tests/timer/Makefile<br />config.status: creating tests/sms/Makefile<br />config.status: creating tests/msgfile/Makefile<br />config.status: creating tests/ussd/Makefile<br />config.status: creating tests/smscb/Makefile<br />config.status: creating tests/bits/Makefile<br />config.status: creating utils/Makefile<br />config.status: creating Doxyfile.core<br />config.status: creating Doxyfile.gsm<br />config.status: creating Doxyfile.vty<br />config.status: creating Doxyfile.codec<br />config.status: creating Makefile<br />config.status: creating config.h<br />config.status: executing depfiles commands<br />config.status: executing libtool commands<br />cd shared/libosmocore/build-host &x%x</span> make<br />make all-recursive<br />Making all in include<br />Making all in osmocom<br />Making all in vty<br />maker5: Nothing to be done for @all'.<br />Making all in codec<br />maker5: Nothing to be done for @all'.<br />Making all in crypt<br />maker5: Nothing to be done for @all'.<br />Making all in gsm<br />Making all in protocol<br />maker6: Nothing to be done for @all'.<br />maker6: Nothing to be done for @all-am'.<br />Making all in core<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc8gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc16gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc32gen.h<br /> SED ../../../../include/osmocom/core/crcXXgen.h.tpl -> crc64gen.h<br />maker5: Nothing to be done for @all-am'.<br />maker4: Nothing to be done for @all-am'.<br />Making all in src<br />Making all in .<br /> CC timer.lo<br /> CC select.lo<br /> CC signal.lo<br /> CC msgb.lo<br /> CC bits.lo<br /> CC bitvec.lo<br /> CC statistics.lo<br /> CC write_queue.lo<br /> CC utils.lo<br />../../src/utils.c:182:7: error: only weak aliases are supported in this configuration<br />maker4: <b></strong> [utils.lo] Error 1<br />maker3: <strong></b> [all-recursive] Error 1<br />maker2: <b></strong> [all-recursive] Error 1<br />maker1: <strong></b> [all] Error 2<br />make: *</strong>* [shared/libosmocore/build-host/src/.libs/libosmocore.la] Error 2</p> OsmocomBB - Bug #1458 (New): AGC broken (strong cell cannot be syncedhttps://osmocom.org/issues/14582016-02-19T22:48:42Zlaforge
<p>There seems to be a problem when trying to sync to particularly strong cells, as we overload the input of the ADC.</p>
<p>As we're doing power measurements anyway, we need to use the received power level as input to the SCH and FCCH task and not start those with some default power level</p> OsmocomDECT - Bug #5388 (New): {MM-INFO-SUGGEST} message not sent with ext bit set to 0https://osmocom.org/issues/53882010-10-05T00:00:00Z
<p>GAP (ETSI EN 300 444) section 8.29 (Location update) requires two consecutive {MM-INFO-SUGGEST} messages to be sent, one with the ext bit set to one, one with the ext bit set to zero, presumably for compatibility with old equipment. libdect always sets the ext bit to one on the final octet.</p>