OpenBSC

openbsc@lists.osmocom.org

9 participants
4171 discussions

by Reza Hosseini

Dear Osmocom developpers, I already installed osmocomnitb and now i am trying to Show the core Network vulnerablites in Wireshark. In order to use existing Osmocom libraries for GSUP protocol processing and USSD coding / decoding, I have to use the file "osmo-hlr / src / osmo-euse-demo.c" in my osmocom directory, the " http: // git "contains. osmocom.org/osmo-hlr/tree/src/osmo-euse-demo.c "Pool. But i don’t find the following libarries to patch it. #include <string.h> #include <stdio.h> #include <errno.h> #include <signal.h> #include <osmocom/core/msgb.h> #include <osmocom/core/select.h> #include <osmocom/core/application.h> #include <osmocom/core/utils.h> #include <osmocom/core/logging.h> #include <osmocom/gsm/gsup.h> #include <osmocom/gsm/gsm0480.h> #include <osmocom/gsm/protocol/gsm_04_80.h> #include <osmocom/gsupclient/gsup_client.h> #include <osmocom/hlr/logging.h> How can i have Access to the .exe (already maked) of this library. Kind regads, Reza

5 years, 4 months

New Mobile Phone Models - Latching Issue using OSMO-NITB - Connection Drops approx after 3 Minutes

by Ron

Hi Community, Does anyone experiences, in newer phone models, that after a successful latched to OSMO-NITB, it will dropped its connection in a few minutes? We have experienced this issue to the following mobile phone models: 1. iPhone X - Software Version - 13.3 (Connection drops approximately after 3 minutes) 2. Samsung S10 (Connection drops after 1 - 3 minutes) 3. Samsung Note 9 Best Regards, Ron Menez

5 years, 5 months

Use of anytype in Osmocom TTCN-3 tests / TITAN

by Harald Welte

Hi Vadim, 22:22 < fixeria> LaF0rge: oh, we already have 'template anytype' in pcu/PCUIF_RAW_Components.ttcn 22:23 < fixeria> ... and that's my code :P 22:26 < fixeria> yay, it even compiles 22:39 < fixeria> but does not work as expected: "error: Type mismatch: a value or template of type `(a)Osmocom_Types.anytype' was expected instead of `integer'" 22:41 < fixeria> I am testing against uint8_t which is defined exactly in Osmocom_Types :/ 22:52 < fixeria> LaF0rge: pespin_: https://pastebin.com/EL9JUqq9 Please see https://www.eclipse.org/forums/index.php?t=msg&th=1074288&goto=1721710&#msg… for how to use anytype in TITAN So if I modify the last line of Osmocom_Types.ttcn with your patch from https://pastebin.com/EL9JUqq9 attached to this: } with { encode "RAW"; variant "FIELDORDER(msb)" extension "anytype OCT1" } The errors about the non-existant OCT1 field in anytype are gone. This is of course not nice, but maybe a work-around to explicitly list those types at the end for now? Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 5 months

D-GSM merge / open question on GT vs. IPA name

by Harald Welte

Hi Neels, some week[s] ago, you mentioned that the D-GSM merge is blocked around the question on how the Global Title vs. IPA-name is to be resolved. Sorry for not getting back any sooner, but I am simply not finding the required amount of time to investigate this topic at the moment. My personal opinion is that it should be a binary blob (buffer + length) and nobody should make any assumptions about the contents. This way we can store whatever we want in it, and I believe we're increasing possible use cases where our HLR would have to work with "stateless" translators between GSUP and MAP. After all, let's say we receive a LU from a subscriber roaming in MAP-land, then that request arrives with the GT of the MSC/VLR. If we can natively "digest" such values, then the translator would not require any state beyond the currently processed transaction (LU/ISD). If we can not, then the translator would have to keep long-term state such as tables to map MAP-GT to IPA name or the like. And that's of course more effort there, and volatile state that you'd need to synchronize in case of high availability or fail-over scenarios, etc. I of course also know none of this is any current use case that any of the sysmocom customers is funding sysmocom (and hence you) to spend time on. So in the end, I'll leave it to you to decide. If you think the effort for becoming "buffer+length" aware is relatively minimal (let's say up to two days?) then by all means, implement that. If you think it's more work, then please go for the faster route of not considering non-NUL-terminated strings as identifiers for "GSUP" peers. In any case, I am happy to merge the D-GSM patch series once you think it should be merged. I put it in your trusted hands. After all, we had a tagged release only 7 commits ago (well, 5 of those are actually already D-GSM related) in osmo-hlr, and should there be any fall-out from the merge, we still have quite some time until some new tagged release will happen a few months down the road. Thanks! Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 6 months

Commercial MSs do not see the network

by Tomcsányi, Domonkos

Hi All, I have been dealing with a weird issue in the past couple of days. I needed to quickly check something about some phones, therefore I created an Osmocom CNI based 2G network. I have done this multiple times in the past even with OsmocomBB transceiver, however in the past some years I was not active in 2G, was more focused on 4G. I was very happy to see, that all familiar things I initially liked about osmocom are still in place/improved a lot (meaningful config files, simple VTY interface, a LOT more and better documentation). So the network is up and running fine, the setup consists of a laptop and a USRP B210 without GPSDO. Then I tried to attach some phones to it, and hit an issue: * Samsung S6, S7 - does not detect the network, even if I put in a SIM card that has previously been in a phone that was already attached * iPhone X - does not detect the network I first fiddled with the power settings, basically trying to turn it down a little bit (initially tx attenuation was at 0, so I turned it 10-20), because range is not needed, but I know distortion can happen when driving SDR HW to its max capacity. No change in the above. Then I turned quickly to gr-gsm and rtl-sdr to see if I'm transmitting properly, the network was detected and C0 decoded properly. Next I tried with a Motorola C115 (yeah, I still have some lying around :)), and it attached to the network without any issue. Finally something that works as expected, right? Last but not least I tried with a Nokia 4.2 phone, which also attached to the network immediately without any issue. So the bottom line is: what could cause this behavior? Is it possible that the USRP B210's accuracy is just not enough for newer phones? If yes how come the Nokia still attached, it is quite a recent phone with Qcomm chipset. I was also thinking if it is a Samsung vs Qualcomm thing, but then the iPhone should have at least detected the network. I tried with different SIM cards as well (not that it would make any difference...but I didn't have any better idea), and also with different bands and ARFCNs (900 and 1800). Antenna used is a VERT900. Configuration: unmodified standard config that came with the binary packages - except for MCC, MNC, rx gain, tx attenuation and max_power_red. I also tried to specify valid and also 'invalid' (unknown) MCC-MNC combinations to see if maybe newer Android/iOS only lists networks that advertise a known combination (again this would be very weird, but I just had no better ideas in the end). Anybody have any recent experience with COTS MSs and OsmoBTS(-TRX) based network? Any input is much appreciated, thanks. Cheers, Domi p.s. It is simply awesome to experience the power of opensource when dealing with 2G. Every step of the way above I was using software created and shared by you guys. It is a great feeling, had to share it :-).

5 years, 6 months

CBS + ETWS + CMAS + Limesdrmini

by Radiarisainana Sitraka

Hi, I follow this tutorial : Version 10 - History - Cell Broadcast - Cellular Network Infrastructure - Open Source Mobile Communications for doing CBS with limesdrmini but it doesn't run , is it due to that limesdrmini doesn't support the command telnet to osmo-bsc at port 4242, and enter something likeor i do something wrong. Chears, | | | | Version 10 - History - Cell Broadcast - Cellular Network Infrastructure ... Redmine | | |

5 years, 6 months

Re: OpenBSC Digest, Vol 64, Issue 2

by Radiarisainana Sitraka

The commercial MS see the network and i could send sms and call with it. the Limesdrmini doesn't support CBS? Le mercredi 12 février 2020 à 20:57:52 UTC, openbsc-request(a)lists.osmocom.org <openbsc-request(a)lists.osmocom.org> a écrit : Send OpenBSC mailing list submissions to openbsc(a)lists.osmocom.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.osmocom.org/mailman/listinfo/openbsc or, via email, send a message with subject or body 'help' to openbsc-request(a)lists.osmocom.org You can reach the person managing the list at openbsc-owner(a)lists.osmocom.org When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenBSC digest..." Today's Topics: 1. CBS + Osmocom + LimeSDR-Mini (Radiarisainana Sitraka) 2. CBS + ETWS + CMAS + Limesdrmini (Radiarisainana Sitraka) 3. Re: Commercial MSs do not see the network (Tomcs?nyi) 4. Re: Commercial MSs do not see the network (Joachim Steiger) ---------------------------------------------------------------------- Message: 1 Date: Wed, 12 Feb 2020 19:12:17 +0000 (UTC) From: Radiarisainana Sitraka <radiarisainanasitraka(a)yahoo.fr> To: "openbsc(a)lists.osmocom.org" <openbsc(a)lists.osmocom.org> Subject: CBS + Osmocom + LimeSDR-Mini Message-ID: <647375309.3679103.1581534737485(a)mail.yahoo.com> Content-Type: text/plain; charset="utf-8" Hello, I'm testing CBS LimeSDR-Mini with osmocom by following this Version 10 - History - Cell Broadcast - Cellular Network Infrastructure - Open Source Mobile Communications | | | | Version 10 - History - Cell Broadcast - Cellular Network Infrastructure ... Redmine | | | h4. make sure your related BTS is configured to use a channel combination with CBCH For using a combined CCCH with SDCCH/4 and CBCH you can use the following example snippet as part of osmo-bsc.cfg: network bts 0 trx 0 timeslot 0 phys_chan_config CCCH+SDCCH4+CBCH

5 years, 6 months

CBS + Osmocom + LimeSDR-Mini

by Radiarisainana Sitraka

Hello, I'm testing CBS LimeSDR-Mini with osmocom by following this Version 10 - History - Cell Broadcast - Cellular Network Infrastructure - Open Source Mobile Communications | | | | Version 10 - History - Cell Broadcast - Cellular Network Infrastructure ... Redmine | | | h4. make sure your related BTS is configured to use a channel combination with CBCH For using a combined CCCH with SDCCH/4 and CBCH you can use the following example snippet as part of osmo-bsc.cfg: network bts 0 trx 0 timeslot 0 phys_chan_config CCCH+SDCCH4+CBCH

5 years, 6 months

Feedback to GSUP Proxy Cache concept

by Oliver Smith

Hi Neels, > D-GSM proxy cache -- if you have the time, feedback on this design document would be appreciated: http://git.osmocom.org/osmo-hlr/commit/?h=neels/dgsm&id=8071c561405a031f204… > (when that commit is checked out, building osmo-hlr with manuals enabled should render the ladder diagrams in proxy_cache.adoc, which illustrate what I'm planning to implement) > (and disregard "(7) Skip the Insert Subscriber Data", as explained in the prose) I like that the key of the home HLR is not shared with the proxy HLRs. All in all, it sounds like a very smart solution! Some notes: * In the ladder diagrams, it shows that the AKAs are cached in both the MSC and the HLR. Why not just cache them in the HLR? * It might be a good idea to make AKA reuse optional with a VTY config option? * Potential use case: phone is home in village A, gets turned off, owner travels to village B with the phone, the link to village A is down. Phone gets turned on, then there will be no AKAs cached in village B's (proxy) HLR and the LU will fail. But there does not seem a way around this without sharing the keys (or without spaming other HLRs with AKAs for all subscribers in the HLR that they might use in the future, but that would just waste traffic). Regards, Oliver -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

5 years, 7 months

build2.osmocom.org hardware replacement

by Harald Welte

Dear Osmocom community, in recent weeks (at least since mid-december) we've had some stability issues with build2.osmocom.org, the physical machine that runs the build2-deb8build-ansible and build2-deb9build-ansible LXCs used heavily by our jenkins. I've had to reset the machine, and now we finally have asked the hosting company to perform a hardware replacement. This has happened about 3 hours ago, and I hope the stability problems are gone now. Let me know if you still see anything odd related to build2. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC