From grgrehreher at gmail.com Sun Sep 1 10:50:07 2019 From: grgrehreher at gmail.com (Anis Anis) Date: Sun, 1 Sep 2019 11:50:07 +0100 Subject: osmocom cni install Message-ID: HI first of all thanks for all the amazing work here! just wanna know after Adding the repository to the Ubuntu_18.04 system,what i need to do in order to install the osmocom cni? thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From grgrehreher at gmail.com Sun Sep 1 12:00:34 2019 From: grgrehreher at gmail.com (Anis Anis) Date: Sun, 1 Sep 2019 13:00:34 +0100 Subject: osmocom cni install (required elements) Message-ID: HI first of all thanks for all the amazing work here! just wanna know after Adding the repository to the Ubuntu_18.04 system,what i need to do in order to install the osmocom cni? when trying apt-get install osmo,it will suggest all those : i just wanna know which elements are required to install! thanks osmo osmo-ggsn-dbg osmo-remsim-bankd osmo-bsc osmo-ggsn-doc osmo-remsim-client osmo-bsc-bs11-utils osmo-gsm-manuals-dev osmo-remsim-doc osmo-bsc-dbg osmo-gtphub osmo-remsim-server osmo-bsc-doc osmo-gtphub-dbg osmo-sdr osmo-bsc-ipaccess-utils osmo-hlr osmose-emulator osmo-bsc-meas-utils osmo-hlr-dbg osmo-sgsn osmo-bts osmo-hlr-doc osmo-sgsn-dbg osmo-bts-doc osmo-hnbgw osmo-sgsn-doc osmo-bts-trx osmo-hnbgw-dbg osmo-sip-connector osmo-bts-trx-dbg osmo-libasn1c0 osmo-sip-connector-dbg osmo-bts-virtual osmo-libasn1c-dev osmo-sip-connector-doc osmo-bts-virtual-dbg osmo-mgw osmosis osmocom-bs11-utils osmo-mgw-doc osmo-stp osmocom-bsc osmo-msc osmo-stp-dbg osmocom-bsc-nat osmo-msc-dbg osmo-stp-doc osmocom-gbproxy osmo-msc-doc osmo-sysmon osmocom-ipaccess-utils osmo-pcap-client osmo-sysmon-dbg osmocom-latest osmo-pcap-client-dbg osmo-trx osmocom-nitb osmo-pcap-server osmo-trx-dbg osmocom-sgsn osmo-pcap-server-dbg osmo-trx-doc osmo-gbproxy osmo-pcu osmo-trx-lms osmo-gbproxy-dbg osmo-pcu-dbg osmo-trx-uhd osmo-ggsn osmo-pcu-doc osmo-trx-usrp1 thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt9j at cs.washington.edu Mon Sep 2 18:11:23 2019 From: matt9j at cs.washington.edu (Matt Johnson) Date: Mon, 2 Sep 2019 13:11:23 -0500 Subject: osmocom cni install (required elements) In-Reply-To: References: Message-ID: <6cf88905-e667-407f-c549-5c83b224d4f8@cs.washington.edu> Hi Anis, The exact components you will need depends on the specific type of network you are hoping to build (2G Voice only? 2G+GPRS Data? 3G? 2G&3G?). All the information you need to setup a core network on a single machine is available here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box . In general the Osmocom wiki and individual component documentation is a rich source of information for this type of stuff. Cheers, -Matt J. On 9/1/19 7:00 AM, Anis Anis wrote: > HI > > first of all thanks for all the amazing work here! > > just wanna know after Adding the repository to the Ubuntu_18.04 > system,what i need to do in order to install the osmocom cni? > when trying apt-get install osmo,it will suggest all those : > i just wanna know which elements are required to install! > thanks > > osmo ? ? ? ? ? ? ? ? ? ? osmo-ggsn-dbg ?osmo-remsim-bankd > osmo-bsc ? ? ? ? ? ? ? ? osmo-ggsn-doc ?osmo-remsim-client > osmo-bsc-bs11-utils ? ? ?osmo-gsm-manuals-dev osmo-remsim-doc > osmo-bsc-dbg ? ? ? ? ? ? osmo-gtphub ?osmo-remsim-server > osmo-bsc-doc ? ? ? ? ? ? osmo-gtphub-dbg ? ? ? ? ?osmo-sdr > osmo-bsc-ipaccess-utils ?osmo-hlr osmose-emulator > osmo-bsc-meas-utils ? ? ?osmo-hlr-dbg ? ? ? ? ? ? osmo-sgsn > osmo-bts ? ? ? ? ? ? ? ? osmo-hlr-doc osmo-sgsn-dbg > osmo-bts-doc ? ? ? ? ? ? osmo-hnbgw osmo-sgsn-doc > osmo-bts-trx ? ? ? ? ? ? osmo-hnbgw-dbg osmo-sip-connector > osmo-bts-trx-dbg ? ? ? ? osmo-libasn1c0 osmo-sip-connector-dbg > osmo-bts-virtual ? ? ? ? osmo-libasn1c-dev ?osmo-sip-connector-doc > osmo-bts-virtual-dbg ? ? osmo-mgw ? ? ? ? ? ? ? ? osmosis > osmocom-bs11-utils ? ? ? osmo-mgw-doc ? ? ? ? ? ? osmo-stp > osmocom-bsc ? ? ? ? ? ? ?osmo-msc ? ? ? ? ? ? ? ? osmo-stp-dbg > osmocom-bsc-nat ? ? ? ? ?osmo-msc-dbg ? ? ? ? ? ? osmo-stp-doc > osmocom-gbproxy ? ? ? ? ?osmo-msc-doc ? ? ? ? ? ? osmo-sysmon > osmocom-ipaccess-utils ? osmo-pcap-client osmo-sysmon-dbg > osmocom-latest ? ? ? ? ? osmo-pcap-client-dbg ? ? osmo-trx > osmocom-nitb ? ? ? ? ? ? osmo-pcap-server ? ? ? ? osmo-trx-dbg > osmocom-sgsn ? ? ? ? ? ? osmo-pcap-server-dbg ? ? osmo-trx-doc > osmo-gbproxy ? ? ? ? ? ? osmo-pcu ? ? ? ? ? ? ? ? osmo-trx-lms > osmo-gbproxy-dbg ? ? ? ? osmo-pcu-dbg ? ? ? ? ? ? osmo-trx-uhd > osmo-ggsn ? ? ? ? ? ? ? ?osmo-pcu-doc osmo-trx-usrp1 > > thanks. From grgrehreher at gmail.com Mon Sep 2 18:23:45 2019 From: grgrehreher at gmail.com (Anis Anis) Date: Mon, 2 Sep 2019 19:23:45 +0100 Subject: osmocom cni install (required elements) In-Reply-To: <6cf88905-e667-407f-c549-5c83b224d4f8@cs.washington.edu> References: <6cf88905-e667-407f-c549-5c83b224d4f8@cs.washington.edu> Message-ID: Thank you for the Information! Much appreciated! Really missed this link,my bad! https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box And Yes,it's well documented! :) Have a great day. Regards. On Mon, Sep 2, 2019, 19:11 Matt Johnson wrote: > Hi Anis, > > The exact components you will need depends on the specific type of > network you are hoping to build (2G Voice only? 2G+GPRS Data? 3G? > 2G&3G?). All the information you need to setup a core network on a > single machine is available here: > > https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box > . In general the Osmocom wiki and individual component documentation is > a rich source of information for this type of stuff. > > Cheers, > > -Matt J. > > On 9/1/19 7:00 AM, Anis Anis wrote: > > HI > > > > first of all thanks for all the amazing work here! > > > > just wanna know after Adding the repository to the Ubuntu_18.04 > > system,what i need to do in order to install the osmocom cni? > > when trying apt-get install osmo,it will suggest all those : > > i just wanna know which elements are required to install! > > thanks > > > > osmo osmo-ggsn-dbg osmo-remsim-bankd > > osmo-bsc osmo-ggsn-doc osmo-remsim-client > > osmo-bsc-bs11-utils osmo-gsm-manuals-dev osmo-remsim-doc > > osmo-bsc-dbg osmo-gtphub osmo-remsim-server > > osmo-bsc-doc osmo-gtphub-dbg osmo-sdr > > osmo-bsc-ipaccess-utils osmo-hlr osmose-emulator > > osmo-bsc-meas-utils osmo-hlr-dbg osmo-sgsn > > osmo-bts osmo-hlr-doc osmo-sgsn-dbg > > osmo-bts-doc osmo-hnbgw osmo-sgsn-doc > > osmo-bts-trx osmo-hnbgw-dbg osmo-sip-connector > > osmo-bts-trx-dbg osmo-libasn1c0 osmo-sip-connector-dbg > > osmo-bts-virtual osmo-libasn1c-dev osmo-sip-connector-doc > > osmo-bts-virtual-dbg osmo-mgw osmosis > > osmocom-bs11-utils osmo-mgw-doc osmo-stp > > osmocom-bsc osmo-msc osmo-stp-dbg > > osmocom-bsc-nat osmo-msc-dbg osmo-stp-doc > > osmocom-gbproxy osmo-msc-doc osmo-sysmon > > osmocom-ipaccess-utils osmo-pcap-client osmo-sysmon-dbg > > osmocom-latest osmo-pcap-client-dbg osmo-trx > > osmocom-nitb osmo-pcap-server osmo-trx-dbg > > osmocom-sgsn osmo-pcap-server-dbg osmo-trx-doc > > osmo-gbproxy osmo-pcu osmo-trx-lms > > osmo-gbproxy-dbg osmo-pcu-dbg osmo-trx-uhd > > osmo-ggsn osmo-pcu-doc osmo-trx-usrp1 > > > > thanks. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jovanovskiborjan at gmail.com Mon Sep 2 21:55:35 2019 From: jovanovskiborjan at gmail.com (Borjan Jovanovski) Date: Mon, 2 Sep 2019 23:55:35 +0200 Subject: ABIS Over SCTP Port 14597 Message-ID: Hi everyone! I have a BTS that is trying to connect to openbsc via SCTP, but as i see it is not supported. I have attached a capture file between the core network equipment and BTS 10.0.0.7 is the IP Address of the ABIS link and port is 14597 the rest is for UMTS and LTE so please ignore it. I would be really gratefull if someone could look into this Kind thanks to everyone! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hnb.zip Type: application/x-zip-compressed Size: 127754 bytes Desc: not available URL: From lynxis at fe80.eu Mon Sep 2 22:02:46 2019 From: lynxis at fe80.eu (Alexander Couzens) Date: Tue, 3 Sep 2019 00:02:46 +0200 Subject: all cccamp2019 branches now on git.osmocom.com Message-ID: <20190903000246.3d581a0e@lazus.yip> Hi, i've pushed all modificatons from the chaos communication camp 2019 to the osmocom repositories as cccamp2019. Except for libosmo-abis which I directly pushed to gerrit. I would like to go next over the 35c3 branches, take a short overlook and remove them if them aren't useful. best, lynxis -- Alexander Couzens mail: lynxis at fe80.eu jabber: lynxis at fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From nhofmeyr at sysmocom.de Mon Sep 2 22:53:02 2019 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 3 Sep 2019 00:53:02 +0200 Subject: ABIS Over SCTP Port 14597 In-Reply-To: References: Message-ID: <20190902225302.GA7479@my.box> On Mon, Sep 02, 2019 at 11:55:35PM +0200, Borjan Jovanovski wrote: > Hi everyone! > > I have a BTS that is trying to connect to openbsc via SCTP, but as i see it > is not supported. Interesting, SCTP on the Abis link is new for me. openbsc (or osmo-nitb) has long been deprecated. The new programs to use are described here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box All of our currently supported 2G BTS models connect to OsmoBSC via TCP/IP (Abis). SCTP is supported for the A interface (between BSC and MSC), and for Iuh serving 3G cells, but not for 2G BTS to connect to the BSC. And just to make sure we're not confusing things: since your filename is 'hnb.zip' and your pcap contains Iub Signalling, it looks to me like you are trying to connect a 3G cell? We have SCTP support for attaching hNodeB to the osmo-hnbgw -- this is not Abis, but the Iuh interface. There is no "OsmoRNC" program yet (and probably won't be any time soon), so the only way to run 3G with Osmocom CNI is to use an hNodeB femto cell that already includes the RNC and talks Iuh to osmo-hnbgw (or operate your own RNC that talks IuCS to osmo-msc and IuPS to osmo-sgsn, which has never been tested before). I hope this clarifies things? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From jovanovskiborjan at gmail.com Mon Sep 2 23:47:16 2019 From: jovanovskiborjan at gmail.com (Borjan Jovanovski) Date: Tue, 3 Sep 2019 01:47:16 +0200 Subject: ABIS Over SCTP Port 14597 In-Reply-To: <20190902225302.GA7479@my.box> References: <20190902225302.GA7479@my.box> Message-ID: Dear Mr. Hofmeyr, Thank you for your kind help and support, yes it is also new to me, it is mostly used in comercial systems due to the network size and complexity, but yes i can confirm that i am talking about ABIS over SCTP. I even have some documentation about it. The device in question is a multimode (GSM,UMTS,LTE) Macrocell so the packet capture contains the following information: 10.0.0.5 LTE SCTP port 36412 10.0.0.7 ABIS over SCTP for GSM port 14597 10.0.0.8 RNC IuB SCTP Port 29169 As of now also, another question, is there an open source RNC available? Thanks once again for the help and support! -------------- next part -------------- An HTML attachment was scrubbed... URL: From nhofmeyr at sysmocom.de Tue Sep 3 14:16:04 2019 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 3 Sep 2019 16:16:04 +0200 Subject: ABIS Over SCTP Port 14597 In-Reply-To: References: <20190902225302.GA7479@my.box> Message-ID: <20190903141604.GA25189@my.box> On Tue, Sep 03, 2019 at 01:47:16AM +0200, Borjan Jovanovski wrote: > 10.0.0.7 ABIS over SCTP for GSM port 14597 Hmm, wireshark shows only "DATA" there, doesn't offer decoding as any GSM protocol. Briefly skimming the raw bytes, they don't really look like Abis OML nor RSL to me. I guess you would have to implement support from scratch using the documentation you mentioned. > As of now also, another question, is there an open source RNC available? At least not that we know of. If you find one, shout! ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From laforge at gnumonks.org Thu Sep 5 11:30:03 2019 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 5 Sep 2019 13:30:03 +0200 Subject: 2019-09-10: Talk about commercial cellular base station technology Message-ID: <20190905113003.GC19175@nataraja> Dear Osmocom community and friends, Next week on September 10, I will be presenting a talk about cellular base station technology as part of the "Datengarten" series of talks at Chaos Computer Club Berlin (CCCB). The talk will focus on actual base station hardware as it evolved during the last 20 years or so. It will not assume much in terms of protocol stacks or cellular architecture, but more focus on the hardware building blocks. More information can be found at https://berlin.ccc.de/datengarten/102/ The event is public, so feel free to invite anyone along whom you think might be interested. Regards, Harald --- Abstract In today?s hyper-connected society, everyone constantly uses their smartphone, which in turn uses the commercial cellular networks (from 2G/GSM to 4G/LTE) in order to achieve connectivity. However, contrary to WiFi technology, even most technology-minded people don?t have much of an idea how the infrastructure behind those cellular networks looks like. This talk does not cover the architecture and protocols of underlying cellular systems, but focuses on the physical side of things: * what are the typical components of cellular base stations? * what are their key functionalities? * how did cellular base station technology evolve during the past 20 years? * how do we expect cellular base stations to change in the [near] future? We will not cover DIY or hobbyist projects here, but the actual technology deployed in the field by real-world commercial operators. --- -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From igorlateliev at gmail.com Thu Sep 5 16:41:17 2019 From: igorlateliev at gmail.com (Igor Lateliev) Date: Thu, 5 Sep 2019 18:41:17 +0200 Subject: Looking for variables names that can be read via osmo-msc CONTROL interface Message-ID: Dear osmocom-cni contributors, I would like to retrieve (i.e. read or get) some data from a running osmo-msc from the CONTROL interface... but sorry, currently I cannot find either from the manuals or the source code the name of variables I can query. Is there a mean to list all the variables that can be ?GET? from the osmo-msc CONTROL interface? And? the list that can be ?SET? through the osmo-msc CONTROL interface? I am also interested in other osmo-cni nodes. Thanks a lot in advance. BR, Igor. From pespin at sysmocom.de Thu Sep 5 21:42:48 2019 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Thu, 5 Sep 2019 23:42:48 +0200 Subject: Looking for variables names that can be read via osmo-msc CONTROL interface In-Reply-To: References: Message-ID: Hi Igor, You can find osmo-msc specific CTRL commands in the User Manual section 6 "Control interface" : https://ftp.osmocom.org/docs/latest/osmomsc-usermanual.pdf You should be able to similarly find available CTRL messages for other osmo-cni nodes in their User Manuals, available in same directory: https://ftp.osmocom.org/docs/latest/ Feel free to open tickets if you are interested in any kind of CTRL cmd which is not there yet, and/or submit patches implementing them. For your information, if you want to interact with the CTRL interface you can find useful scripts in osmo-python-tests: https://git.osmocom.org/python/osmo-python-tests/tree/scripts/osmo_interact_ctrl.py -- - Pau Espin Pedrol 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 From laforge at gnumonks.org Fri Sep 13 19:06:36 2019 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 13 Sep 2019 21:06:36 +0200 Subject: DW-TV report on Rhizomatica, TIC and Osmocom/sysmocom Message-ID: <20190913190636.GF1669@nataraja> Hi all, DW-TV has just released a video report on the community owned and operated cellular networks within TIC, the Mexican partner of Rhizomatica. You can find the (Spanish only) video at https://www.dw.com/es/telefon%C3%ADa-ind%C3%ADgena-en-defensa-del-derecho-a-la-comunicaci%C3%B3n/av-50416268 I recommend to watch the full video to catch some glimpses into the life of people in one of the communities operating their own Osmocom based cellular network. If you don't have the time to follow the full video, some pointers below: * from 4:35 you can see how the taxi service (the only form of public transport!) can pick up people anywhere in the region after they make a mobile phone call * from 12:50 onwards, the BTS is introduced, and its role (and that of the BSC) are explained in a nice animation. * from 18:49 you can see the part covering the role Osmocom and sysmocom are playing in the development of the underlying technology. You can also catch a glimpse of the sysmocom office Especially for somebody who's never been there in person, it is very enlightening to see more about how people use it. And the technology geek in me of course enjoys the work related to power supply, including the home-made inverter for solar charging (from 16:12) Let me conclude with the statement that I'm extremely happy about (and proud of) the amazing work that Rhizomatica, TIC and friends are doing. It's great to see Osmocom code being put to use in such a meaningful way, and for what it was crated: To enable people (literally anyone) to operate their own cellular networks in whatever way, independent of large multi-national corporations. There are just very few places where people have actually managed to do this, given all the legal, political, economic constraints, including spectrum licensing. Thanks to Peter, Keith and his colleagues for dedicating many years to this cause. Thanks to DW-TV and Eva Usi (the reporter behind this piece). Further links (in case you weren't aware of those projects/entities): https://www.rhizomatica.org/ https://www.tic-ac.org/ Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From osmith at sysmocom.de Wed Sep 18 12:26:14 2019 From: osmith at sysmocom.de (Oliver Smith) Date: Wed, 18 Sep 2019 14:26:14 +0200 Subject: C/C++ dialect defaults Message-ID: <46d76f11-06fc-8b68-8183-85f2b0a6a090@sysmocom.de> Hello Osmocom community, how about we set the C and C++ dialect defaults in for each Osmocom program? Then we would not run into the kind of errors, where code compiled without errors in the gerrit verification jenkins job, but failed to compile elsewhere because a different GCC uses different default dialects. We ran into this already with differences in gerrit verification and master builds [1], and it can easily happen when building the binary packages for the various Debian versions and derivatives in OBS. In [2] is an example patch for OsmoPCU, hardcoding the following dialects (gnu89 is the same as the linux kernel uses [3]). CXXFLAGS="$CXXFLAGS -std=gnu++03" CFLAGS="$CFLAGS -std=gnu89" (Note that we can't use the non-gnu dialects, libosmocore won't build with those.) Is anybody against doing this, or has other recommendations for dialects we should use? Regards, Oliver [1] https://osmocom.org/issues/3598 [2] https://gerrit.osmocom.org/c/osmo-pcu/+/15565 [3] https://github.com/torvalds/linux/commit/51b97e354ba9fce1890cf38ecc754aa49677fc89 -- - Oliver Smith 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 From laforge at gnumonks.org Thu Sep 19 05:23:13 2019 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 19 Sep 2019 07:23:13 +0200 Subject: Fwd: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64 In-Reply-To: <5d82dd946696d_1c842ab7120fc5f020369d@build.opensuse.org> References: <5d82dd946696d_1c842ab7120fc5f020369d@build.opensuse.org> Message-ID: In case this wasn't noticed yet, libosmo-netif doesn't build (pass "make check") on debian 8 anymore. This clearly looks like a regression. It happens both on x86_64 and on armv7l. Thanks in advance for anyone finding time to investigate. Cheers (from holidays), Harald -------- Original Message -------- From: OBS Notification Sent: September 19, 2019 3:44:40 AM GMT+02:00 To: Alexander Couzens , Harald Welte , OpenBSC gerrit-log Mailing List Subject: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64 Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-netif/Debian_8.0/x86_64 Package network:osmocom:nightly/libosmo-netif failed to build in Debian_8.0/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-netif Last lines of build log: [ 124s] autoreconnecting test step 3 [client OK, server OK], FD reg 1 [ 124s] [ 124s] autoreconnecting test step 2 [client OK, server OK], FD reg 0 [ 124s] + [ 124s] +autoreconnecting test step 1 [client OK, server OK], FD reg 0 [ 124s] connection closed with srv [ 124s] [ 124s] -autoreconnecting test step 1 [client OK, server NA], FD reg 0 [ 124s] +autoreconnecting test step 0 [client OK, server NA], FD reg 0 [ 124s] [ 124s] non-reconnecting test step 7 [client NA, server OK], FD reg 1 [ 124s] [ 124s] 1. testsuite.at:4: 1. stream_test (testsuite.at:4): FAILED (testsuite.at:8) [ 124s] debian/rules:27: recipe for target 'override_dh_auto_test' failed [ 124s] make[1]: *** [override_dh_auto_test] Error 1 [ 124s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 124s] debian/rules:13: recipe for target 'build' failed [ 124s] make: *** [build] Error 2 [ 124s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 124s] [ 124s] build30 failed "build libosmo-netif_0.6.0.2.a1e9.dsc" at Thu Sep 19 01:44:36 UTC 2019. [ 124s] [ 124s] ### VM INTERACTION START ### [ 125s] Powering off. [ 125s] [ 106.236806] reboot: Power down [ 125s] ### VM INTERACTION END ### [ 125s] [ 125s] build30 failed "build libosmo-netif_0.6.0.2.a1e9.dsc" at Thu Sep 19 01:44:38 UTC 2019. [ 125s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/) -- Sent from a mobile device. Please excuse my brevity. From pespin at sysmocom.de Thu Sep 19 13:38:36 2019 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Thu, 19 Sep 2019 15:38:36 +0200 Subject: Fwd: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64 In-Reply-To: References: <5d82dd946696d_1c842ab7120fc5f020369d@build.opensuse.org> Message-ID: <71f16b8a-cb66-0fe7-f244-6d2e6c9766c2@sysmocom.de> Hi On 9/19/19 7:23 AM, Harald Welte wrote: > In case this wasn't noticed yet, libosmo-netif doesn't build (pass "make check") on debian 8 anymore. This clearly looks like a regression. It happens both on x86_64 and on armv7l. I submitted these two patches to make the test more deterministic regarding time and order of events. Let's see if it fixes the issue, otherwise the introduced new log format will ease debugging: https://gerrit.osmocom.org/c/libosmo-netif/+/15576 stream_test: Log fake time https://gerrit.osmocom.org/c/libosmo-netif/+/15575 stream_test: Use fake time -- - Pau Espin Pedrol 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 From nhofmeyr at sysmocom.de Mon Sep 30 15:55:14 2019 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 30 Sep 2019 17:55:14 +0200 Subject: Fwd: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64 In-Reply-To: <71f16b8a-cb66-0fe7-f244-6d2e6c9766c2@sysmocom.de> References: <5d82dd946696d_1c842ab7120fc5f020369d@build.opensuse.org> <71f16b8a-cb66-0fe7-f244-6d2e6c9766c2@sysmocom.de> Message-ID: <20190930155514.GA17164@my.box> On Thu, Sep 19, 2019 at 03:38:36PM +0200, Pau Espin Pedrol wrote: > https://gerrit.osmocom.org/c/libosmo-netif/+/15575 stream_test: Use fake > time Excellent, Pau, thanks! This stream_test was irritating me from the start :) It was short enough and almost not worth the effort to act on it, but still it was an ever so slight provocation on every build. Am glad that delay is gone. ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: