OpenBSC January 2017

openbsc@lists.osmocom.org

24 participants
56 discussions

[PATCH 00/17] gtp: fixes and support multiple VRF's per GTP socket

by Andreas Schultz

The current linking of GTP network devices and GTP enabled sockets means that we can not have multiple VRF's per GTP socket. This series seperates the sockets from network device, makes sockets attached to GTP network device optional and adds a API function to enable GTP encapsulation on socket without having to create a new GTP device. It is still possible to use the old API. The network device attached socket is then used when no socket is specified on PDP context creation. During that work some smaller problems where found and fixes for them are included. Regards Andreas -- Andreas Schultz (17): gtp: add genl family modules alias gtp: clear DF bit on GTP packet tx gtp: make GTP sockets in gtp_newlink optional gtp: return error ptr in find pdp helpers gtp: unify genl_find_pdp and prepare for per socket lookup gtp: fix cross netns recv on gtp socket gtp: remove unnecessary rcu_read_lock gtp: consolidate pdp context destruction into helper gtp: use addr_hash when traversing pdp contexts gtp: add socket to pdp context gtp: consolidate gtp socket rx path gtp: let userspace handle packets for invalid tunnels gtp: replace netdev_dbg and KERN_DEBUG printk with pr_debug gtp: move TEID hash to per socket structure gtp: rename gtp hashtable helpers gtp: add genl cmd to enable GTP encapsulation on UDP socket gtp: add support to select a GTP socket during PDP context creation drivers/net/gtp.c | 681 +++++++++++++++++++++++++++-------------------- include/uapi/linux/gtp.h | 4 + 2 files changed, 392 insertions(+), 293 deletions(-) -- 2.10.2

8 years, 8 months

Re: Omsobts -osmotrx communication problem

by Snehasish Kar

Problem is usrp x310 doesnot support the gsmband, it works above 1.2GHz. Also if I still change the MCC and MNC I am not not able to find the network on the phone, and any clue on this error "check_rx_md_err: An internal receive buffer has filled", it comes in osmo-trx. ________________________________ From: Dhananjay kumar <dhananjay.cse(a)gmail.com> Sent: Monday, January 23, 2017 11:37:38 AM To: Snehasish Kar Cc: nhofmeyr(a)sysmocom.de Subject: Re: Omsobts -osmotrx communication problem hi, network country code 404 mobile network code 31 Change it to network country code 001 mobile network code 01 short name TESTPLMN long name TESTPLMN Try it in Band 850 . 900 and 1800 and widely used in India by commercial operates. Remove all neighbor cell list. You are using 404 31 , it might match some real network, and you will not able to see your test network. BR Dhananjay On Mon, Jan 23, 2017 at 11:20 AM, Snehasish Kar <snehasish.cse(a)live.com<mailto:snehasish.cse@live.com>> wrote: Hi I have attached my config as requested, also in osmo-trx I am getting the following error "check_rx_md_err: An internal receive buffer has filled" and I am not able to view the network in my phone. I am using usrp x310 and os UBUNTU. BR Snehasish ________________________________ From: Neels Hofmeyr <nhofmeyr(a)sysmocom.de<mailto:nhofmeyr@sysmocom.de>> Sent: Saturday, January 21, 2017 4:35:06 AM To: Snehasish Kar Cc: openbsc(a)lists.osmocom.org<mailto:openbsc@lists.osmocom.org> Subject: Re: Omsobts -osmotrx communication problem On Fri, Jan 20, 2017 at 11:58:53AM +0000, Snehasish Kar wrote: > Hi > > I have installed osmobts and osmotrx with openbsc, to enable openbsc with usrp. But whenever I tried running the three applications, I gave the following error in osmobts. Please help me with it. > > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid > > <000b> trx_if.c:490 Tx burst length 0 invalid If I remember correctly, osmo-bts-trx will at startup show a bunch of these and then continue normally. To clarify, you need to run 'osmo-trx', 'osmo-bts-trx' and 'osmo-nitb'. We can't help further with this little information on your config. ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de<mailto:nhofmeyr@sysmocom.de>> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -- Thanks & Regards Dhananjay 9686184214 Luck is what happens when preparation meets opportunity.

8 years, 8 months

Omsobts -osmotrx communication problem

by Snehasish Kar

Hi I have installed osmobts and osmotrx with openbsc, to enable openbsc with usrp. But whenever I tried running the three applications, I gave the following error in osmobts. Please help me with it. <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid > <000b> trx_if.c:490 Tx burst length 0 invalid BR Snehasish

8 years, 8 months

redmine issue

by Max

Hi. I've hit strange issue with redmine: https://osmocom.org/issues/1836 gives 403 error but https://osmocom.org/issues/71 works for example. Is this intended due to some access control restrictions or it's a glitch in our setup? -- Max Suraev <msuraev(a)sysmocom.de> http://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

8 years, 8 months

osmo-trx jenkins

by Max

HI. A little heads up: uhd version in jenkins building osmo-trx should be updated to 3.9.0 - this would allow gerrit #1117 to be properly verified by jenkins. -- Max Suraev <msuraev(a)sysmocom.de> http://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

8 years, 8 months

Add VTY command to immediately expire user (set expire_lu to now)

by Keith

Hi all, ( so.. by way of finding out what is the best way to do this kind of thing, I went ahead and submitted my patch to gerrit. ) I've added a command to the vty to set the expire_lu value for the subscriber to now. My personal use case for this is that I wanted a way to set lac = GSM_LAC_RESERVED_DETACHED when I know that the MS is not there, (because I know it has gone to another nitb with a different lac) and therefore I no longer want to page it and I also don't want it showing up as connected when I poll the hlr for lac>0 via sqlite3. So if I set the expire_lu to now, openbsc will very shortly afterwards, issue <0002> gsm_subscriber.c:366 Expiring inactive subscriber...... I'm not sure if this would be considered something anybody else might want, or confusing for users, and I haven't fully tested (yet) what might happen if the mobile has not in fact done an IMSI attach to another lac yet I expire it. Also, my C programming history is nill. I have no idea if setting a time_t to time(0) is cool, or will result in sky falling down. I'm not quite sure if it's necessary to call subscr_put() I also realise I left a pointless rc declaration in there. oh well.. guess I learn about submitting patch set 2.. So the unwritten question is, with ideas like this, should I first ask here on the list for opinion on the theoretical merits or not of such an idea, or should I just submit to gerrit and should the discussion, if any, happen there? Many Thanks! k/

8 years, 8 months

osmo_sock_init API changes

by Holger Freyther

Hey, osmo_sock_init is nice but I have hit a missing feature. I want to be able to make an outgoing connection but need to specify the src ip (and maybe src port too). a.) I could extend osmo_sock_init to have a src_ip and src_port in the parameter and issue a bind between the socket(2) and connect(2). b.) I could add a cb function that is passing the fd to the cb and do the bind (or others do setsockopt). Any other ideas? Preferences? Comments? holger

8 years, 8 months

Intregation with usrp

by Snehasish Kar

Hi I want to intregate my openbsc code with a usrp. Please help me with it. BR Snehasish

8 years, 8 months

Build failure of network:osmocom:nightly/osmo-bts in xUbuntu_16.10/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-bts failed to build in xUbuntu_16.10/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-bts Last lines of build log: [ 264s] ## ----------- ## [ 264s] [ 264s] /* confdefs.h */ [ 264s] #define PACKAGE_NAME "osmo-bts" [ 264s] #define PACKAGE_TARNAME "osmo-bts" [ 264s] #define PACKAGE_VERSION "0.5.0.20170117" [ 264s] #define PACKAGE_STRING "osmo-bts 0.5.0.20170117" [ 264s] #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" [ 264s] #define PACKAGE_URL "" [ 264s] #define PACKAGE "osmo-bts" [ 264s] #define VERSION "0.5.0.20170117" [ 264s] #define STDC_HEADERS 1 [ 264s] [ 264s] configure: exit 1 [ 264s] dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/i386-linux-gnu --libexecdir=${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --enable-trx returned exit code 1 [ 264s] debian/rules:22: recipe for target 'override_dh_auto_configure' failed [ 264s] make[1]: *** [override_dh_auto_configure] Error 2 [ 264s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 264s] debian/rules:12: recipe for target 'build' failed [ 264s] make: *** [build] Error 2 [ 264s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 264s] [ 264s] build11a failed "build osmo-bts_0.5.0.20170117.dsc" at Tue Jan 17 20:20:46 UTC 2017. [ 264s] [ 264s] ### VM INTERACTION START ### [ 268s] ### VM INTERACTION END ### [ 269s] [ 269s] build11a failed "build osmo-bts_0.5.0.20170117.dsc" at Tue Jan 17 20:20:51 UTC 2017. [ 269s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

8 years, 8 months

Build failure of network:osmocom:nightly/openbsc in xUbuntu_16.04/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/openbsc failed to build in xUbuntu_16.04/i586 Check out the package for editing: osc checkout network:osmocom:nightly openbsc Last lines of build log: [ 219s] [ 219s] Makefile:718: recipe for target 'check-local' failed [ 219s] make[5]: *** [check-local] Error 1 [ 219s] make[5]: Leaving directory '/usr/src/packages/BUILD/openbsc/tests' [ 219s] Makefile:569: recipe for target 'check-am' failed [ 219s] make[4]: *** [check-am] Error 2 [ 219s] make[4]: Leaving directory '/usr/src/packages/BUILD/openbsc/tests' [ 219s] Makefile:421: recipe for target 'check-recursive' failed [ 219s] make[3]: *** [check-recursive] Error 1 [ 219s] make[3]: Leaving directory '/usr/src/packages/BUILD/openbsc/tests' [ 219s] Makefile:484: recipe for target 'check-recursive' failed [ 219s] make[2]: *** [check-recursive] Error 1 [ 219s] make[2]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 219s] Makefile:775: recipe for target 'check' failed [ 219s] make[1]: *** [check] Error 2 [ 219s] make[1]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 219s] dh_auto_test: make -j1 check returned exit code 2 [ 219s] debian/rules:13: recipe for target 'build' failed [ 219s] make: *** [build] Error 2 [ 219s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 219s] [ 219s] cloud120 failed "build openbsc_0.15.1.20170117.dsc" at Tue Jan 17 20:12:17 UTC 2017. [ 219s] [ 219s] ### VM INTERACTION START ### [ 222s] [ 201.329022] reboot: Power down [ 223s] ### VM INTERACTION END ### [ 223s] [ 223s] cloud120 failed "build openbsc_0.15.1.20170117.dsc" at Tue Jan 17 20:12:21 UTC 2017. [ 223s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

8 years, 8 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2017