osmocom-commitlog July 2017

osmocom-commitlog@lists.osmocom.org

1 participants
223 discussions

openbsc.git branch pmaier/aoip3 created. 0.15.0-930-gc54a5f3d6
by gitosis＠osmocom.org 31 Jul '17

31 Jul '17

This 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 "Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, pmaier/aoip3 has been created at c54a5f3d69c18b7b9cc236eca5b8ef8ad7481f34 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=c54a5f3d69c18b7b9cc236eca5b8ef8a… commit c54a5f3d69c18b7b9cc236eca5b8ef8ad7481f34 Author: Philipp Maier <pmaier(a)sysmocom.de> Date: Mon Jul 31 19:19:34 2017 +0200 mgcp: remove proactive DLCX To prevent a situation where one ore more seized enpoints stay seized after an MSC crash (information loss, endpoints can not be released) we send a DLCX command before making new connections on the MGCP-GW. This method is loud and hackish. Remove all functionality that sends a DLCX before making a new connection. Enable force_realloc functionality in the MGCP code in order to have seized enpoints automatically released on new connections, in case they are seized ----------------------------------------------------------------------- hooks/post-receive -- Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-bts.git branch pmaier/octdynts updated. 0.4.0-563-g4a111fc
by gitosis＠osmocom.org 31 Jul '17

31 Jul '17

This 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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, pmaier/octdynts has been updated via 4a111fc5e9e0fb7a5d330286315cb0f880342e21 (commit) via afee2fd264f8d806859ae02dc3b34039e97c459d (commit) from dc61555fe0d4bc1142c9de433ed9f17a776bab91 (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/osmo-bts/commit/?id=4a111fc5e9e0fb7a5d330286315cb0f… commit 4a111fc5e9e0fb7a5d330286315cb0f880342e21 Author: Philipp Maier <pmaier(a)sysmocom.de> Date: Mon Jul 31 18:09:45 2017 +0200 add more debug output, to be removed later http://cgit.osmocom.org/osmo-bts/commit/?id=afee2fd264f8d806859ae02dc3b3403… commit afee2fd264f8d806859ae02dc3b34039e97c459d Author: Philipp Maier <pmaier(a)sysmocom.de> Date: Mon Jul 31 16:09:19 2017 +0200 pick_pchan ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-octphy/l1_if.c | 29 ++++++++++++++++++++++++++--- src/osmo-bts-octphy/l1_oml.c | 10 ++++++++-- 2 files changed, 34 insertions(+), 5 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-bts.git branch master updated. 0.4.0-571-gdc46999
by gitosis＠osmocom.org 31 Jul '17

31 Jul '17

1 0

osmo-bts.git branch pmaier/octdynts created. 0.4.0-561-gdc61555
by gitosis＠osmocom.org 31 Jul '17

31 Jul '17

This 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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, pmaier/octdynts has been created at dc61555fe0d4bc1142c9de433ed9f17a776bab91 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=dc61555fe0d4bc1142c9de433ed9f17… commit dc61555fe0d4bc1142c9de433ed9f17a776bab91 Author: Philipp Maier <pmaier(a)sysmocom.de> Date: Mon Jul 31 13:27:48 2017 +0200 non-working-test ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-bts.git branch master updated. 0.4.0-570-g82987f7
by gitosis＠osmocom.org 30 Jul '17

30 Jul '17

This 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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via 82987f7a7dd35451b75326b34e36c8f83289f6f6 (commit) via d6da809d2fe35a00e03b0ae1422536245acd28be (commit) from 69e0461674611425beefa4753d8743978259f19c (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/osmo-bts/commit/?id=82987f7a7dd35451b75326b34e36c8f… commit 82987f7a7dd35451b75326b34e36c8f83289f6f6 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 30 16:38:18 2017 +0200 L1SAP: Print chan_nr and link_id always as hex The RSL Channel ID is best read / interpreted as hex value, not as decimal, primarily due to the fact that it is a bit-mask of various fields. Change-Id: I9b72a67407870b485e7f7e8a72fa1ad30fc8ed4d http://cgit.osmocom.org/osmo-bts/commit/?id=d6da809d2fe35a00e03b0ae14225362… commit d6da809d2fe35a00e03b0ae1422536245acd28be Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 30 16:03:32 2017 +0200 TRX / VIRT-PHY: Make check for BCCH/CCCH more specific In bts_model_l1sap_down() we want to identify BCCH/CCCH channel numbers, but our check is a bit non-specific. Let's make the check more specific to only cover the BCCH, Uplink CCCH and Downlink CCCH C-bits as defined n 3GPP TS 08.58 Section 9.3.1 Change-Id: Ia20ab09b96c87c0dfbfaf98e5b2a8d36423fac67 ----------------------------------------------------------------------- Summary of changes: src/common/l1sap.c | 16 ++++++++-------- src/osmo-bts-trx/l1_if.c | 4 ++-- src/osmo-bts-virtual/l1_if.c | 4 ++-- 3 files changed, 12 insertions(+), 12 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-bts.git branch master updated. 0.4.0-568-g69e0461
by gitosis＠osmocom.org 30 Jul '17

30 Jul '17

This 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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via 69e0461674611425beefa4753d8743978259f19c (commit) from bbd4d54e46b3d2ed7d134b8b103abd1683616b9f (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/osmo-bts/commit/?id=69e0461674611425beefa4753d87439… commit 69e0461674611425beefa4753d8743978259f19c Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Jul 19 16:03:25 2017 +0200 VIRT-PHY: Print NOTICE log message from unimplemented stubs There are plenty of functions stubbed out in osmo-bts-virtual, let's print a NOTICE level log message to be able to correlate any kind of erroneous behavior with the fact that a given function has no actual implementation. Change-Id: Ib607d192f90af7fb2d5a8747de5527f39e3cfefa ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-virtual/bts_model.c | 8 ++++++++ src/osmo-bts-virtual/main.c | 5 +++++ 2 files changed, 13 insertions(+) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

libosmocore.git branch master updated. 0.9.6-356-ga8a8d397
by gitosis＠osmocom.org 30 Jul '17

30 Jul '17

This 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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via a8a8d3977dc3b31352f8a87ca005763677bd7e8c (commit) from 977231cc3e701366e438f97f4e441670c9c130ad (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/libosmocore/commit/?id=a8a8d3977dc3b31352f8a87ca005… commit a8a8d3977dc3b31352f8a87ca005763677bd7e8c Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 30 15:16:18 2017 +0200 RSL: Add support for RSL_CHAN_OSMO_PDCH to rsl_dec_chan_nr() Change-Id: Icc772285636c06e1075a89809f0ac379d7a0002c ----------------------------------------------------------------------- Summary of changes: src/gsm/rsl.c | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

osmo-pcu.git branch master updated. 0.2-927-g0cd8e4e
by gitosis＠osmocom.org 30 Jul '17

30 Jul '17

This 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 "UNNAMED PROJECT". The branch, master has been updated via 0cd8e4eadea3fc4ec709b102e428f7a47836a7e3 (commit) from bc219d5450fc022afaec8f4a37d929c815685b89 (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/osmo-pcu/commit/?id=0cd8e4eadea3fc4ec709b102e428f7a… commit 0cd8e4eadea3fc4ec709b102e428f7a47836a7e3 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 29 22:11:34 2017 +0200 README: Clarify that fixed allocations have been revmoved from 3GPP specs In Release 5, Fixed Allocations were removed as part of a "GPRS simplification project" inside 3PGPP. This means that any MS compatible with Rel-5 or higher may not support it, which makes implementation in the PCU af historical interest only. See Tdoc GP-021277 for the actual removal, it happened at 5.0.0 time. Change-Id: I8138bc0a47d3468b67cec866447fd4b0fc69d4c5 ----------------------------------------------------------------------- Summary of changes: README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

wireshark.git branch laforge/pending updated. 8ab28948017c08c91d20495935ddaaef19116d28
by gitosis＠osmocom.org 30 Jul '17

30 Jul '17

This 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 "wireshark with Osmocom specific dissectors". The branch, laforge/pending has been updated discards c43624265a95c41acaa31e40cc8170aa96b8c506 (commit) discards b778aa5f88de68870cc6af4a7aaf90d6b2ddf90c (commit) discards ae91d940ccf4d3f43500b7da8a205819674e825e (commit) discards 787b79baf2ebb77c44dd17fc2b3386ec3c539395 (commit) discards 4e81008d44c7347b195677a155c592f7950a68d8 (commit) discards f3ae89b3f3ef6b79ca9c3681075ebfbf9afe0c9e (commit) discards 7f980d77a77f3c23dd2a378613a4a904848eb7c1 (commit) discards 5f6062e7dd00d80902a915f47465a42af66eed74 (commit) via 8ab28948017c08c91d20495935ddaaef19116d28 (commit) via 4915f4f40012095d63fe545415f3465baf5db1dc (commit) via f719da8599dae95e7b467d39978470690f605627 (commit) via dcba0bf9d24bb9f1631f1c01b37cfb5b77fdd855 (commit) via a8a3669393b6d6cde9c00c7b7317f62821c8d140 (commit) via 5708294c1eaffe035c47b806510cf475a4dca190 (commit) via d28c4fa82dc530caff964ec7a60dc92978ef1d99 (commit) via c259f80de7553d269b41d67af9c3b504beef5c5b (commit) via 7f8079d9db16f824256b41d676debd0c8b773778 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (c43624265a95c41acaa31e40cc8170aa96b8c506) \ N -- N -- N (8ab28948017c08c91d20495935ddaaef19116d28) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. 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/wireshark/commit/?id=8ab28948017c08c91d20495935ddaa… commit 8ab28948017c08c91d20495935ddaaef19116d28 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jan 7 18:08:21 2017 +0100 WIP: Qualcomm DIAG Protocol support Change-Id: I0bd06c46e00570005a1148860954a77c8f5445a8 http://cgit.osmocom.org/wireshark/commit/?id=4915f4f40012095d63fe545415f346… commit 4915f4f40012095d63fe545415f3465baf5db1dc Author: Harald Welte <laforge(a)gnumonks.org> Date: Fri Dec 2 16:44:20 2016 +0100 WIP: RSL Ericsson support Change-Id: I1e9b3c08848f4feb60361e629d7225b6d2e1dcbd http://cgit.osmocom.org/wireshark/commit/?id=f719da8599dae95e7b467d39978470… commit f719da8599dae95e7b467d39978470690f605627 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Oct 26 22:38:20 2016 +0200 HACK: Hand GPRS RLC payload to GPRS LLC dissector this is an ugly hack, as there is no code for packet re-assembly in betwween, i.e. we only get proper dissection if the LLC message was fitting entirely into one RLC block. Nevertheless, sufficient to see things like RAU, ATTACH, IDENTITY procedures. Change-Id: I1fc488aa58353e5f4264b940f9f4c18987148a7d http://cgit.osmocom.org/wireshark/commit/?id=dcba0bf9d24bb9f1631f1c01b37cfb… commit dcba0bf9d24bb9f1631f1c01b37cfb5b77fdd855 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Oct 26 20:09:31 2016 +0200 WIP: Jacob's EGPRS patch ... with add_new_data_source() to visualize the re-aligned bits Change-Id: I1604dceaf3d91228e87712e099c8a209ff812f4a http://cgit.osmocom.org/wireshark/commit/?id=a8a3669393b6d6cde9c00c7b7317f6… commit a8a3669393b6d6cde9c00c7b7317f62821c8d140 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 17 16:22:19 2016 +0200 l2tp: Introduce preference for default pseudowire In some cases, the establishment of the L2TP session is not captured in the pcap file, and thus wireshark cannot determine the l2tp pseudowire to be used for decode. So rather than using a ocmpile-time hard-coded default of cisco hdlc, let's introduce a prference where the user can select the default pseudowire in such cases. Change-Id: I44a6373d4812c9ab5a919514273a41a2ab57142c http://cgit.osmocom.org/wireshark/commit/?id=5708294c1eaffe035c47b806510cf4… commit 5708294c1eaffe035c47b806510cf475a4dca190 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 16 15:39:17 2016 +0200 L2TP: Add preference to select Ericsson HDLC flavor At some point over the wireshark last years, the connection between the L2TP dissector and the Ericsson HDLC dissector (packet-ehdlc.c) got broken. I cannot poinpoint the exact change when it broke. However, traces with Ericsson L2TP that used to display correctly no longer do so. The problem with Ericsson L2TP is that they simply re-use the HDLC pseudowire (0x0006), but then have frames completely different than what's specified in the RFCs for that. To address this, let's add a protocol preference to allow the user to choose. Change-Id: Idce022ef0f233c01ecffc67dca7f428bde31ef6b http://cgit.osmocom.org/wireshark/commit/?id=d28c4fa82dc530caff964ec7a60dc9… commit d28c4fa82dc530caff964ec7a60dc92978ef1d99 Author: Harald Welte <laforge(a)gnumonks.org> Date: Fri Jul 28 19:23:15 2017 +0200 gprs-llc: Don't attempt to decode Dummy UI Command As explained by 3GPP TS 44.064 Section 6.4.2.2 there are Dummy UI Commands which are never generated by a LLC entity, but nevertheless received by a LLC entity. They are generated by the underlying network-side RLC/MAC entity a as a means to artificially delay the release of a downlink TBF. We introduce a new "llcgprs.dummy_ui" boolean field on which the user can match to filter our such messages, if needed. Change-Id: Ie8fcb42cbd66a7e5b77849f0bc5a3630d0d54a9c http://cgit.osmocom.org/wireshark/commit/?id=c259f80de7553d269b41d67af9c3b5… commit c259f80de7553d269b41d67af9c3b504beef5c5b Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 30 15:52:38 2017 +0200 GSMTAP: Treat PDTCH identical to PACCH (hand into packet-gsm-rlcmac.c) The RLC/MAC dissector decodes both signalling (PACCH) and data (PDTCH) RLC/MAC blocks, so let's make sure we dispatch both logical channels into that dissector. Change-Id: Ia26a1ba74468a49da071185cc5ee876ade907207 http://cgit.osmocom.org/wireshark/commit/?id=7f8079d9db16f824256b41d676debd… commit 7f8079d9db16f824256b41d676debd0c8b773778 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 30 15:49:21 2017 +0200 GSMTAP: Proper name for PDTCH (not PDCH) PDCH is the physical channel name, while PDTCH is one of the logical channels (goether with PTCCH and PACCH) on the PDTCH. Let's call it by its proper name, rather than keeping the misnomer. Change-Id: I724fcfba595c9c861b64a30d5510468ec007424c ----------------------------------------------------------------------- Summary of changes: epan/dissectors/packet-gsmtap.c | 3 ++- epan/dissectors/packet-gsmtap.h | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- wireshark with Osmocom specific dissectors

1 0

osmo-pcu.git branch master updated. 0.2-926-gbc219d5
by gitosis＠osmocom.org 29 Jul '17

29 Jul '17

This 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 "UNNAMED PROJECT". The branch, master has been updated via bc219d5450fc022afaec8f4a37d929c815685b89 (commit) via cd34dd3b2bd98c3d7d29adaaa08b48b76cc4f0ef (commit) via f7740aa44ba754ca42b8b454438e23dd8c1269ea (commit) from 05d7b5dd590886d706d25cc05315a46cfaa648aa (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/osmo-pcu/commit/?id=bc219d5450fc022afaec8f4a37d929c… commit bc219d5450fc022afaec8f4a37d929c815685b89 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 29 13:42:27 2017 +0200 GSMTAP: Ad PTCCH as separate gsmtap category This allows us to send GSMTAP for PTCCH only if requested by user/vty Change-Id: Id720f4bebdce7f6152fbddddbe05036638c5866e http://cgit.osmocom.org/osmo-pcu/commit/?id=cd34dd3b2bd98c3d7d29adaaa08b48b… commit cd34dd3b2bd98c3d7d29adaaa08b48b76cc4f0ef Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 29 13:37:48 2017 +0200 GSMTAP: Fix logical channel of downlink PTCCH Change-Id: I29ecc968d56d4d0165cffa206297c42d6fb02cf4 http://cgit.osmocom.org/osmo-pcu/commit/?id=f7740aa44ba754ca42b8b454438e23d… commit f7740aa44ba754ca42b8b454438e23dd8c1269ea Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 29 13:29:37 2017 +0200 GSMTAP: Fix channel type for data blocks: PDTCH instead of PACCH PACCH is used only for RLC/MAC control messages, while PDTCH is used for data. Change-Id: I6c912e17d8c8d4178096679a541e61eeeb4b6643 ----------------------------------------------------------------------- Summary of changes: src/bts.cpp | 4 ++-- src/bts.h | 1 + src/gprs_rlcmac_sched.cpp | 2 +- src/pcu_l1_if.cpp | 3 ++- src/pcu_vty.c | 2 ++ 5 files changed, 8 insertions(+), 4 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog July 2017