<div dir="ltr"><div><div>Hi all!<br><br></div>Moving all projects to a Redmine is a good way, I think.<br><br></div><div style="" id="gt-input-tool"><div id="itamenu"><span class=""></span></div></div><div id="gt-src-c" class=""><div id="gt-src-p"> </div> </div> <div id="gt-res-content" class=""><div dir="ltr" style="zoom:1"><span id="result_box" class="" lang="en"><span class="">In connection</span> <span class="">with the event I would like to offer my help with <br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">post-processing some old pages (</span></span><span id="result_box" class="" lang="en"><span class=""><span id="result_box" class="" lang="en"><span class=""><span id="result_box" class="" lang="en"><span class="">mostly</span><span class=""> OsmocomBB</span></span></span></span>) and with <br>improving the new wiki</span></span><span id="result_box" class="" lang="en"><span class=""> structure.</span></span><span id="result_box" class="" lang="en"><span class=""><br><br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">So, </span></span>m<span id="result_box" class="" lang="en"><span class="">y suggestions:</span></span><br><div style=""><span id="result_box" class="" lang="en"><span class="">- Create the main page that will describe all </span></span><span id="result_box" class="" lang="en"><span class="">all of the child</span> <span class="">projects</span><span class=""> <br></span></span></div><span id="result_box" class="" lang="en"><span class="">of Osmocom umbrella including recent news and plans.<br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">- Separate the libosmocore related pages from OsmocomBB <br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">into a new section named "Libraries", for example.<br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">- Separate both SIMTrace and softSIM into a new sections.<br><br></span></span></div><div style=""><span id="result_box" class="" lang="en"><span class="">It it would be nice to enable </span></span>Strict-Transport-Security to avoid <br></div><div style="">some traffic interception attempts. Also what about enabling <br></div><div style="">SPF and DKIM for mailing lists?<br></div></div><div><div><div><div class="gmail_extra"><br clear="all"><div><div><div>With best regards,<br></div><div>Vadim Yanitskiy.<br></div></div></div>
<br><div class="gmail_quote">2016-02-19 4:46 GMT+06:00 <span dir="ltr"><<a href="mailto:openbsc-request@lists.osmocom.org" target="_blank">openbsc-request@lists.osmocom.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send OpenBSC mailing list submissions to<br>
<a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.osmocom.org/mailman/listinfo/openbsc" rel="noreferrer" target="_blank">https://lists.osmocom.org/mailman/listinfo/openbsc</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openbsc-request@lists.osmocom.org" target="_blank">openbsc-request@lists.osmocom.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openbsc-owner@lists.osmocom.org" target="_blank">openbsc-owner@lists.osmocom.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenBSC digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: autoreconf v2.69 with subdir-objects: ./configure creates<br>
directory 'src/tests/\$(top_srcdir)' (Neels Hofmeyr)<br>
2. Re: hnb_cs_lu.msc (Neels Hofmeyr)<br>
3. Re: hnb_cs_lu.msc (Harald Welte)<br>
4. branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;<br>
merging to master (Neels Hofmeyr)<br>
5. Re: Moving from trac to a single redmine (Harald Welte)<br>
6. Re: Moving from trac to a single redmine (Holger Freyther)<br>
7. Re: branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;<br>
merging to master (Holger Freyther)<br>
8. sysmocom/iu: your commits from today (Neels Hofmeyr)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 17 Feb 2016 15:44:35 +0100<br>
From: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
To: Eric Blake <<a href="mailto:eblake@redhat.com" target="_blank">eblake@redhat.com</a>><br>
Cc: <a href="mailto:bug-autoconf@gnu.org" target="_blank">bug-autoconf@gnu.org</a>, <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: Re: autoreconf v2.69 with subdir-objects: ./configure creates<br>
directory 'src/tests/\$(top_srcdir)'<br>
Message-ID: <20160217144435.GD2106@dub6><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Eric,<br>
<br>
you've clarified just about all of my questions.<br>
Many thanks for your reply!<br>
<br>
~Neels<br>
<br>
> <a href="https://lists.gnu.org/archive/html/automake/2015-12/msg00001.html" rel="noreferrer" target="_blank">https://lists.gnu.org/archive/html/automake/2015-12/msg00001.html</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: Digital signature<br>
URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20160217/8d3fdbf8/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.osmocom.org/pipermail/openbsc/attachments/20160217/8d3fdbf8/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 17 Feb 2016 15:47:10 +0100<br>
From: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
To: Harald Welte <<a href="mailto:hwelte@sysmocom.de" target="_blank">hwelte@sysmocom.de</a>><br>
Cc: <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: Re: hnb_cs_lu.msc<br>
Message-ID: <20160217144710.GE2106@dub6><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Update: it seems that for IuPS/SGSN, a quite identical Identity Request<br>
message is indeed answered upon by the UE, so the reason why I'm not<br>
receiving one for IuCS/CSCN is unclear.<br>
<br>
~Neels<br>
<br>
On Wed, Feb 17, 2016 at 02:18:54PM +0100, Neels Hofmeyr wrote:<br>
> Hi Harald,<br>
><br>
> in osmo-iuh/doc/hnb_cs_lu.msc I find that after the location update<br>
> request from the UE, an identity request "should" follow from the CN.<br>
><br>
> Yesterday I made my first pcap using our hNodeB and that weighty black UE<br>
> we use for testing, and saw that the MSC indeed sends out an identity<br>
> request at that time [1], however, the UE simply never responds to it.<br>
><br>
> My question: is the hnb_cs_lu.msc declarative and definitely correct, or<br>
> could it be that in 3G, UEs in general expect authentication first, as<br>
> the "osmo-iuh/pcap/UPP RANAP.pcap" suggests (starting at packet #335).<br>
><br>
> Since my sources tell me (i.e. Daniel) that an identity request at that<br>
> time is indeed kinda special practise by openbsc to collect all IMEIs we<br>
> possibly can, I'm going for authentication first.<br>
><br>
> Just wanted to make sure you agree that the hnb_cs_lu.msc may be erratic<br>
> in that case. Thanks!<br>
><br>
> ~Neels<br>
><br>
> [1] near openbsc/src/libmsc/gsm_04_08.c:589 (thanks Daniel!)<br>
><br>
> --<br>
> - Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>> <a href="http://www.sysmocom.de/" rel="noreferrer" target="_blank">http://www.sysmocom.de/</a><br>
> =======================================================================<br>
> * sysmocom - systems for mobile communications GmbH<br>
> * Alt-Moabit 93<br>
> * 10559 Berlin, Germany<br>
> * Sitz / Registered office: Berlin, HRB 134158 B<br>
> * Gesch?ftsf?hrer / Managing Directors: Holger Freyther, Harald Welte<br>
<br>
<br>
<br>
--<br>
- Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>> <a href="http://www.sysmocom.de/" rel="noreferrer" target="_blank">http://www.sysmocom.de/</a><br>
=======================================================================<br>
* sysmocom - systems for mobile communications GmbH<br>
* Alt-Moabit 93<br>
* 10559 Berlin, Germany<br>
* Sitz / Registered office: Berlin, HRB 134158 B<br>
* Gesch?ftsf?hrer / Managing Directors: Holger Freyther, Harald Welte<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: Digital signature<br>
URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20160217/7dbd36fd/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.osmocom.org/pipermail/openbsc/attachments/20160217/7dbd36fd/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 17 Feb 2016 17:26:52 +0100<br>
From: Harald Welte <<a href="mailto:hwelte@sysmocom.de" target="_blank">hwelte@sysmocom.de</a>><br>
To: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
Cc: <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: Re: hnb_cs_lu.msc<br>
Message-ID: <20160217162652.GU5868@nataraja><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi Neels,<br>
<br>
On Wed, Feb 17, 2016 at 02:18:54PM +0100, Neels Hofmeyr wrote:<br>
> in osmo-iuh/doc/hnb_cs_lu.msc I find that after the location update<br>
> request from the UE, an identity request "should" follow from the CN.<br>
<br>
it is no 'should at all'. There are some "Common MM Procedures" that<br>
can be invoked by MM (on the network side) at any time. This includes,<br>
AFAIR:<br>
* IDENTITY REQ / RESP<br>
* AUTHENTICATION REQ / RESP<br>
* MM INFO<br>
<br>
So the network can at any point in time ask the MS/UE about any of its<br>
identities.<br>
<br>
> Yesterday I made my first pcap using our hNodeB and that weighty black UE<br>
> we use for testing, and saw that the MSC indeed sends out an identity<br>
> request at that time [1], however, the UE simply never responds to it.<br>
<br>
OsmoNITB was originally developed as part of security research, and thus<br>
we wanted to demonstrate the fact that we can query the IMSI and IMEI of<br>
every phone at a very early stage. This is why we always ask for the<br>
IMEI, and we ask for the IMSI if we don't already know it (because it<br>
was contained in the LU / CM SERV REQ, or because we know the TMSI and<br>
can use it to map to the IMSI).<br>
<br>
If there's no response from the phone, then it's likely something is<br>
going wrong somehwere in between. Do you see the request on the RUA<br>
interface towards the HNB? What does the HNB logging/tracing tell you<br>
about that message? What does a protocol trace on a UE with xgoldmon<br>
tell you?<br>
<br>
> My question: is the hnb_cs_lu.msc declarative and definitely correct, or<br>
> could it be that in 3G, UEs in general expect authentication first, as<br>
> the "osmo-iuh/pcap/UPP RANAP.pcap" suggests (starting at packet #335).<br>
<br>
No. There might still be situtaions where the IMSI is not known to the<br>
network at LU time, and the network must be able to obtain it via<br>
IDENTITY REQUEST before being able to obtain the auth quintuples and<br>
perform authentication.<br>
<br>
What else would you do if you'd get a LU with an unknown TMSI?<br>
<br>
--<br>
- Harald Welte <<a href="mailto:hwelte@sysmocom.de" target="_blank">hwelte@sysmocom.de</a>> <a href="http://www.sysmocom.de/" rel="noreferrer" target="_blank">http://www.sysmocom.de/</a><br>
=======================================================================<br>
* sysmocom - systems for mobile communications GmbH<br>
* Alt-Moabit 93<br>
* 10559 Berlin, Germany<br>
* Sitz / Registered office: Berlin, HRB 134158 B<br>
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 18 Feb 2016 12:56:20 +0100<br>
From: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
To: <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;<br>
merging to master<br>
Message-ID: <20160218115512.GA2630@dub6><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
The openbsc branches to use for testing IuPS and IuCS have changed,<br>
because Daniel and I have merged the branches.<br>
<br>
They used to be daniel/gprs-iu (IIRC) and sysmocom/cscn.<br>
Both are now merged as:<br>
<br>
sysmocom/iu<br>
<br>
Holger, this is relevant to our coverity configuration.<br>
<br>
<br>
We are still using other branches that may or may not be merged to their<br>
respective masters. I'd like to publicly record here why or why not we<br>
should merge them now. Please add any reasons you know.<br>
<br>
We're using master for Iu[h|CS|PS] in:<br>
<br>
libasn1c: * master<br>
libosmo-abis: * master<br>
libosmocore: * master<br>
openggsn: * master<br>
osmo-python-tests: * master<br>
osmo-iuh: * master<br>
<br>
Reasons NOT to merge to master in:<br>
<br>
openbsc: * sysmocom/iu<br>
- hardcoded kc and sres for testing<br>
- NITB and most probably osmo-bsc are not operational<br>
- A-interface not implemented in CSCN<br>
<br>
asn1c: * aper-prefix<br>
- ?<br>
<br>
libosmo-netif: * sysmocom/sctp<br>
- ?<br>
<br>
libosmo-sccp: * laforge/wip<br>
- ?<br>
<br>
Thanks for any additions...<br>
<br>
~Neels<br>
<br>
--<br>
- Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>> <a href="http://www.sysmocom.de/" rel="noreferrer" target="_blank">http://www.sysmocom.de/</a><br>
=======================================================================<br>
* sysmocom - systems for mobile communications GmbH<br>
* Alt-Moabit 93<br>
* 10559 Berlin, Germany<br>
* Sitz / Registered office: Berlin, HRB 134158 B<br>
* Gesch?ftsf?hrer / Managing Directors: Holger Freyther, Harald Welte<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: Digital signature<br>
URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20160218/3f7a1c48/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.osmocom.org/pipermail/openbsc/attachments/20160218/3f7a1c48/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 18 Feb 2016 19:43:18 +0100<br>
From: Harald Welte <<a href="mailto:laforge@gnumonks.org" target="_blank">laforge@gnumonks.org</a>><br>
To: Holger Freyther <<a href="mailto:holger@freyther.de" target="_blank">holger@freyther.de</a>><br>
Cc: <a href="mailto:baseband-devel@lists.osmocom.org" target="_blank">baseband-devel@lists.osmocom.org</a>, OpenBSC Mailing List<br>
<<a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a>>, <a href="mailto:osmocom-sdr@lists.osmocom.org" target="_blank">osmocom-sdr@lists.osmocom.org</a>,<br>
<a href="mailto:gmr@lists.osmocom.org" target="_blank">gmr@lists.osmocom.org</a><br>
Subject: Re: Moving from trac to a single redmine<br>
Message-ID: <20160218184318.GW4570@nataraja><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi Holger,<br>
<br>
let's move ahead and start with the migration, I can't wait to put all<br>
the various tickets into a public redmine.<br>
<br>
Thanks!<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>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 18 Feb 2016 19:52:55 +0100<br>
From: Holger Freyther <<a href="mailto:holger@freyther.de" target="_blank">holger@freyther.de</a>><br>
To: <a href="mailto:baseband-devel@lists.osmocom.org" target="_blank">baseband-devel@lists.osmocom.org</a>, OpenBSC Mailing List<br>
<<a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a>>, <a href="mailto:osmocom-sdr@lists.osmocom.org" target="_blank">osmocom-sdr@lists.osmocom.org</a>,<br>
<a href="mailto:gmr@lists.osmocom.org" target="_blank">gmr@lists.osmocom.org</a><br>
Subject: Re: Moving from trac to a single redmine<br>
Message-ID: <<a href="mailto:753DCDAF-0723-4EC5-8E3C-870B7D5959C5@freyther.de" target="_blank">753DCDAF-0723-4EC5-8E3C-870B7D5959C5@freyther.de</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
> On 18 Feb 2016, at 19:43, Harald Welte <<a href="mailto:laforge@gnumonks.org" target="_blank">laforge@gnumonks.org</a>> wrote:<br>
><br>
> Hi Holger,<br>
<br>
Hi all!<br>
<br>
<br>
><br>
> let's move ahead and start with the migration, I can't wait to put all<br>
> the various tickets into a public redmine.<br>
<br>
<br>
last weekend I used the "stock" redmine trac->redmine converter and the result is on <a href="http://projects.osmocom.org" rel="noreferrer" target="_blank">projects.osmocom.org</a>. It is not perfect but I think good enough to start moving. We see that certain formating needs a post-import correction but that should be doable by all of us quickly.<br>
<br>
My plan/timeline (on short notice but I don't expect a major resistence so I hope it is fine):<br>
<br>
* Patch the redmine importer to not import tickets. This hopefully allows me to import other tracs at the same time (and re-add the security tickets by hand)<br>
* Friday evening set the tracs to read-only (I probably move the account file away)<br>
* Saturday/Sunday do the migration of the trac.<br>
* Make it available on <a href="http://osmocom.org" rel="noreferrer" target="_blank">osmocom.org</a> (currently it is <a href="http://projects.osmocom.org" rel="noreferrer" target="_blank">projects.osmocom.org</a>)<br>
* Keep the trac as read-only version for now<br>
<br>
In the mid-term:<br>
<br>
* We need to post-process some pages and move them around to have a better structure<br>
* Add permanent redirects from the trac to <a href="http://osmocom.org" rel="noreferrer" target="_blank">osmocom.org</a> for "approved" content. This way normal traffic will automatically move to the new page and then we can look at the access.log for which pages still need a re-direct.<br>
<br>
<br>
<br>
any objections?<br>
<br>
holger<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 18 Feb 2016 21:02:42 +0100<br>
From: Holger Freyther <<a href="mailto:holger@freyther.de" target="_blank">holger@freyther.de</a>><br>
To: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
Cc: <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: Re: branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;<br>
merging to master<br>
Message-ID: <<a href="mailto:D8449C8C-5FD0-4A03-88FA-F0EBBA3ADD41@freyther.de" target="_blank">D8449C8C-5FD0-4A03-88FA-F0EBBA3ADD41@freyther.de</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
<br>
> On 18 Feb 2016, at 12:56, Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>> wrote:<br>
><br>
> The openbsc branches to use for testing IuPS and IuCS have changed,<br>
> because Daniel and I have merged the branches.<br>
><br>
> They used to be daniel/gprs-iu (IIRC) and sysmocom/cscn.<br>
> Both are now merged as:<br>
><br>
> sysmocom/iu<br>
><br>
> Holger, this is relevant to our coverity configuration.<br>
<br>
and the build is broken.<br>
<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:126:1: warning: "ENHANCEDRELOCATIONCOMPLETEREQUESTIES_RANAP_EXTENDEDRNC_ID_PRESENT" redefined<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:125:1: warning: this is the location of the previous definition<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:436:1: warning: "RANAP_ENHANCEDRELOCATIONINFORMATIONREQUESTIES_RANAP_IUSIGNALLINGCONNECTIONIDENTIFIER_PRESENT" redefined<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:434:1: warning: this is the location of the previous definition<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:437:1: warning: "RANAP_ENHANCEDRELOCATIONINFORMATIONREQUESTIES_RANAP_GLOBALCN_ID_PRESENT" redefined<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:435:1: warning: this is the location of the previous definition<br>
In file included from /home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_common.h:592,<br>
from /home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:7,<br>
from iu.c:26:<br>
/home/builder/coverity/install-iuh/include/osmocom/ranap/ranap_ies_defs.h:856: error: redefinition of typedef 'RANAP_RAB_SetupOrModifiedItemIEs_t'<br>
../../include/openbsc/iu.h:8: note: previous declaration of 'RANAP_RAB_SetupOrModifiedItemIEs_t' was here<br>
In file included from iu.c:31:<br>
/home/builder/coverity/install-iuh/include/asn1c/asn1helpers.h: In function 'OCTET_STRING_noalloc':<br>
/home/builder/coverity/install-iuh/include/asn1c/asn1helpers.h:26: warning: assignment discards qualifiers from pointer target type<br>
iu.c: In function 'ranap_handle_co_rab_ass_resp':<br>
iu.c:273: warning: implicit declaration of function 'ranap_free_rab_setupormodifieditemies'<br>
make[3]: *** [iu.o] Error 1<br>
make[3]: Leaving directory `/home/builder/coverity/source-iuh/openbsc/openbsc/src/libiu'<br>
make[2]: *** [all-recursive] Error 1<br>
make[2]: Leaving directory `/home/builder/coverity/source-iuh/openbsc/openbsc/src'<br>
make[1]: *** [all-recursive] Error 1<br>
make[1]: Leaving directory `/home/builder/coverity/source-iuh/openbsc/openbsc'<br>
make: *** [all] Error 2<br>
<br>
branches used:<br>
<br>
asn1c<br>
* aper-prefix<br>
layer1-api<br>
* master<br>
libasn1c<br>
* master<br>
libosmo-abis<br>
* master<br>
libosmo-dsp<br>
* master<br>
libosmo-netif<br>
* sysmocom/sctp<br>
libosmo-sccp<br>
* laforge/wip<br>
libosmocore<br>
* master<br>
libsmpp34<br>
* master<br>
openbsc<br>
* sysmocom/iu<br>
openggsn<br>
* master<br>
osmo-bts<br>
* master<br>
osmo-gmr<br>
* master<br>
osmo-iuh<br>
* master<br>
osmo-pcu<br>
* master<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Thu, 18 Feb 2016 23:45:44 +0100<br>
From: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>><br>
To: Daniel Willmann <<a href="mailto:dwillmann@sysmocom.de" target="_blank">dwillmann@sysmocom.de</a>><br>
Cc: <a href="mailto:openbsc@lists.osmocom.org" target="_blank">openbsc@lists.osmocom.org</a><br>
Subject: sysmocom/iu: your commits from today<br>
Message-ID: <20160218224544.GA18542@dub6><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Moin Daniel :)<br>
<br>
(1)<br>
About ebd4d820b3b0d7ba5db3b25a14f407d0c7276044<br>
"libiu: Use custom setupormodifieditemies function"<br>
<br>
It seems you forgot to commit the actual function definition of<br>
ranap_decode_rab_setupormodifieditemies_fromlist()<br>
I got the caller of it only and thus can't compile as-is.<br>
<br>
<br>
(2)<br>
About 38e2f1bca4e43414ed39a938d7c5d8bafe5e8533<br>
"<br>
Revert "iu.c: avoid warning by declaring ranap_free_rab_setupormodifieditemies()"<br>
<br>
There should be no need to silence this warning, the ranap_free_*<br>
functions are declared in libranap headers. In any case this will only<br>
obscure any real issue. Maybe osmo-iuh was not rebuilt completely<br>
(including generation of the c files from the python script).<br>
<br>
This reverts commit 05ae5b1245f95bf765b42e49af7b2596e013f0a0.<br>
"<br>
<br>
I declared ranap_free_rab_setupormodifieditemies() like that because it is<br>
indeed not declared in a header that is installed. Also a grep tells me<br>
that no ranap_free_* is found in any osmo-iuh header file at all.<br>
I also did a 'make regen' in osmo-iuh/src/ to no avail.<br>
By 'libranap headers' I assume you mean libosmo-ranap, or is there a<br>
libranap I'm not aware of yet?<br>
<br>
If the ranap_free_* aren't in headers yet, I agree that they should be. I<br>
wanted to silence the warning without being sucked down the rabbit hole of<br>
autogenerated asn1 stuff. Any suggestions: more than welcome.<br>
<br>
<br>
(3)<br>
In general, I would welcome to see more of your WIP work in publicly<br>
visible private branches, maturing as you go and merged to sysmocom/iu<br>
once ready. For one, having a backup of your work-in-progress in the git<br>
repos makes it harder to lose it due to hardware failure. More important<br>
for me though is that I can see what you're up to, e.g. I could possibly<br>
find the ranap_..._fromlist() function defintion now. It's of course<br>
opening up your "most private" code developments to the outside world,<br>
possibly some stupid commits will be seen by one or two hacker peers, but<br>
I think it's a healthy premise that we all commit mostly bollocks and all<br>
needs refinement anyway... once again: push it! :)<br>
<br>
<br>
Ah, push it<br>
Push it good<br>
Ah, push it<br>
Pu-Push it real good<br>
-- Salt N Pepa (1987)<br>
<br>
<br>
As always I'm open to opinions and suggestions...<br>
<br>
~Neels<br>
<br>
<br>
--<br>
- Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" target="_blank">nhofmeyr@sysmocom.de</a>> <a href="http://www.sysmocom.de/" rel="noreferrer" target="_blank">http://www.sysmocom.de/</a><br>
=======================================================================<br>
* sysmocom - systems for mobile communications GmbH<br>
* Alt-Moabit 93<br>
* 10559 Berlin, Germany<br>
* Sitz / Registered office: Berlin, HRB 134158 B<br>
* Gesch?ftsf?hrer / Managing Directors: Holger Freyther, Harald Welte<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: Digital signature<br>
URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20160218/e2656577/attachment.bin" rel="noreferrer" target="_blank">http://lists.osmocom.org/pipermail/openbsc/attachments/20160218/e2656577/attachment.bin</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
OpenBSC mailing list<br>
<a href="mailto:OpenBSC@lists.osmocom.org" target="_blank">OpenBSC@lists.osmocom.org</a><br>
<a href="https://lists.osmocom.org/mailman/listinfo/openbsc" rel="noreferrer" target="_blank">https://lists.osmocom.org/mailman/listinfo/openbsc</a><br>
<br>
<br>
------------------------------<br>
<br>
End of OpenBSC Digest, Vol 16, Issue 19<br>
***************************************<br>
</blockquote></div><br></div></div></div></div></div>