This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, sysmocom/iu has been updated
via fc68c83ddbda55fc2aaa908a3a6a6fca2af71761 (commit)
via 74101106a1114d819dfce83cd5a50837c8bd5d0e (commit)
via db916bfd8dcceaeb0414ea0628e99a8e7955e660 (commit)
via a54358879f1ab928659568ebd6547fc65265f662 (commit)
via a54b47b04876152d6f5473d528480a67ccc89803 (commit)
via 3b922064a478f3a403d3a40d3f22c9a5675390fa (commit)
via 5b3fd465d16547f1175b211dd5366123f260fedb (commit)
from 0991c684d342c292e8e5b0fb42f93fc615643580 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=fc68c83ddbda55fc2aaa908a3a6a6fca2af71761
commit fc68c83ddbda55fc2aaa908a3a6a6fca2af71761
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 15:29:52 2016 +0200
Support raw IPv4 address in RAB Assignment Response
There are different Iu dialects in terms of encoding the
transport layer address inside RAB Assignment req + resp.
Let's be liberal in what we accept, and simply use the length
as an indicator of the format. Wireshark uses similar heuristics.
http://cgit.osmocom.org/openbsc/commit/?id=74101106a1114d819dfce83cd5a50837c8bd5d0e
commit 74101106a1114d819dfce83cd5a50837c8bd5d0e
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 15:23:41 2016 +0200
RAB Assignment Response: Handle TEID changes
When the RNC confirms the RAB Assignment, it can each time indicate a
new TEID for the GTP-U endpoint on the RNC side. We need to update our
information about the PDP context and include that in the UPDATE PDP
CONTEXT that we're sending towards the GGSN. This is similar to
updating the RNC-side IP address of the GTP endpoint.
http://cgit.osmocom.org/openbsc/commit/?id=db916bfd8dcceaeb0414ea0628e99a8e7955e660
commit db916bfd8dcceaeb0414ea0628e99a8e7955e660
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 13:36:48 2016 +0200
iu_rab_act_ps: Use GGSN-side TEI in RAB Assignment Requeset
When we send the RAB Assignment Request to the RNC, we need
to tell it the GGSN-side TEI for data, not "our" (SGSN side)
TEID.
In the RAB-Assignment.req we inform the RNC of the TEID on the GGSN
side, and in the RAB-Assignment.resp the RNC informs us of the TEID
on the RNC side.
http://cgit.osmocom.org/openbsc/commit/?id=a54358879f1ab928659568ebd6547fc65265f662
commit a54358879f1ab928659568ebd6547fc65265f662
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 12:43:21 2016 +0200
Identify PDP context by RAB ID, not TEI
When receiving an RAB-Assignment response from the RNC,
we should use the RAB ID (=NSAPI) to resolve the PDP context.
We cannot use the TEID, as the TEID chosen by the RNC for this RAB has
no relationship to the TEID we were using for the RAB-Assignment
request. TEIDs are local to each of the peer, like UDP port numbers.
http://cgit.osmocom.org/openbsc/commit/?id=a54b47b04876152d6f5473d528480a67ccc89803
commit a54b47b04876152d6f5473d528480a67ccc89803
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 12:21:45 2016 +0200
libiu: Fix missing break statements in switch in cn_ranap_handle_co()
http://cgit.osmocom.org/openbsc/commit/?id=3b922064a478f3a403d3a40d3f22c9a5675390fa
commit 3b922064a478f3a403d3a40d3f22c9a5675390fa
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun May 1 10:59:12 2016 +0200
SGSN: Use PDP Context NSAPI as RAB ID
As Dieter has pointed out, the RANAP spec requires the RAB ID to be
equal to the NSAPI of the PDP context for which it is established.
http://cgit.osmocom.org/openbsc/commit/?id=5b3fd465d16547f1175b211dd5366123f260fedb
commit 5b3fd465d16547f1175b211dd5366123f260fedb
Author: Harald Welte <laforge at gnumonks.org>
Date: Sat Apr 30 22:04:50 2016 +0200
Fix parsing of auto-generated config file
When starting with empty config file, saving it by 'write file',
and then re-starting osmo-cscn, it would complain:
Error occurred during reading below line:
long name Osmocom Circuit-Switched Core Network
The problem is that the vty parser is configured to expect a single
token and not a list of tokens here, but we initialize the default value
with multiple words (which are treated as separate token).
-----------------------------------------------------------------------
Summary of changes:
openbsc/include/openbsc/gprs_sgsn.h | 5 ----
openbsc/src/gprs/gprs_gmm.c | 4 +--
openbsc/src/gprs/gprs_sgsn.c | 19 --------------
openbsc/src/gprs/sgsn_libgtp.c | 52 +++++++++++++++++++++++++++----------
openbsc/src/libiu/iu.c | 8 +++---
openbsc/src/osmo-cscn/cscn_main.c | 2 +-
6 files changed, 45 insertions(+), 45 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)