January 2017 - OpenBSC - lists.osmocom.org

by OMAR RAMADAN

If the SIP server dies in the middle of a call, osmo-sip-connector is in a bad state and generates a never ending stream of error messages: 58): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f258): zero length packettport(0xb7e9f25 It looks like the messages are generated from sofia-sip and I have managed to suppress the messages by setting the environment variable SU_DEBUG < 3: http://sofia-sip.sourcearchive.com/documentation/1.12.7/tport__internal_8h_… However, it looks like osmo-sip-connector is clearly in a bad state when this happens and we need a way to detect and release these ghosted calls.

7 years, 1 month

4
15
0 0

[PATCH net-next v2 0/6] gtp: misc improvements

by Andreas Schultz

Hi Pablo, Resent as v2, because I forgot the net-next target. Sorry for noise, I promise I won't forget it again. This series lays the groundwork for removing the socket references from the GTP netdevice by removing duplicate code and simplifying the logic on some code paths. It slighly changes the GTP genl API by making the socket parameters optional (though one of them is still required). The removal of the socket references will break the 1:1 releation between GTP netdevice and GTP socket that prevents us to support multiple VRFs with overlaping IP addresse spaces attached to the same GTP socket (needed for multi APN support). Regards Andreas Andreas Schultz (6): gtp: make GTP sockets in gtp_newlink optional gtp: merge gtp_get_net and gtp_genl_find_dev gtp: unify genl_find_pdp and prepare for per socket lookup gtp: consolidate pdp context destruction into helper gtp: add socket to pdp context gtp: consolidate gtp socket rx path drivers/net/gtp.c | 564 +++++++++++++++++++++++++++--------------------------- 1 file changed, 280 insertions(+), 284 deletions(-) -- 2.10.2

7 years, 2 months

5
28
0 0

Channel release error when osmo-nitb want execute location update

by Hossein Amini

hi dear I install openbsc, osmosgsn, ggsn, osmo-trx, osmo-bts-trx, osmo-pcu and dependency from master branch step by step from this link. <https://osmocom.org/projects/cellular-infrastructure/wiki/OpenBSC_GPRS> but when run osmo-nitb, osmo-trx and osmo-bts-trx, mobile connect to network but no access to network. (I used USRP N210/B210, ubuntu 15.10/16.10 64x) osmo-nitb log: 20170130041914525 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Allocating lchan=0 as SDCCH 20170130041914525 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(0) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x05 ta=0 20170130041914525 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Tx RSL Channel Activate with act_type=INITIAL 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state NONE -> ACTIVATION REQUESTED 20170130041914525 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVATION REQUESTED -> ACTIVE 20170130041924529 DRSL <0004> abis_rsl.c:852 (bts=0,trx=0,ts=0,ss=0) RF Channel Release due to error: 1 20170130041924529 DRSL <0004> abis_rsl.c:762 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20170130041924529 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVE -> RELEASE DUE ERROR 20170130041924530 DRSL <0004> abis_rsl.c:925 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK 20170130041926530 DRSL <0004> abis_rsl.c:811 (bts=0,trx=0,ts=0,ss=0) is back in operation. 20170130041926531 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state RELEASE DUE ERROR -> NONE NITB config: ! ! OpenBSC (0.15.0.646-f1886-dirty) configuration saved from vty !! password foo ! log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rll debug logging level cc debug logging level mm info logging level rr info logging level rsl debug logging level nm debug logging level mncc debug logging level pag debug logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs notice logging level ns info logging level bssgp notice logging level llc notice logging level sndcp notice logging level nat notice logging level ctrl notice logging level smpp notice logging level filter notice logging level ranap debug logging level sua debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive ipa bind 127.0.0.1 network network country code 432 mobile network code 70 short name dynch long name dynch auth policy accept-all authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 4 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3122 10 timer t3141 0 subscriber-keep-in-ram 0 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 1 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator ascending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1800 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 0 gprs network-control-order nc1 gprs cell bvci 1800 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 1800 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 1800 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.1 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si trx 0 rf_locked 0 arfcn 0 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h hr nitb subscriber-create-on-demand assign-tmsi OSMO-BTS-TRX Config file ! ! OsmoBTS (0.4.0.372-f65b) configuration saved from vty !! ! log stderr logging filter all 1 logging color 0 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rsl debug logging level oml debug logging level rll notice logging level rr notice logging level meas notice logging level pag info logging level l1c debug logging level l1p info logging level dsp debug logging level pcu notice logging level ho notice logging level trx notice logging level loop notice logging level abis notice logging level rtp notice logging level sum notice logging level lglobal notice logging level llapd debug logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive phy 0 osmotrx ip 127.0.0.1 osmotrx fn-advance 20 osmotrx rts-advance 5 osmotrx tx-attenuation oml instance 0 bts 0 band GSM900 ipa unit-id 1800 0 oml remote-ip 127.0.0.1 rtp jitter-buffer 100 paging queue-size 200 paging lifetime 0 uplink-power-target -75 min-qual-rach 50 min-qual-norm -5 no ms-power-loop timing-advance-loop trx 0 power-ramp max-initial 23000 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 0 Regards

7 years, 2 months

2
1
0 0

Pcs1900 cant make calls ...only messages

by Rajitha peiris

Hello all I have installed openbsc with pcs1900 nano bts but I can't make voice calls only the messages. It's telling network busy Thanks Regards Rajitha Sri Lanka Sent from my iPhone On Jan 27, 2017, at 3:11 PM, "openbsc-request(a)lists.osmocom.org<mailto:openbsc-request@lists.osmocom.org>" <openbsc-request(a)lists.osmocom.org<mailto:openbsc-request@lists.osmocom.org>> wrote: Send OpenBSC mailing list submissions to openbsc(a)lists.osmocom.org<mailto:openbsc@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<mailto:openbsc-request@lists.osmocom.org> You can reach the person managing the list at openbsc-owner(a)lists.osmocom.org<mailto:openbsc-owner@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. Re: [MERGED] osmo-trx[master]: Do not embed sqlite3 when building (Alexander Chemeris) 2. Re: [PATCH net v2 3/3] gtp: fix cross netns recv on gtp socket (David Miller) 3. Re: [MERGED] osmo-trx[master]: Do not embed sqlite3 when building (Neels Hofmeyr) 4. HEADS UP: jenkins DOWN (Neels Hofmeyr) 5. HEADS DOWN: jenkins UP (Neels Hofmeyr) 6. Re: HEADS DOWN: jenkins UP (Holger Freyther) 7. [PATCH net v3 0/3] various gtp fixes (Andreas Schultz) 8. [PATCH net v3 2/3] gtp: clear DF bit on GTP packet tx (Andreas Schultz) ---------------------------------------------------------------------- Message: 1 Date: Thu, 26 Jan 2017 20:53:07 +0400 From: Alexander Chemeris <alexander.chemeris(a)gmail.com<mailto:alexander.chemeris@gmail.com>> To: Max <msuraev(a)sysmocom.de<mailto:msuraev@sysmocom.de>> Cc: OpenBSC Mailing List <openbsc(a)lists.osmocom.org<mailto:openbsc@lists.osmocom.org>> Subject: Re: [MERGED] osmo-trx[master]: Do not embed sqlite3 when building Message-ID: <CABmJbFUifn=3OdUWH=aH5Nij9xz4v7Z3HCm09SQEHOBkaEBtXA(a)mail.gmail.com<mailto:CABmJbFUifn=3OdUWH=aH5Nij9xz4v7Z3HCm09SQEHOBkaEBtXA@mail.gmail.com>> Content-Type: text/plain; charset=UTF-8 Great. I was also going to ask about debian contrl files, etc. Glad this is already fixed. Is there a way to subscribe to gerrit patches for a particular project? On Thu, Jan 26, 2017 at 8:10 PM, Max <msuraev(a)sysmocom.de<mailto:msuraev@sysmocom.de>> wrote: It should have been removed with gerrit 1485 <https://gerrit.osmocom.org/1485>. See also gerrit 1691 <https://gerrit.osmocom.org/1691> for follow-up fixes. On 26.01.2017 16:53, Alexander Chemeris wrote: Hi Harald, Thomas, I think it also makes sense to remove sqlite3 subdirectory, since it's no longer used. Any reason it's kept in the repository? -- Max Suraev <msuraev(a)sysmocom.de<mailto:msuraev@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 -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co ------------------------------ Message: 2 Date: Thu, 26 Jan 2017 14:22:47 -0500 (EST) From: David Miller <davem(a)davemloft.net<mailto:davem@davemloft.net>> To: aschultz(a)tpip.net<mailto:aschultz@tpip.net> Cc: pablo(a)netfilter.org<mailto:pablo@netfilter.org>, netdev(a)vger.kernel.org<mailto:netdev@vger.kernel.org>, Lionel.Gauthier(a)eurecom.fr<mailto:Lionel.Gauthier@eurecom.fr>, openbsc(a)lists.osmocom.org<mailto:openbsc@lists.osmocom.org>, laforge(a)gnumonks.org<mailto:laforge@gnumonks.org> Subject: Re: [PATCH net v2 3/3] gtp: fix cross netns recv on gtp socket Message-ID: <20170126.142247.527598780818100974.davem(a)davemloft.net<mailto:20170126.142247.527598780818100974.davem@davemloft.net>> Content-Type: Text/Plain; charset=iso-8859-7 From: Andreas Schultz <aschultz(a)tpip.net<mailto:aschultz@tpip.net>> Date: Thu, 26 Jan 2017 16:11:34 +0100 The use of the passed through netlink src_net to check for a cross netns operation was wrong. Using the GTP socket and the GTP netdevice is always correct (even if the netdev has been moved to new netns after link creation). Remove the now obsolete net field from gtp_dev. Signed-off-by: Andreas Schultz <aschultz(a)tpip.net<mailto:aschultz@tpip.net>> Please at least compile test your submissions: drivers/net/gtp.c: In function ?gtp_newlink?: drivers/net/gtp.c:677:8: error: too many arguments to function ?gtp_encap_enable? err = gtp_encap_enable(dev, gtp, fd0, fd1, src_net); ^ drivers/net/gtp.c:659:12: note: declared here static int gtp_encap_enable(struct net_device *dev, struct gtp_dev *gtp, ^ drivers/net/gtp.c: At top level: drivers/net/gtp.c:822:12: error: conflicting types for ?gtp_encap_enable? static int gtp_encap_enable(struct net_device *dev, struct gtp_dev *gtp, ^ drivers/net/gtp.c:659:12: note: previous declaration of ?gtp_encap_enable? was here static int gtp_encap_enable(struct net_device *dev, struct gtp_dev *gtp, ^ drivers/net/gtp.c:659:12: warning: ?gtp_encap_enable? used but never defined drivers/net/gtp.c:822:12: warning: ?gtp_encap_enable? defined but not used [-Wunused-function] static int gtp_encap_enable(struct net_device *dev, struct gtp_dev *gtp, ^ scripts/Makefile.build:299: recipe for target 'drivers/net/gtp.o' failed ------------------------------ Message: 3 Date: Thu, 26 Jan 2017 21:40:27 +0100 From: Neels Hofmeyr <nhofmeyr(a)sysmocom.de<mailto:nhofmeyr@sysmocom.de>> To: Alexander Chemeris <alexander.chemeris(a)gmail.com<mailto:alexander.chemeris@gmail.com>> Cc: Max <msuraev(a)sysmocom.de<mailto:msuraev@sysmocom.de>>, OpenBSC Mailing List <openbsc(a)lists.osmocom.org<mailto:openbsc@lists.osmocom.org>> Subject: Re: [MERGED] osmo-trx[master]: Do not embed sqlite3 when building Message-ID: <20170126204027.GA7681(a)my.box<mailto:20170126204027.GA7681@my.box>> Content-Type: text/plain; charset="us-ascii" On Thu, Jan 26, 2017 at 08:53:07PM +0400, Alexander Chemeris wrote: Great. I was also going to ask about debian contrl files, etc. Glad this is already fixed. Is there a way to subscribe to gerrit patches for a particular project? I'm not sure, but I guess not. We have our gerrit-log mailing list that catches all changes https://lists.osmocom.org/mailman/listinfo/gerrit-log -- otherwise take a look at your user's settings, maybe there's such a feature hidden there? ~N

7 years, 2 months

1
0
0 0

Channel release error when osmo-nitb want execute location update

by Hossein Amini

hi dear I install openbsc, osmosgsn, ggsn, osmo-trx, osmo-bts-trx, osmo-pcu and dependency from master branch step by step from this link. <https://osmocom.org/projects/cellular-infrastructure/wiki/OpenBSC_GPRS> but when run osmo-nitb, osmo-trx and osmo-bts-trx, mobile connect to network but no access to network. (I used USRP N210 and B210, Ubuntu 15.10/16.10 x64) osmo-nitb log: 20170130041914525 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Allocating lchan=0 as SDCCH 20170130041914525 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(0) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x05 ta=0 20170130041914525 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Tx RSL Channel Activate with act_type=INITIAL 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state NONE -> ACTIVATION REQUESTED 20170130041914525 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVATION REQUESTED -> ACTIVE 20170130041924529 DRSL <0004> abis_rsl.c:852 (bts=0,trx=0,ts=0,ss=0) RF Channel Release due to error: 1 20170130041924529 DRSL <0004> abis_rsl.c:762 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20170130041924529 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVE -> RELEASE DUE ERROR 20170130041924530 DRSL <0004> abis_rsl.c:925 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK 20170130041926530 DRSL <0004> abis_rsl.c:811 (bts=0,trx=0,ts=0,ss=0) is back in operation. 20170130041926531 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state RELEASE DUE ERROR -> NONE NITB config: ! ! OpenBSC (0.15.0.646-f1886-dirty) configuration saved from vty !! password foo ! log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rll debug logging level cc debug logging level mm info logging level rr info logging level rsl debug logging level nm debug logging level mncc debug logging level pag debug logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs notice logging level ns info logging level bssgp notice logging level llc notice logging level sndcp notice logging level nat notice logging level ctrl notice logging level smpp notice logging level filter notice logging level ranap debug logging level sua debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive ipa bind 127.0.0.1 network network country code 432 mobile network code 70 short name dynch long name dynch auth policy accept-all authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 4 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3122 10 timer t3141 0 subscriber-keep-in-ram 0 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 1 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator ascending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1800 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 0 gprs network-control-order nc1 gprs cell bvci 1800 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 1800 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 1800 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.1 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si trx 0 rf_locked 0 arfcn 0 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h hr nitb subscriber-create-on-demand assign-tmsi OSMO-BTS-TRX Config file ! ! OsmoBTS (0.4.0.372-f65b) configuration saved from vty !! ! log stderr logging filter all 1 logging color 0 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rsl debug logging level oml debug logging level rll notice logging level rr notice logging level meas notice logging level pag info logging level l1c debug logging level l1p info logging level dsp debug logging level pcu notice logging level ho notice logging level trx notice logging level loop notice logging level abis notice logging level rtp notice logging level sum notice logging level lglobal notice logging level llapd debug logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive phy 0 osmotrx ip 127.0.0.1 osmotrx fn-advance 20 osmotrx rts-advance 5 osmotrx tx-attenuation oml instance 0 bts 0 band GSM900 ipa unit-id 1800 0 oml remote-ip 127.0.0.1 rtp jitter-buffer 100 paging queue-size 200 paging lifetime 0 uplink-power-target -75 min-qual-rach 50 min-qual-norm -5 no ms-power-loop timing-advance-loop trx 0 power-ramp max-initial 23000 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 0 Regards! openbsc(a)lists.osmocom.org

7 years, 2 months

1
0
0 0

[PATCH 0/6] gtp: misc improvements

by Andreas Schultz

Hi Pablo, This series lays the groundwork for removing the socket references from the GTP netdevice by removing duplicate code and simplifying the logic on some code paths. It slighly changes the GTP genl API by making the socket parameters optional (though one of them is still required). The removal of the socket references will break the 1:1 releation between GTP netdevice and GTP socket that prevents us to support multiple VRFs with overlaping IP addresse spaces attached to the same GTP socket (needed for multi APN support). Regards Andreas -- Andreas Schultz (6): gtp: make GTP sockets in gtp_newlink optional gtp: merge gtp_get_net and gtp_genl_find_dev gtp: unify genl_find_pdp and prepare for per socket lookup gtp: consolidate pdp context destruction into helper gtp: add socket to pdp context gtp: consolidate gtp socket rx path drivers/net/gtp.c | 564 +++++++++++++++++++++++++++--------------------------- 1 file changed, 280 insertions(+), 284 deletions(-) -- 2.10.2

7 years, 2 months

1
6
0 0

Channel release error when osmo-nitb want execute location update

by Hossein Amini

hi dear I install openbsc, osmosgsn, ggsn, osmo-trx, osmo-bts-trx, osmo-pcu and dependency from master branch step by step from this link. <https://osmocom.org/projects/cellular-infrastructure/wiki/OpenBSC_GPRS> but when run osmo-nitb, osmo-trx and osmo-bts-trx, mobile connect to network but no access to network. (I used USRP N210 and B210.) osmo-nitb log: 20170130041914525 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Allocating lchan=0 as SDCCH 20170130041914525 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(0) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x05 ta=0 20170130041914525 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Tx RSL Channel Activate with act_type=INITIAL 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state NONE -> ACTIVATION REQUESTED 20170130041914525 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK 20170130041914525 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVATION REQUESTED -> ACTIVE 20170130041924529 DRSL <0004> abis_rsl.c:852 (bts=0,trx=0,ts=0,ss=0) RF Channel Release due to error: 1 20170130041924529 DRSL <0004> abis_rsl.c:762 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20170130041924529 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVE -> RELEASE DUE ERROR 20170130041924530 DRSL <0004> abis_rsl.c:925 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK 20170130041926530 DRSL <0004> abis_rsl.c:811 (bts=0,trx=0,ts=0,ss=0) is back in operation. 20170130041926531 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state RELEASE DUE ERROR -> NONE NITB config: ! ! OpenBSC (0.15.0.646-f1886-dirty) configuration saved from vty !! password foo ! log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rll debug logging level cc debug logging level mm info logging level rr info logging level rsl debug logging level nm debug logging level mncc debug logging level pag debug logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs notice logging level ns info logging level bssgp notice logging level llc notice logging level sndcp notice logging level nat notice logging level ctrl notice logging level smpp notice logging level filter notice logging level ranap debug logging level sua debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive ipa bind 127.0.0.1 network network country code 432 mobile network code 70 short name dynch long name dynch auth policy accept-all authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 4 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3122 10 timer t3141 0 subscriber-keep-in-ram 0 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 1 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator ascending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1800 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 0 gprs network-control-order nc1 gprs cell bvci 1800 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 1800 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 1800 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.1 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si trx 0 rf_locked 0 arfcn 0 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h hr nitb subscriber-create-on-demand assign-tmsi OSMO-BTS-TRX Config file ! ! OsmoBTS (0.4.0.372-f65b) configuration saved from vty !! ! log stderr logging filter all 1 logging color 0 logging print category 1 logging print extended-timestamp 1 logging level all everything logging level rsl debug logging level oml debug logging level rll notice logging level rr notice logging level meas notice logging level pag info logging level l1c debug logging level l1p info logging level dsp debug logging level pcu notice logging level ho notice logging level trx notice logging level loop notice logging level abis notice logging level rtp notice logging level sum notice logging level lglobal notice logging level llapd debug logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive phy 0 osmotrx ip 127.0.0.1 osmotrx fn-advance 20 osmotrx rts-advance 5 osmotrx tx-attenuation oml instance 0 bts 0 band GSM900 ipa unit-id 1800 0 oml remote-ip 127.0.0.1 rtp jitter-buffer 100 paging queue-size 200 paging lifetime 0 uplink-power-target -75 min-qual-rach 50 min-qual-norm -5 no ms-power-loop timing-advance-loop trx 0 power-ramp max-initial 23000 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 0 Regards!

7 years, 2 months

1
0
0 0

[PATCH net-next v2 0/2] gtp: simple gtp improvements

by Andreas Schultz

This is the part of the previous "simple gtp improvements" series that Pablo indicated should go into net-next. The rcu_lock removal is small correctness changes. Passing invalid to user space allows for more standards compliant handling of invalid tunnels. -- Andreas Schultz (2): gtp: remove unnecessary rcu_read_lock gtp: let userspace handle packets for invalid tunnels drivers/net/gtp.c | 24 ++++-------------------- 1 file changed, 4 insertions(+), 20 deletions(-) -- 2.10.2

7 years, 2 months

2
3
0 0

[PATCH net v3 0/3] various gtp fixes

by Andreas Schultz

I'm sorry for the compile error mess up in the last version. It's no excuse for not test compiling, but the hunks got lost in a rebase. This is the part of the previous "simple gtp improvements" series that Pablo indicated should go into net. The addition of the module alias fixes genl family autoloading, clearing the DF bit fixes a protocol violation in regard to the specification and the netns comparison fixes a corner case of cross netns recv. Andreas v2->v3: fix compiler error introduced in rebase -- Andreas Schultz (3): gtp: add genl family modules alias gtp: clear DF bit on GTP packet tx gtp: fix cross netns recv on gtp socket drivers/net/gtp.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) -- 2.10.2

7 years, 2 months

2
4
0 0

HEADS UP: jenkins DOWN

by Neels Hofmeyr

While I was waiting for jenkins just now, I noticed that it was getting impossibly slow despite an idle CPU. An attempt to restart resulted in failure to launch jenkins due to "Disk quota exceeded". There are things happening that I don't understand (file system is shrinking as I remove files). I need help from Holger (or Harald?), to understand and probably fix with a simple command making more space for the jail... Until then our jenkins will be DOWN :/ ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 2 months

2
2
0 0

Re: [MERGED] osmo-trx[master]: Do not embed sqlite3 when building

by Neels Hofmeyr

Looks related to this osmo-trx nightly package build breakage? https://osmocom.org/issues/1928 ~N On Wed, Jan 25, 2017 at 07:42:53PM +0000, Harald Welte wrote: > Harald Welte has submitted this change and it was merged. > > Change subject: Do not embed sqlite3 when building > ...................................................................... > > > Do not embed sqlite3 when building > > Change-Id: If5edadc04c3ff953b451676e55ad3d00d4e43c82 > --- > M Makefile.am > M Makefile.common > 2 files changed, 1 insertion(+), 2 deletions(-) > > Approvals: > Tom Tsou: Looks good to me, approved > Harald Welte: Looks good to me, but someone else must approve > Jenkins Builder: Verified > > > > diff --git a/Makefile.am b/Makefile.am > index 06251f0..f9f5a5c 100644 > --- a/Makefile.am > +++ b/Makefile.am > @@ -28,7 +28,6 @@ > > # Order must be preserved > SUBDIRS = \ > - sqlite3 \ > CommonLibs \ > GSM \ > Transceiver52M > diff --git a/Makefile.common b/Makefile.common > index 734ab3a..d7927a5 100644 > --- a/Makefile.common > +++ b/Makefile.common > @@ -33,6 +33,6 @@ > > COMMON_LA = $(top_builddir)/CommonLibs/libcommon.la > GSM_LA = $(top_builddir)/GSM/libGSM.la > -SQLITE_LA = $(top_builddir)/sqlite3/libsqlite.la -ldl > +SQLITE_LA = -lsqlite3 > > MOSTLYCLEANFILES = *~ > > -- > To view, visit https://gerrit.osmocom.org/1484 > To unsubscribe, visit https://gerrit.osmocom.org/settings > > Gerrit-MessageType: merged > Gerrit-Change-Id: If5edadc04c3ff953b451676e55ad3d00d4e43c82 > Gerrit-PatchSet: 2 > Gerrit-Project: osmo-trx > Gerrit-Branch: master > Gerrit-Owner: Max <msuraev(a)sysmocom.de> > Gerrit-Reviewer: Harald Welte <laforge(a)gnumonks.org> > Gerrit-Reviewer: Jenkins Builder > Gerrit-Reviewer: Ruben Undheim <ruben.undheim(a)gmail.com> > Gerrit-Reviewer: Tom Tsou <tom(a)tsou.cc> -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 2 months

3
4
0 0

[PATCH net v2 0/3] various gtp fixes

by Andreas Schultz

This is the part of the previous "simple gtp improvements" series that Pablo indicated should go into net. The addition of the module alias fixes genl family autoloading, clearing the DF bit fixes a protocol violation in regard to the specification and the netns comparison fixes a corner case of cross netns recv. I'm not sure if Pablos comments on the previous version qualify as ACK, so I left that out. -- Andreas Schultz (3): gtp: add genl family modules alias gtp: clear DF bit on GTP packet tx gtp: fix cross netns recv on gtp socket drivers/net/gtp.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) -- 2.10.2

7 years, 2 months

3
7
0 0

test error analysis on build services

by Neels Hofmeyr

On jenkins and opensuse, we have builds where we cannot easily analyse the testsuite.dir after a build failed. So we only see which tests failed and not why. On jenkins I have in most places added a script invocation that prints all testsuite.dir/*/*.log in case of build failure, so we can see it in the jenkins log right away. On opensuse.org, IIUC, the 'make check' is run by dh or something, so it's not trivial (to me) to make it output the test logs in case of failure. I'm thinking now, don't we always want to see these failures anyway? We could include in our Makefile.am a tweak to print the test logs in case of testsuite failure. Sometimes this output can become fairly large though; e.g. when a long test fails early and prints "nothing", the test log shows a huge diff with all expected output as minus-lines. My main goal right now is to see why/how the libosmo-netif OBS build failed (osmux test fails) without further local reproduction effort. This situation will certainly repeat over and over, for all of the other projects as well. What do you think? Can we get that easily? ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 2 months

2
2
0 0

jenkins nr of executors

by Neels Hofmeyr

FYI, no "Broken Pipe" errors in a long time, so today I increased the OsmocomBuild1 nr of executors from 3 to 4 ... and immediately got two subsequent openbsc builds hitting the "Broken Pipe" again. https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/1716/IU=--enable-iu,… https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/1717/IU=--disable-iu… This time I tried something else: lower the "make -j 9" to "make -j 3" and leave the nr of executors at 4... Just dabbling, would be nicer to pinpoint the real cause. ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 2 months

1
0
0 0

[PATCH 0/5] simple gtp improvements

by Andreas Schultz

As requested are here the simple and most obvious changes from the larger GTP changeset. I'll break down the rest and send them out separately. The module alias addition and the rcu_lock removal are just small convenience changes. The other changes are needed to correctly implement one of the 3GPP GW functions, userspace needs to see invalid T-PDU's in order to generate the proper error messages, GTP fragmentation rules need the cleared DF bit. Andreas -- Andreas Schultz (5): gtp: add genl family modules alias gtp: clear DF bit on GTP packet tx gtp: fix cross netns recv on gtp socket gtp: remove unnecessary rcu_read_lock gtp: let userspace handle packets for invalid tunnels drivers/net/gtp.c | 33 ++++++++------------------------- 1 file changed, 8 insertions(+), 25 deletions(-) -- 2.10.2

7 years, 2 months

4
14
0 0

[PATCH v2 00/18] 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. v2 changes: * the socket that is hold by the pdp context has to be release in a rcu callback. Otherwise a stray GTP rx could end uo with an invalid socket. * accessing the skb->sk field in gtp_rx is invalid, that field has no been populated at that point * add dst_cache to speed up the routing Regards Andreas -- Andreas Schultz (18): 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 gtp: add dst_cache support drivers/net/gtp.c | 714 +++++++++++++++++++++++++++-------------------- include/uapi/linux/gtp.h | 4 + 2 files changed, 422 insertions(+), 296 deletions(-) -- 2.10.2

7 years, 2 months

3
20
0 0

Build failure of network:osmocom:nightly/osmo-trx in xUbuntu_16.04/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 408s] #define HAVE_SYS_TYPES_H 1 [ 408s] #define HAVE_SYS_STAT_H 1 [ 408s] #define HAVE_STDLIB_H 1 [ 408s] #define HAVE_STRING_H 1 [ 408s] #define HAVE_MEMORY_H 1 [ 408s] #define HAVE_STRINGS_H 1 [ 408s] #define HAVE_INTTYPES_H 1 [ 408s] #define HAVE_STDINT_H 1 [ 408s] #define HAVE_UNISTD_H 1 [ 408s] #define HAVE_DLFCN_H 1 [ 408s] #define LT_OBJDIR ".libs/" [ 408s] #define STDC_HEADERS 1 [ 408s] #define HAVE_BYTESWAP_H 1 [ 408s] #define TIME_WITH_SYS_TIME 1 [ 408s] [ 408s] configure: exit 1 [ 408s] dh_auto_configure: ./configure --build=x86_64-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/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 408s] debian/rules:6: recipe for target 'build' failed [ 408s] make: *** [build] Error 255 [ 408s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 408s] [ 408s] cloud116 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 20:00:47 UTC 2017. [ 408s] [ 408s] ### VM INTERACTION START ### [ 411s] [ 364.791340] reboot: Power down [ 412s] ### VM INTERACTION END ### [ 412s] [ 412s] cloud116 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 20:00:52 UTC 2017. [ 412s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

6
12
0 0

[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

7 years, 3 months

1
17
0 0

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.

7 years, 3 months

2
2
0 0

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

7 years, 3 months

2
2
0 0

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

7 years, 3 months

3
5
0 0

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

7 years, 3 months

4
5
0 0

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/

7 years, 3 months

2
1
0 0

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

7 years, 3 months

2
2
0 0

Intregation with usrp

by Snehasish Kar

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

7 years, 3 months

4
4
0 0

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/)

7 years, 3 months

1
0
0 0

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/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.04/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [ 99s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o vty_interface_cmds.o vty_interface_cmds.c [ 100s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_patch.o mgcp_patch.c [ 100s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_callagent.o mgcp_callagent.c [ 100s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o isup_filter.o isup_filter.c [ 100s] gcc -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o cellmgr_ng main.o mtp_layer3.o thread.o ipaccess.o pcap.o bss_patch.o bssap_sccp.o bsc_sccp.o bsc_ussd.o links.o msc_conn.o link_udp.o snmp_mtp.o debug.o isup.o mtp_link.o counter.o sccp_state.o bsc.o ss7_application.o vty_interface_legacy.o vty_interface_cmds.o mgcp_patch.o mgcp_callagent.o isup_filter.o -ltalloc -losmocore -ltalloc -losmogsm -losmocore -ltalloc -losmovty -losmocore -losmosccp -losmoxua -lpthread -lnetsnmp -lcrypto [ 100s] /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libosmosccp.so: undefined reference to `talloc_free' [ 100s] collect2: error: ld returned 1 exit status [ 100s] Makefile:425: recipe for target 'cellmgr_ng' failed [ 100s] make[3]: *** [cellmgr_ng] Error 1 [ 100s] make[3]: Leaving directory '/usr/src/packages/BUILD/src' [ 100s] Makefile:380: recipe for target 'all-recursive' failed [ 100s] make[2]: *** [all-recursive] Error 1 [ 100s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 100s] Makefile:321: recipe for target 'all' failed [ 100s] make[1]: *** [all] Error 2 [ 100s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 100s] dh_auto_build: make -j1 returned exit code 2 [ 100s] debian/rules:23: recipe for target 'build' failed [ 100s] make: *** [build] Error 2 [ 100s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 100s] [ 100s] lamb04 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:11:55 UTC 2017. [ 100s] [ 100s] ### VM INTERACTION START ### [ 103s] [ 89.910909] reboot: Power down [ 103s] ### VM INTERACTION END ### [ 103s] [ 103s] lamb04 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:11:58 UTC 2017. [ 103s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-netif in xUbuntu_16.10/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-netif failed to build in xUbuntu_16.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-netif Last lines of build log: [ 194s] [ 194s] You may investigate any problem if you feel able to do so, in which [ 194s] case the test suite provides a good starting point. Its output may [ 194s] be found below `tests/testsuite.dir'. [ 194s] [ 194s] Makefile:641: recipe for target 'check-local' failed [ 194s] make[4]: *** [check-local] Error 1 [ 194s] make[4]: Leaving directory '/usr/src/packages/BUILD/tests' [ 194s] Makefile:494: recipe for target 'check-am' failed [ 194s] make[3]: *** [check-am] Error 2 [ 194s] make[3]: Leaving directory '/usr/src/packages/BUILD/tests' [ 194s] Makefile:466: recipe for target 'check-recursive' failed [ 194s] make[2]: *** [check-recursive] Error 1 [ 194s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 194s] Makefile:757: recipe for target 'check' failed [ 194s] make[1]: *** [check] Error 2 [ 194s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 194s] dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 [ 194s] debian/rules:13: recipe for target 'build' failed [ 194s] make: *** [build] Error 2 [ 194s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 194s] [ 194s] cloud116 failed "build libosmo-netif_0.0.7.20170117.dsc" at Tue Jan 17 20:07:51 UTC 2017. [ 194s] [ 194s] ### VM INTERACTION START ### [ 198s] ### VM INTERACTION END ### [ 198s] [ 198s] cloud116 failed "build libosmo-netif_0.0.7.20170117.dsc" at Tue Jan 17 20:07:55 UTC 2017. [ 198s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.10/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [ 78s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o vty_interface_cmds.o vty_interface_cmds.c [ 79s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_patch.o mgcp_patch.c [ 79s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_callagent.o mgcp_callagent.c [ 79s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o isup_filter.o isup_filter.c [ 79s] gcc -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o cellmgr_ng main.o mtp_layer3.o thread.o ipaccess.o pcap.o bss_patch.o bssap_sccp.o bsc_sccp.o bsc_ussd.o links.o msc_conn.o link_udp.o snmp_mtp.o debug.o isup.o mtp_link.o counter.o sccp_state.o bsc.o ss7_application.o vty_interface_legacy.o vty_interface_cmds.o mgcp_patch.o mgcp_callagent.o isup_filter.o -ltalloc -losmocore -ltalloc -losmogsm -losmocore -ltalloc -losmovty -losmocore -losmosccp -losmoxua -lpthread -lnetsnmp -lcrypto [ 79s] /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libosmosccp.so: undefined reference to `talloc_free' [ 79s] collect2: error: ld returned 1 exit status [ 79s] Makefile:425: recipe for target 'cellmgr_ng' failed [ 79s] make[3]: *** [cellmgr_ng] Error 1 [ 79s] make[3]: Leaving directory '/usr/src/packages/BUILD/src' [ 79s] Makefile:380: recipe for target 'all-recursive' failed [ 79s] make[2]: *** [all-recursive] Error 1 [ 79s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 79s] Makefile:321: recipe for target 'all' failed [ 79s] make[1]: *** [all] Error 2 [ 79s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 79s] dh_auto_build: make -j1 returned exit code 2 [ 79s] debian/rules:23: recipe for target 'build' failed [ 79s] make: *** [build] Error 2 [ 79s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 79s] [ 79s] lamb07 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:06:44 UTC 2017. [ 79s] [ 79s] ### VM INTERACTION START ### [ 82s] [ 68.378653] reboot: Power down [ 82s] ### VM INTERACTION END ### [ 82s] [ 82s] lamb07 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:06:47 UTC 2017. [ 82s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-stp 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/osmo-stp failed to build in xUbuntu_16.04/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [ 123s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o vty_interface_cmds.o vty_interface_cmds.c [ 123s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_patch.o mgcp_patch.c [ 123s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_callagent.o mgcp_callagent.c [ 123s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o isup_filter.o isup_filter.c [ 123s] gcc -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o cellmgr_ng main.o mtp_layer3.o thread.o ipaccess.o pcap.o bss_patch.o bssap_sccp.o bsc_sccp.o bsc_ussd.o links.o msc_conn.o link_udp.o snmp_mtp.o debug.o isup.o mtp_link.o counter.o sccp_state.o bsc.o ss7_application.o vty_interface_legacy.o vty_interface_cmds.o mgcp_patch.o mgcp_callagent.o isup_filter.o -ltalloc -losmocore -ltalloc -losmogsm -losmocore -ltalloc -losmovty -losmocore -losmosccp -losmoxua -lpthread -lnetsnmp -lcrypto [ 123s] /usr/lib/gcc/i686-linux-gnu/5/../../../i386-linux-gnu/libosmosccp.so: undefined reference to `talloc_free' [ 123s] collect2: error: ld returned 1 exit status [ 123s] Makefile:425: recipe for target 'cellmgr_ng' failed [ 123s] make[3]: *** [cellmgr_ng] Error 1 [ 123s] make[3]: Leaving directory '/usr/src/packages/BUILD/src' [ 123s] Makefile:380: recipe for target 'all-recursive' failed [ 123s] make[2]: *** [all-recursive] Error 1 [ 123s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 123s] Makefile:321: recipe for target 'all' failed [ 123s] make[1]: *** [all] Error 2 [ 123s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 123s] dh_auto_build: make -j1 returned exit code 2 [ 123s] debian/rules:23: recipe for target 'build' failed [ 123s] make: *** [build] Error 2 [ 123s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 123s] [ 123s] lamb16 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:03:26 UTC 2017. [ 123s] [ 123s] ### VM INTERACTION START ### [ 127s] [ 113.842641] reboot: Power down [ 127s] ### VM INTERACTION END ### [ 127s] [ 127s] lamb16 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:03:30 UTC 2017. [ 127s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-stp 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-stp failed to build in xUbuntu_16.10/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [ 80s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o vty_interface_cmds.o vty_interface_cmds.c [ 80s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_patch.o mgcp_patch.c [ 80s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o mgcp_callagent.o mgcp_callagent.c [ 80s] gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -c -o isup_filter.o isup_filter.c [ 80s] gcc -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o cellmgr_ng main.o mtp_layer3.o thread.o ipaccess.o pcap.o bss_patch.o bssap_sccp.o bsc_sccp.o bsc_ussd.o links.o msc_conn.o link_udp.o snmp_mtp.o debug.o isup.o mtp_link.o counter.o sccp_state.o bsc.o ss7_application.o vty_interface_legacy.o vty_interface_cmds.o mgcp_patch.o mgcp_callagent.o isup_filter.o -ltalloc -losmocore -ltalloc -losmogsm -losmocore -ltalloc -losmovty -losmocore -losmosccp -losmoxua -lpthread -lnetsnmp -lcrypto [ 80s] /usr/lib/gcc/i686-linux-gnu/6/../../../i386-linux-gnu/libosmosccp.so: undefined reference to `talloc_free' [ 80s] collect2: error: ld returned 1 exit status [ 80s] Makefile:425: recipe for target 'cellmgr_ng' failed [ 80s] make[3]: *** [cellmgr_ng] Error 1 [ 80s] make[3]: Leaving directory '/usr/src/packages/BUILD/src' [ 80s] Makefile:380: recipe for target 'all-recursive' failed [ 80s] make[2]: *** [all-recursive] Error 1 [ 80s] make[2]: Leaving directory '/usr/src/packages/BUILD' [ 80s] Makefile:321: recipe for target 'all' failed [ 80s] make[1]: *** [all] Error 2 [ 80s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 80s] dh_auto_build: make -j1 returned exit code 2 [ 80s] debian/rules:23: recipe for target 'build' failed [ 80s] make: *** [build] Error 2 [ 80s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 80s] [ 80s] lamb09 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:02:13 UTC 2017. [ 80s] [ 80s] ### VM INTERACTION START ### [ 83s] [ 70.380259] reboot: Power down [ 84s] ### VM INTERACTION END ### [ 84s] [ 84s] lamb09 failed "build cellmgr-ng_1.4.7.20170117.dsc" at Tue Jan 17 20:02:17 UTC 2017. [ 84s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx 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-trx failed to build in xUbuntu_16.10/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 241s] #define STDC_HEADERS 1 [ 241s] #define HAVE_SYS_TYPES_H 1 [ 241s] #define HAVE_SYS_STAT_H 1 [ 241s] #define HAVE_STDLIB_H 1 [ 241s] #define HAVE_STRING_H 1 [ 241s] #define HAVE_MEMORY_H 1 [ 241s] #define HAVE_STRINGS_H 1 [ 241s] #define HAVE_INTTYPES_H 1 [ 241s] #define HAVE_STDINT_H 1 [ 241s] #define HAVE_UNISTD_H 1 [ 241s] #define HAVE_DLFCN_H 1 [ 241s] #define LT_OBJDIR ".libs/" [ 241s] #define STDC_HEADERS 1 [ 241s] #define HAVE_BYTESWAP_H 1 [ 241s] #define TIME_WITH_SYS_TIME 1 [ 241s] [ 241s] configure: exit 1 [ 241s] 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 returned exit code 1 [ 241s] debian/rules:6: recipe for target 'build' failed [ 241s] make: *** [build] Error 2 [ 241s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 241s] [ 241s] cloud106 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:55:56 UTC 2017. [ 241s] [ 241s] ### VM INTERACTION START ### [ 245s] ### VM INTERACTION END ### [ 245s] [ 245s] cloud106 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:56:01 UTC 2017. [ 245s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx in Debian_8.0/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-trx failed to build in Debian_8.0/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 132s] #define HAVE_STDLIB_H 1 [ 132s] #define HAVE_STRING_H 1 [ 132s] #define HAVE_MEMORY_H 1 [ 132s] #define HAVE_STRINGS_H 1 [ 132s] #define HAVE_INTTYPES_H 1 [ 132s] #define HAVE_STDINT_H 1 [ 132s] #define HAVE_UNISTD_H 1 [ 132s] #define HAVE_DLFCN_H 1 [ 132s] #define LT_OBJDIR ".libs/" [ 132s] #define STDC_HEADERS 1 [ 132s] #define HAVE_BYTESWAP_H 1 [ 132s] #define TIME_WITH_SYS_TIME 1 [ 132s] [ 132s] configure: exit 1 [ 132s] dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=[ 117.804251] serial8250: too much work for irq4 [ 132s] ${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 132s] debian/rules:6: recipe for target 'build' failed [ 132s] make: *** [build] Error 255 [ 132s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 132s] [ 132s] lamb13 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:55:38 UTC 2017. [ 132s] [ 132s] ### VM INTERACTION START ### [ 133s] Powering off. [ 133s] [ 119.012402] reboot: Power down [ 133s] ### VM INTERACTION END ### [ 133s] [ 133s] lamb13 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:55:40 UTC 2017. [ 133s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx in Debian_8.0/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-trx failed to build in Debian_8.0/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 186s] #define HAVE_SYS_STAT_H 1 [ 186s] #define HAVE_STDLIB_H 1 [ 186s] #define HAVE_STRING_H 1 [ 186s] #define HAVE_MEMORY_H 1 [ 186s] #define HAVE_STRINGS_H 1 [ 186s] #define HAVE_INTTYPES_H 1 [ 186s] #define HAVE_STDINT_H 1 [ 186s] #define HAVE_UNISTD_H 1 [ 186s] #define HAVE_DLFCN_H 1 [ 186s] #define LT_OBJDIR ".libs/" [ 186s] #define STDC_HEADERS 1 [ 186s] #define HAVE_BYTESWAP_H 1 [ 186s] #define TIME_WITH_SYS_TIME 1 [ 186s] [ 186s] configure: exit 1 [ 186s] dh_auto_configure: ./configure --build=i586-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libdir=${prefix}/lib/i386-linux-gnu --libexecdir=${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 186s] debian/rules:6: recipe for target 'build' failed [ 186s] make: *** [build] Error 255 [ 186s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 186s] [ 186s] cloud122 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:48 UTC 2017. [ 186s] [ 186s] ### VM INTERACTION START ### [ 187s] Powering off. [ 187s] [ 156.454218] reboot: Power down [ 189s] ### VM INTERACTION END ### [ 189s] [ 189s] cloud122 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:51 UTC 2017. [ 189s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx in xUbuntu_16.10/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 119s] #define HAVE_SYS_TYPES_H 1 [ 119s] #define HAVE_SYS_STAT_H 1 [ 119s] #define HAVE_STDLIB_H 1 [ 119s] #define HAVE_STRING_H 1 [ 119s] #define HAVE_MEMORY_H 1 [ 119s] #define HAVE_STRINGS_H 1 [ 119s] #define HAVE_INTTYPES_H 1 [ 119s] #define HAVE_STDINT_H 1 [ 119s] #define HAVE_UNISTD_H 1 [ 119s] #define HAVE_DLFCN_H 1 [ 119s] #define LT_OBJDIR ".libs/" [ 119s] #define STDC_HEADERS 1 [ 119s] #define HAVE_BYTESWAP_H 1 [ 119s] #define TIME_WITH_SYS_TIME 1 [ 119s] [ 119s] configure: exit 1 [ 119s] dh_auto_configure: ./configure --build=x86_64-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/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 119s] debian/rules:6: recipe for target 'build' failed [ 119s] make: *** [build] Error 2 [ 119s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 119s] [ 119s] lamb04 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:41 UTC 2017. [ 119s] [ 119s] ### VM INTERACTION START ### [ 122s] [ 109.442861] reboot: Power down [ 122s] ### VM INTERACTION END ### [ 122s] [ 122s] lamb04 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:45 UTC 2017. [ 122s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx 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/osmo-trx failed to build in xUbuntu_16.04/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 145s] #define HAVE_SYS_TYPES_H 1 [ 145s] #define HAVE_SYS_STAT_H 1 [ 145s] #define HAVE_STDLIB_H 1 [ 145s] #define HAVE_STRING_H 1 [ 145s] #define HAVE_MEMORY_H 1 [ 145s] #define HAVE_STRINGS_H 1 [ 145s] #define HAVE_INTTYPES_H 1 [ 145s] #define HAVE_STDINT_H 1 [ 145s] #define HAVE_UNISTD_H 1 [ 145s] #define HAVE_DLFCN_H 1 [ 145s] #define LT_OBJDIR ".libs/" [ 145s] #define STDC_HEADERS 1 [ 145s] #define HAVE_BYTESWAP_H 1 [ 145s] #define TIME_WITH_SYS_TIME 1 [ 145s] [ 145s] configure: exit 1 [ 145s] 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 returned exit code 1 [ 145s] debian/rules:6: recipe for target 'build' failed [ 145s] make: *** [build] Error 255 [ 145s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 145s] [ 146s] lamb04 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:15 UTC 2017. [ 146s] [ 146s] ### VM INTERACTION START ### [ 149s] [ 135.329906] reboot: Power down [ 149s] ### VM INTERACTION END ### [ 149s] [ 149s] lamb04 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 19:54:19 UTC 2017. [ 149s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)

7 years, 3 months

1
0
0 0

What hardware is needed for 3G

by Akib Sayyed

Dear list I would like to know what hardware is needed for running 3G network. -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

7 years, 3 months

3
5
0 0

AMR SID length?

by Max

Hi. There seems to be a disagreement between Osmocom libraries as to which is the length of AMR SID RTP payload. According to libosmocodec it's 7 bytes (see amr_len_by_ft in gsm690.c), according to libosmo-netif it's 6 bytes (see amr_ft_to_bytes in amr.c). However, than I look at 3GPP TS 26.101 Table 6 it seems like it should be 8 bytes. Reading http://www.rfc-base.org/txt/rfc-4867.txt did not shed a light except that it can't be lower than 5 bytes. Please help me out - what's the right number of bytes? -- 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

7 years, 3 months

1
0
0 0

jenkins.osmocom.org build slave

by Neels Hofmeyr

Previously I wrote about the "Broken Pipe" error sporadically causing our gerrit tests to fail for unknown reasons. To try and avoid those (successfully as it seems), I reduced the nr of executors for our OsmocomBuild1 debian slave to 2; used to be 6 IIRC. My argument was that 'make -j 9' would anyway utlize the resources, except during the python testing phase. But the build slave queue is getting awfully long sometimes and builds are just sitting and waiting for a long time. But when I 'top' on the build slave, I see the CPU idling between 50% and 90% ... assuming that the CPU activity in docker is also shown on the host OS. So now I increased the nr of executors to 3, seraching the optimum that still avoids the 'Broken Pipe' error. Would of course be much nicer to fix this particular curious failure and just hammer the nr of executors up to the roof again. ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 3 months

2
1
0 0

[PATCH 4/4] core/conv: Add optimized Viterbi decoding

by Vadim Yanitskiy

Hi Tom and all, After a quick look at the 4th patch, related to your optimized Viterbi decoder, I have noticed that currently the convolutional code definitions from the 'src/gsm/gsm0503_conv.c' are out of the 'tests/conv' test coverage... So, I would like to extend the test coverage. All I need are the test vectors, which I'll add to existing ones. Some of them I already found in your 4th patch, but some pending I need to write myself. Right now I have a simple question... Let's look at one example: { .name = "GSM RACH (non-recursive, flushed, not punctured)", .code = &gsm_conv_rach, .in_len = 14, .out_len = 36, // ??? .has_vec = 0, .vec_in = { }, .vec_out = { }, } As I noticed, the 'in_len' may be taken from the code definition: const struct osmo_conv_code gsm0503_rach = { .N = 2, .K = 5, .len = 14, // The 'in_len' is here! .next_output = xcch_output, .next_state = xcch_state, }; But I don't know how to calculate the 'out_len'... Could you please give me some hint? I already started to work on your 4th patch: https://gerrit.osmocom.org/1542 https://gerrit.osmocom.org/1543 With best regards, Vadim Yanitskiy.

7 years, 3 months

1
1
0 0

jenkins env update

by Max

Hi. Please add autoconf-archive package to jenkins build slaves. It contains handy macro necessary for gerrit #1368. -- 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

7 years, 3 months

2
2
0 0

gerrit #1411, asan fix for egprs_puncturing_values

by Neels Hofmeyr

I would like to see https://gerrit.osmocom.org/#/c/1411/ fixed and merged. Firstly, the way the code is written leaves it unclear whether it works as intended. Secondly, this is blocking the effort to do more sanitizer builds in jenkins / gerrit build jobs. Aravind, would you please provide feedback on your availability -- will you get around to this any time soon, or should we try to assign this to someone else? Thanks! ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 3 months

2
3
0 0

redmine main page

by Neels Hofmeyr

I find the link https://osmocom.org/news/ quite valuable, but it's not easy to get there. I would expect a "News" link on http://osmocom.org to point there, so I placed one. We do have a "Planet" link -> http://planet.osmocom.org/ , which is currently broken. Firefox outright refuses to display it: the certificate is invalid/unknown/expired and the site is marked as "only show when secure", so one cannot add a security exception (fail: that should be the user's choice!). Chromium redirects to https://admin-trac.openmoko.org/trac/ ... doesn't match. So I took the liberty to remove the "Planet" link -- for now? All this by editing, in our redmine jail, file /usr/local/www/redmine-3.2.3/plugins/impressum_plugin/init.rb Feedback welcome! ~N -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 3 months

4
9
0 0

Quectel EC20 question

by Petr Štetiar

Hi, according to a lot of sources one would think, that EC20 is based around the Qualcomm MDM9615, but the picture of naked EC20[1] clearly shows, that there is Qualcomm MDM9215 chip soldered on the board. Which source is true? :-) Or it's just a wrong text on that BGA? 1. https://osmocom.org/attachments/download/2501/ec20-naked-top.jpg -- ynezz

7 years, 3 months

2
2
0 0

[openbsc 0.15.0.621-80ab] testsuite: 3 5 failed

by Hossein Amini

hi I compliled OpenBSC in linux kernel 4.2.* and all test was successful but when upgrade my linux to kernel v4.8.* , we face 2 failed test. logs attached Regards Hossein

7 years, 3 months

3
2
0 0

Relicensing optimized Viterbi decoder

by Vadim Yanitskiy

Hi Tom, Recently I already asked for your permission to relicense the GSM 05.03 code from OpenBTS, and now I am contacting you with the same purpose. I am going to move your optimized Viterbi decoder forward, but currently it is licensed under the LGPL v2.1 (or later). To avoid license mix within the core Osmocom library, it would be better to relicense your code to the same one, if you agree. So, the question is: do you agree to relicense your code under the GPLv2-or-later? With best regards, Vadim Yanitskiy.

7 years, 3 months

3
2
0 0

RFC: OsmoDevCon 2017 planning

by Harald Welte

Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc(a)lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] >From 2012 to 2016 we were running a series of small, invitation-only Osmocom Developer Conferences. Access was intentionally restricted to those community members who have demonstrated an existing track record of contribution to any of the projects under the Osmocom umbrella. This format of a small, tightly knit group of about 20 people has been successful over the years, and I have received a lot of positive feedback from past participants. On the other hand, the Osmocom project has grown in scope and diversity, and some of those projects don't have all that much relationship to each other - except being started by people from within the same group. There's the cellular communications (GSM/GPRS/EDGE/UMTS and hopefully at some point LTE) protocols which is attracting a lot of professional users. And then there's pure community projects like rtl-sdr, OsmocomBB, OsmocomGMR and many other efforts. Particularly the cellular infrastructure projects (OsmoBTS, OsmoPCU, OsmoBTS, OsmoNITB, OsmoSGSN, OpenGGSN, OsmoIuh & co) are somehow "standing out" of the othe projects in the context of having a wider user bsae, and in that user base also primarily commercial users. So I'd like to start a discussion on how to possibly change the event format to accomodate the various interests and parties. I definitely don't want to loose the "annual meeting of old friends" atmosphere, while at the same time also opening up to other interested parties. One idea would be to keep OsmoDevCon as-is and have a separate event where non-contributing/developing users / sysadmins / system integrators could also be attending. Another idea would be to split into a 'user day' and 'developer days' format. This is something the netfilter developer workshops have been using for many years, and from my limited insight quite successfully so. The "user day" is more like a traditional tech conference, with a large auditorium and talks oriented towards users / sysadmins / integrators of the software. The "developer days" are the invitation-only part, for known contributing developers only, similar to what we have at OsmoDevCon. Having both events (or both parts of an event) back-to-back has the advantage that a large number of potential speakers for the 'user day' are already present, and they don't have to travel yet another time. One could even structure it further and say we have one user day, one public 'Osmocom cellular developer day' and then the closed 'OsmoDevCon classic', maybe reduced from 4 days to 3 or even 2 days only? What is the general opinion about this? Are there people lurking on this list who would be interested in attending a public 'user day' or even 'developer day' about the Osmocom cellular projects, with presentations and workshops around topics such as running Osmocom based cellular networks? In terms of when/where, I would suggest to keep the tradition of April in Berlin/Germany. But I'm of course very happy if somebody wants to host it some place else... Regards, and looking forward to meeting you [again] in 2017, 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)

7 years, 3 months

6
14
0 0

Contribute to Osmocom and receive a free 3.5G femtocell

by Harald Welte

Dear all, not everyone might have seen the news item that was posted in late December on our website at http://osmocom.org/news/62 I'm looking forward to receiving your proposal on how you would contribute to the Osmocom project if you were to receive one of those free 3.5G femtocells. Quote of the news item below: ------ So please excuse me to cross-post this over several Osmocom project mailing lists. I know that a number of people have either hacked on femtocells in the past, or at least expressed interest in doing so... Osmocom's support for 2G/GSM is mature and widespread. Since 2016, we're taking on the next level: 3G/3.5G. The key to running your own 3G network is to obtain actual 3G cell hardware -- here is an exciting opportunity to get started: No less than 50 femtocells will be given away for free by sysmocom, one of the main drivers of the Osmocom project. To receive a free 3G femtocell, tell us how you will help the Osmocom project drive 3.5G forward if you had one, before the end of January 2017. This marks the launch of the 3.5G Acceleration Project, backed by the Osmocom community. Join us! Find further details on the 3.5G Acceleration Project and receiving your own 3G femtocell for free at https://sysmocom.de/downloads/accelerate_3g5_cfp.pdf. ------ Best regards and happy hacking, Harald Welte -- - 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)

7 years, 3 months

1
0
0 0

Re: libosmocore[master]: libosmocoding: migrate transcoding routines from OsmoBTS

by Harald Welte

On Wed, Jan 04, 2017 at 08:55:45AM +0000, Vadim Yanitskiy wrote: > I think it's due to --enable-sanitize, because > when I am trying to compile libosmocore this way: > > ./configure --enable-static --enable-sanitize > make check > > Some other tests fail (current master version, clang-3.6): > > Regression tests. > 8: gea FAILED (testsuite.at:51) > 9: msgfile FAILED (testsuite.at:59) > 15: lapd FAILED (testsuite.at:96) > 16: gsm0808 FAILED (testsuite.at:102) > 17: gsm0408 FAILED (testsuite.at:108) > 30: bssgp-fc FAILED (testsuite.at:190) I pushed some fixes,see https://gerrit.osmocom.org/1530 and https://gerrit.osmocom.org/1531 - the remaining failures are all LeakSanitizer warnings, and I suspect that while we release all memory back to talloc, talloc itself doesn't release it back to glibc malloc/free, and hence LeakSanitizer is kicking in. A quick online search didn't seem like anyone else has yet come up with a solution for this, so I guess we should turn it off. I remember some discussion on the list about a year ago where the concensus was to disable LeakSanitizer by environment variables on the buildhost anyway? -- - 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)

7 years, 3 months

4
3
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2017