- OpenBSC - lists.osmocom.org

[RFC] proposal for new library: libosmo-net
by Pablo Neira Ayuso 30 Sep '11

30 Sep '11

Hi, After some private discussion with Harald, I'd like to propose one new library to abstract the network interface that is used to communicate two elements that are part of one GSM network (no matter if it's on the A-bis interface, A interface, ...). This new library, whose proposed name can be "libosmo-net", would initially support: - E1 interfaces. - Ethernet + IPA TCP/IP. - rs232 (as required by bs11 its config interface). This support is included in libosmo-abis, so my idea is to extract this code from it and leave in libosmo-abis only the specific A-bis bits. The libosmo-net library would be extensible, so we can add new interfaces to it (new E1 cards supported, new protocols over BSD sockets, and so on). The interface provided to the client of the library will be homogeneous for all supported interfaces (at least, as much as we can). The new library will provide: * a constructor/destructor to create/release some network interface of * a given supported type. * a call-back for receiving incoming messages that will take the actual msgb. * one function for sending signalling messages. As well as many helper functions in this regard. Therefore, libosmo-abis will require this new libosmo-net library after all is done. For the A interface, I'd propose some hypothetical libosmo-a library that will contain the specific A interface protocols. Let me know what you think.

2 3

comments on jolly/lapd branch
by Harald Welte 26 Sep '11

26 Sep '11

Hi Andreas, I've done a quick read through your jolly/lapd branches, and I have the following comments: 1) great work, thanks :) 2) lapd_profile I would like to use a 'struct lapd_profile' instead of a simple enum. Why? Because this puts all the values/parameters (like k, n201, short_address, use_sabme, t200, etc.) into the control of the caller, instead of the library. so basically we would have struct lapd_profile { uint8_t k; unsigned int n201; ... }; and then some library-pre-defined ones: const struct lapd_profile lapd_profile_isdn = { ... }; const struct lapd_profile lapd_profile_abis = { ... }; but this way an application could define their own profile with slightly different timers, without having to modify the library codebase. The actual lapd_datalink then just would have a const struct lapd_profile *profile; member that is assigned during lapd_dl_init(). 3) the msgb_free() changes in input/dahdi.c, src/e1_input.c, etc. should be a separate patch, as they are actual bugfixes of the old code, as far as I understand. That bugfix patch should be first, then the actual LAPD restructuring on top of it. 4) regarding the two-dimensional switch() statements, I suggest introducing the following macros to include/osmocom/core/osmo_prim.h: #define OSMO_PRIM(prim, op) (prim << 8 | op & 0xFF) #define OSMO_PRIM_HDR(oph) OSMO_PRIM(oph->primitive, oph->operation) then you can do something like this in the lapd code: switch (OSMO_PRIM_HDR(oph)) { case OSMO_PRIM(PRIM_DL_EST, PRIM_OP_REQUEST): ... } 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)

1 0

New open hardware for OpenBTS
by Alexander Chemeris 21 Sep '11

21 Sep '11

Hi all, (and sorry to those who receive this twice) At Sept 15th I will speak at the Open Hardware Summit at the breakout session "Open Hardware in Voice Telecommunications" and there I will present Fairwaves project to create an open hardware transceiver for OpenBTS. Someone may recall I proposed similar project about 1.5 years ago, but then abandoned due to lack of interest from the community. Now it was revived on a new level, thanks to financial and motivational support from Jean-Samuel Najnudel of BJT Partners SARL. As an experiment this project will be completely open-sourced in an open-source hardware way. Project is in active development, so just to give you an idea of what we're aiming: * Targeted for rural installations. * CAPEX and OPEX optimized. * 2 TRX per sector. Each TRX connected to its own antenna with its own saturated (=cheap) power amplifier on Tx side. On Rx side both antennas are used to provide diversity receive. * Reference clock synchronized to GPS for accurate timing. * Based on USRP N200, but with Xilinx Spartan 6 and LimeMicro LMS6002D. Which means it's actually design is much more capable then just GSM. More details, web-site, schematics, etc will be available after OHS. First samples of the hardware we hope to have at the end of this year. If you're going to OHS - come to our breakout session to discuss the project and share your ideas! -- Regards, Alexander Chemeris.

4 5

[PATCH/RFC 0/2] libosmo-abis ctrl related fixes
by Daniel Willmann 19 Sep '11

19 Sep '11

Hello, attached are two patches I came across while looking at the pablo/ctrl-updates branch in OpenBSC. The first one is just a bugfix for a resource leak and the second one adds a possibility to register a callback that will notify you if the connection is lost. This is needed for the control interface as we'll need to clean up some ctrlif related things if a connection is lost. Be aware that I haven't tested this with the ctrl-updates branch since this doesn't compile yet. I did test that master still compiles and osmo-bsc/nat don't segfault on start (though openbsc doesn't seem to use ipa_server_conn at the moment). The e1inp_ipa_{bsc,bts}_test worked as well. Regards, Daniel Willmann (2): ipa: Fix resource leak if we encounter an error in ipa_server_conn_read ipa: Add a callback to detect if the server_conn was closed include/osmocom/abis/ipa.h | 3 ++- src/input/ipa.c | 6 +++++- src/ipa_proxy.c | 2 +- 3 files changed, 8 insertions(+), 3 deletions(-) -- 1.7.6.1

4 7

bug in A-bis OML wireshark dissector
by Pablo Neira Ayuso 19 Sep '11

19 Sep '11

Hi! While submitting the A-bis OML wireshark dissector I noticed one bug in it that results in bogus message labeling. The following patch should be applied to osmocom/wireshark.git tree. P.S: I have submitted a patch to wireshark bugzilla that includes this bugfix.

1 0

anyone give me a hint to implement L1 for openbsc
by John Wu 16 Sep '11

16 Sep '11

Hi list, I want to implement a L1 hardware and software for openbsc. But I am not familiar with openbsc framework. I saw there is a project named osmo-nitb which is a standalone application that implement L2 L3 and some other gsm network function. If I can using my L1 software connect to osmo-nitb through abis-overip? Also I notice another project osmo-bts project which implement BTS-side Layer3 and Layer2 protocol. So can I just implement BTS side L1 then combine with osmo-bts which connect to osmo-nitb? Regards!

4 9

[PATCH 0/5] pablo/ctrl-updates related patches
by Daniel Willmann 16 Sep '11

16 Sep '11

Hello Pablo, attached are patches against the current pablo/ctrl-updates branch that fix the compile issues. It needs the closed callback in libosmo-abis to work. As long as the bsc_msc_connection is still using write_queues I have added the old ctrl_cmd_send function again (under a different name) So we can still send commands over that connection. I've tested the communication/timeout/closed_cb handling and nothing problematic showed up. Having two send commands is unfortunate, but I guess it's okay for the time being. I'm guessing that the other connections will be switching to libosmo-abis as well in the foreseeable future and then this issue will resolve itself. Feel free to squash the patches as you see fit in order to get them merged. Regards, Daniel Willmann (5): libctrl: Catch up with API change for ipa_server_conn_create nat: Use libosmo-abis infrastructure in the pending entries libctrl: Add a new function to send commands through an osmo_wqueue osmo-bsc: Use ctrl_cmd_send_wqueue to send cmds over the nat-bsc link nat: Use ctrl_cmd_send_wqueue to send cmds over the nat-bsc link openbsc/include/openbsc/bsc_nat.h | 2 +- openbsc/include/openbsc/control_cmd.h | 1 + openbsc/src/libctrl/control_if.c | 24 +++++++++++++++++++++++- openbsc/src/osmo-bsc/osmo_bsc_msc.c | 4 ++-- openbsc/src/osmo-bsc_nat/bsc_nat.c | 19 ++++++++++--------- 5 files changed, 37 insertions(+), 13 deletions(-) -- 1.7.6.1

2 6

M3UA SLS
by Ammar Naamat Hameed 15 Sep '11

15 Sep '11

Dear All, I have a question regarding the SLS in M3UA, is the sls number mapped to the sctp stream id? for example, lets consider that i have sctp association with two stream id, 1 and 2, can i send m3ua message with sls 0 mapped to sctp stread id 1, and another m3ua message with sls1 mapped to sctp stream id 2. is this correct? if not can you please help digest this issue :). Appreciate your help, Ammar

1 0

Fwd: regarding openBSC
by anish achenkunju 14 Sep '11

14 Sep '11

Hi Just ran across your blog and was interested in emulating some real traffic to Cisco GGSN code running on dynamips. Could you please provide me some references where I can start with so that i can get openBSC or openSGSN up and running? Also wondering if you have or aware of a code that emulated MS instead of having real BTS up , Thank you v.much in advance. Anish

1 0

some issues configuring openbsc
by Stephen Siadak 13 Sep '11

13 Sep '11

While I think I am pretty close to getting my ip.access nanoBTS to communicate with my laptop running osmo-nitb I seem to be running into a problem. I am running openbsc-0.9.13 and using libosmocore-0.1.30 When I start osmo-nitb I see this error: ./osmo-nitb -T -c ./openbsc.cfg DB: Database initialized. DB: Database prepared. Sat Sep 10 17:39:42 2011 <0007> sms_queue.c:223 Attempting to send 20 SMS Sat Sep 10 17:39:45 2011 <000d> input/ipaccess.c:650 accept()ed new OML link from 2.2.2.1 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 8a c4 0b Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 00 00 c0 a8 ea 01 00 00 00 00 00 00 00 00 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 d4 07 c0 a8 ea 01 38 a4 45 00 04 59 40 00 Sat Sep 10 17:39:45 2011 <0005> bsc_init.c:50 Failed to set BTS attributes. That is fatal. Was the bts type and frequency properly specified? I am using one of the stock nitb configuration files with no modifications. openbsc.git/openbsc/doc/examples/osmo-nitb/nanobts/openbsc.cfg My setup is a little odd. I did not do the original configuration for the nanoBTS. I was hoping to just get stuff working with the current configuration before I changed anything. The nanoBTS comes up with an IP of 2.2.2.1 and expects a gateway of 2.2.2.2. So I simply configured the ip eth0 on my laptop to 2.2.2.2. Then annoyingly the nanoBTS starts looking for 3.3.3.3. Now I start getting a little hacky to try and move stuff along: ip addr add 3.3.3.3/24 dev eth0 ip route add 3.3.3.3/32 via 2.2.2.2 I am able to use ipaccess-find: ./ipaccess-find eth0 # finally shows # MAC Address='00:02:95:00:51:83' IP Address='2.2.2.1' Unit ID='1801/0/0' # Location 1='' Location 2='BTS_NBT131G' Equipment Version='165b029_58' # Software Version='168a302_v142b13d0' Unit Name='nbts-00-02-95-00-51-83' # Serial Number='00106317' I am also able to use ipaccess-config: ./ipaccess-config -u 1801/0/0 -o 2.2.2.2 -r 2.2.2.1 # Trying to connect to ip.access BTS ... # <0005> abis_nm.c:537 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) # <0005> abis_nm.c:537 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled # AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # OML link established using TRX 0 # setting Unit ID to '1801/0/0' # setting primary OML link IP to '2.2.2.2' # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) # IPACCESS(0xf0): SET NVATTR ACK # Set the NV Attributes. # The BTS has acked the restart. Exiting. At this point I try to start osmo-nitb and receive the error I mentioned earlier: ./osmo-nitb -T -c ./openbsc.cfg DB: Database initialized. DB: Database prepared. Sat Sep 10 17:39:42 2011 <0007> sms_queue.c:223 Attempting to send 20 SMS Sat Sep 10 17:39:45 2011 <000d> input/ipaccess.c:650 accept()ed new OML link from 2.2.2.1 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 8a c4 0b Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 00 00 c0 a8 ea 01 00 00 00 00 00 00 00 00 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 d4 07 c0 a8 ea 01 38 a4 45 00 04 59 40 00 Sat Sep 10 17:39:45 2011 <0005> bsc_init.c:50 Failed to set BTS attributes. That is fatal. Was the bts type and frequency properly specified? I think the bts type is set correct in the configuration file: type nanobts I am not sure what setting actually sets the frequency. I am happy to provide more information and any help is appreciated. Thanks in advance, -Steve

3 2