From felangga at gmail.com Sat Dec 2 15:43:40 2017 From: felangga at gmail.com (felangga at gmail.com) Date: Sat, 02 Dec 2017 22:43:40 +0700 Subject: Osmocon failed to flash Message-ID: <14284302.9VqWCQNGkK@felangga> Hello, I'm newbie and want to learn about osmocombb. I already compiled all of the programs, but when I try to upload helloworld program, it stuck on this error $ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/ compal_e88/hello_world.compalram.bin -c got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f7 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 72 r got 2 bytes from modem, data looks like: 82 bf .. got 1 bytes from modem, data looks like: 7d } got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 7f . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: a6 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: d2 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 3a : got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 4d M got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: da . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I don't know if it hardware problem, or software problem. When I try to debug using putty to listen to /dev/ttyUSB0 there is no fmttool erro just like this article said http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html Regards. From laforge at gnumonks.org Sun Dec 3 10:50:15 2017 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 3 Dec 2017 11:50:15 +0100 Subject: Osmocon failed to flash In-Reply-To: <14284302.9VqWCQNGkK@felangga> References: <14284302.9VqWCQNGkK@felangga> Message-ID: <20171203105015.GT7821@nataraja> On Sat, Dec 02, 2017 at 10:43:40PM +0700, felangga at gmail.com wrote: > $ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/ > compal_e88/hello_world.compalram.bin -c have you tried 'c123' without XOR? Are you running in some kind of VM or on bare hardware? The timing is very critical, and some combinations of hardware + drivers + software are not able to fulfill the strict timing requirements. In case of doubt, try using a different computer. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From felangga at gmail.com Sun Dec 3 11:08:04 2017 From: felangga at gmail.com (Felix Angga) Date: Sun, 3 Dec 2017 18:08:04 +0700 Subject: Osmocon failed to flash In-Reply-To: <20171203105015.GT7821@nataraja> References: <14284302.9VqWCQNGkK@felangga> <20171203105015.GT7821@nataraja> Message-ID: Yes I've tried using xor and without xor. I'm running on bare hardware. Linux mint 18. Do I need to configure baud rate? Or the default 115200 should be OK? Hmm okay, i'll try on other computer. Btw, will it be affected with the length of the cable? On Dec 3, 2017 6:00 PM, "Harald Welte" wrote: On Sat, Dec 02, 2017 at 10:43:40PM +0700, felangga at gmail.com wrote: > $ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/ > compal_e88/hello_world.compalram.bin -c have you tried 'c123' without XOR? Are you running in some kind of VM or on bare hardware? The timing is very critical, and some combinations of hardware + drivers + software are not able to fulfill the strict timing requirements. In case of doubt, try using a different computer. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- An HTML attachment was scrubbed... URL: From felangga at gmail.com Sun Dec 3 11:38:20 2017 From: felangga at gmail.com (Felix Angga) Date: Sun, 3 Dec 2017 18:38:20 +0700 Subject: Osmocon failed to flash In-Reply-To: References: <14284302.9VqWCQNGkK@felangga> <20171203105015.GT7821@nataraja> Message-ID: I'm using CP2102 with apprx 1 m stereo cable. I create another jack with shorter cable and still the same error. I have cp2102 and Pl 2303 and has the same resut. My last suspect is the phone. My phone is C118 made in china. Is that any limitations on specified region that support osmocom ? On Dec 3, 2017 6:35 PM, "Tomcs?nyi, Domonkos" wrote: > Hi, > > Length of the cable and the type of serial adapter can also cause some > issues. > > What adapter are you using? > > Cheers, > Domi > > > 2017. dec. 3. d?tummal, 12:09 id?pontban Felix Angga > ?rta: > > Yes I've tried using xor and without xor. > I'm running on bare hardware. Linux mint 18. > Do I need to configure baud rate? Or the default 115200 should be OK? > Hmm okay, i'll try on other computer. > > Btw, will it be affected with the length of the cable? > > > On Dec 3, 2017 6:00 PM, "Harald Welte" wrote: > > On Sat, Dec 02, 2017 at 10:43:40PM +0700, felangga at gmail.com wrote: > > $ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/ > > compal_e88/hello_world.compalram.bin -c > > have you tried 'c123' without XOR? Are you running in some kind of VM > or on bare hardware? The timing is very critical, and some combinations > of hardware + drivers + software are not able to fulfill the strict > timing requirements. > > In case of doubt, try using a different computer. > > -- > - Harald Welte > http://laforge.gnumonks.org/ > ============================================================ > ================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From domi at tomcsanyi.net Sun Dec 3 11:35:08 2017 From: domi at tomcsanyi.net (=?utf-8?B?VG9tY3PDoW55aSwgRG9tb25rb3M=?=) Date: Sun, 3 Dec 2017 12:35:08 +0100 (CET) Subject: Osmocon failed to flash In-Reply-To: References: <14284302.9VqWCQNGkK@felangga> <20171203105015.GT7821@nataraja> Message-ID: Hi, Length of the cable and the type of serial adapter can also cause some issues. What adapter are you using? Cheers, Domi 2017. dec. 3. d?tummal, 12:09 id?pontban Felix Angga ?rta: > Yes I've tried using xor and without xor. > I'm running on bare hardware. Linux mint 18. > Do I need to configure baud rate? Or the default 115200 should be OK? > Hmm okay, i'll try on other computer. > > Btw, will it be affected with the length of the cable? > > > On Dec 3, 2017 6:00 PM, "Harald Welte" wrote: > On Sat, Dec 02, 2017 at 10:43:40PM +0700, felangga at gmail.com wrote: > > $ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/ > > compal_e88/hello_world.compalram.bin -c > > have you tried 'c123' without XOR? Are you running in some kind of VM > or on bare hardware? The timing is very critical, and some combinations > of hardware + drivers + software are not able to fulfill the strict > timing requirements. > > In case of doubt, try using a different computer. > > -- > - Harald Welte http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Sun Dec 3 11:46:14 2017 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 3 Dec 2017 12:46:14 +0100 Subject: Osmocon failed to flash In-Reply-To: References: <14284302.9VqWCQNGkK@felangga> <20171203105015.GT7821@nataraja> Message-ID: Hi, > My last suspect is the phone. My phone is C118 made in china. Is that any > limitations on specified region that support osmocom ? No but a lot of "old" phones have a pretty damaged/ dirty jack connector inside that makes the data transfer unreliable. You could try replacing it. Cheers, Sylvain From felangga at gmail.com Sun Dec 3 13:38:31 2017 From: felangga at gmail.com (Felix Angga) Date: Sun, 3 Dec 2017 20:38:31 +0700 Subject: Osmocon failed to flash In-Reply-To: References: <14284302.9VqWCQNGkK@felangga> <20171203105015.GT7821@nataraja> Message-ID: Hi, thanks for all the support :) I found out that my 2.5mm stereo jack is not long enough into the port. So I try to cut out the plastic and now it work with the Hello World program. But when I try to flash RSSI program, it said that not enough memory 64k blabla... On Sun, Dec 3, 2017 at 6:46 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > > > My last suspect is the phone. My phone is C118 made in china. Is that any > > limitations on specified region that support osmocom ? > > No but a lot of "old" phones have a pretty damaged/ dirty jack > connector inside that makes the data transfer unreliable. > You could try replacing it. > > Cheers, > > Sylvain > -- |* felangga *| ? facebook | *?* www.felangga.id | 082135994120 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Sun Dec 3 19:11:58 2017 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 3 Dec 2017 20:11:58 +0100 Subject: GAPK status update In-Reply-To: References: <20170908131634.fahl5vqfb7gpdudr@nataraja> Message-ID: <20171203191158.GB16589@nataraja> Hi Vadim, [as you requested a response on IRC, sorry for dropping the ball] On Sun, Sep 10, 2017 at 04:52:55PM +0300, Vadim Yanitskiy wrote: > Only libgsmhr do use generic malloc / free calls. And I think there > is no reason to link this library against talloc as there is only > one allocation / deallocation cycle. correct. > BTW: what about the 'laforge/mmx' branch? > Does anything prevents us from merging it to the master? I think it wasn't fully validated yet, so I think unless somebody hacks up a test suite or some other means that make us confident that the MMX optimized version produces the same results as the standard one, we shouldn't merge it. > > Finally, as a personal wishlist item, I would love to see some unit > > tests that create a couple of processing queues, destroy them, check > > if the resulting encode/decodes is what was expected, and [if possible?] > > even check if allocated memory has been properly cleaned up during > > destruction of the processing queue. > > Yeah, I have this idea too. But I don't have enough time > right now. Will do it as soon as it will be possible. Thanks, this would indeed be very useful (also to validate the MMX code as mentioned above) > What do you think about adding GAPK to Gerrit? Fine with me. But then, it's Sylvain's project and I wouldn't want to do anything to it that he isn't asking for / approving of. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Sun Dec 3 21:22:40 2017 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 3 Dec 2017 22:22:40 +0100 Subject: gapk now in gerrit (Re: GAPK status update) In-Reply-To: <20171203191158.GB16589@nataraja> References: <20170908131634.fahl5vqfb7gpdudr@nataraja> <20171203191158.GB16589@nataraja> Message-ID: <20171203212240.GC14790@nataraja> Hi Vadim, On Sun, Dec 03, 2017 at 08:11:58PM +0100, Harald Welte wrote: > > What do you think about adding GAPK to Gerrit? > > Fine with me. But then, it's Sylvain's project and I wouldn't want to do > anything to it that he isn't asking for / approving of. As Sylvain agreed on IRC, I've migrated gapk to gerrit: -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Mon Dec 4 12:23:47 2017 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 4 Dec 2017 13:23:47 +0100 Subject: OsmoDevCon 2018 schedule planning Message-ID: <20171204122347.GN14790@nataraja> Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc at lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] Like every year in early December, it is time to discuss as schedule for OsmoDevCon in the upcoming year. Note: Ths is about OsmoDevCon, the more private meeting of developers, *NOT* about OsmoCon, the public conference. == When, Who, Where == I propose the following date for OsmoDevCon 2018: April 20 - April 23rd, 2018 * Who: Active developers/contributors of Osmocom projects (as usual) * Where: IN-Berlin, Berlin (as usual) Please let me know ASAP if that proposed date works for everyone who'd want to attend. We can still change it now, but I would want to nail down the date pretty soon. == Format == After the experiment of reducing from 4 to 3 days last year (due to OsmoCon), we will again go for *four days* in 2018. However, we should clearly divide the days in a way that e.g. "GSM/3G" topics are on two days, while SDR+Other topics are on the other days, so people not interested in some topics can skip one or two days, as needed. We could even divide it further like: * 1 day 3GPP RAN (osmo-bts, osmo-bsc, osmo-pcu, virt_phy, fake_trx, ...) * 1 day 3GPP CN (osmo-msc, osmo-hlr, osmo-sip-connector, nextepc, etc.) * 2 days misc Regards, and looking forward to meeting you [again] in 2018, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From craig at unreasonablefarm.org Wed Dec 6 03:48:43 2017 From: craig at unreasonablefarm.org (Craig Comstock) Date: Tue, 5 Dec 2017 21:48:43 -0600 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system Message-ID: <20171206034843.GA27384@localhost.localdomain> --- src/target/firmware/Makefile.mtk | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/target/firmware/Makefile.mtk b/src/target/firmware/Makefile.mtk index 30fa2fcf..927e31a0 100644 --- a/src/target/firmware/Makefile.mtk +++ b/src/target/firmware/Makefile.mtk @@ -4,14 +4,16 @@ BOARDS?=mt62xx # List of all applications (meant to be overridden on command line) APPLICATIONS?=loader_mtk -mtkram_LDS=board/mediatek/ram.lds -mtkram_OBJS=board/mediatek/start.ram.o +APP_loader_mtk_ENVIRONMENTS=mtkram + +ENV_mtkram_LDS=board/mediatek/ram.lds +ENV_mtkram_OBJS=board/mediatek/start.ram.o mtk_COMMON_OBJS=board/mediatek/uart.o # Mediatek MT62xx -mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o -mt62xx_ENVIRONMENTS=mtkram +BOARD_mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o +BOARD_mt62xx_ENVIRONMENTS=mtkram # Global include path INCLUDES=-Iinclude/ -I../../../include -I../../shared/libosmocore/include -- 2.15.0 From f12.sebastian at gmail.com Wed Dec 6 10:33:55 2017 From: f12.sebastian at gmail.com (f12.sebastian) Date: Wed, 6 Dec 2017 16:03:55 +0530 Subject: Classmark Testing Message-ID: Hi I am trying to test osmocom-bb/fixeria-Trx. After configuring test-sim the functions for receiver side like the " network selection mode " " select ARFCN" do work. But how to test or configure " Early Classmark Sending" for varying set of encryption (A5/1,2,3,4...). Regards. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From duarteetraud at gmail.com Wed Dec 6 10:45:50 2017 From: duarteetraud at gmail.com (Duarte) Date: Wed, 6 Dec 2017 10:45:50 +0000 Subject: Classmark Testing In-Reply-To: References: Message-ID: Hi, You can take a look at the mobile application patch here https://gitlab.com/francoip/thesis/blob/public/patch/thesis.patch which allows you to setup in the vty what is the type of encryption supported by the MS. Thank you. 2017-12-06 10:33 GMT+00:00 f12.sebastian : > Hi > > I am trying to test osmocom-bb/fixeria-Trx. > After configuring test-sim the functions for receiver side like the " > network selection mode " " select ARFCN" do work. > But how to test or configure " Early Classmark Sending" for varying set of > encryption (A5/1,2,3,4...). > > Regards. > > -- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Wed Dec 6 10:51:25 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Wed, 6 Dec 2017 17:51:25 +0700 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system Message-ID: Hi Craig, Could you please provide a bit more detailed description of the change you've sent: what was wrong and what this change is intended to fix, so I'll push it to gerrit. Thanks! With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuraev at sysmocom.de Wed Dec 6 10:53:26 2017 From: msuraev at sysmocom.de (Max) Date: Wed, 6 Dec 2017 11:53:26 +0100 Subject: Classmark Testing In-Reply-To: References: Message-ID: That looks interesting. Have you considered extracting encryption selection and silent sms parts and submitting it to gerrit for upstream merge? The process is described in https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit and should be rather straightforward. On 06.12.2017 11:45, Duarte wrote: > > You can take a look at the mobile application patch > here?https://gitlab.com/francoip/thesis/blob/public/patch/thesis.patch which allows > you to setup in the vty what is the type of encryption supported by the MS. -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From duarteetraud at gmail.com Wed Dec 6 10:59:57 2017 From: duarteetraud at gmail.com (Duarte) Date: Wed, 6 Dec 2017 10:59:57 +0000 Subject: Classmark Testing In-Reply-To: References: Message-ID: Hi Max, Sorry but I'm not the owner of the code, ref: https://brage.bibsys.no/xmlui/bitstream/handle/11250/2352780/13286_FULLTEXT.pdf I wouldn't feel good submitting other people's code. Cheers. 2017-12-06 10:53 GMT+00:00 Max : > That looks interesting. > > Have you considered extracting encryption selection and silent sms parts > and > submitting it to gerrit for upstream merge? > The process is described in > https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit and > should be rather > straightforward. > > On 06.12.2017 11:45, Duarte wrote: > > > > You can take a look at the mobile application patch > > here https://gitlab.com/francoip/thesis/blob/public/patch/thesis.patch > which allows > > you to setup in the vty what is the type of encryption supported by the > MS. > > -- > Max Suraev 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 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Wed Dec 6 11:03:23 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Wed, 6 Dec 2017 18:03:23 +0700 Subject: Classmark Testing Message-ID: Hi Max, This work is a part of "GSM and GPRS Security Using OsmocomBB" thesis written by Francois Ponsgen and was published a quite time ago. Moreover, I already have the changes in my local repo, which is mostly used for research purposes. I can push them, if it's really required. BTW: if I remember correctly, this work was done in NTNU ;) With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuraev at sysmocom.de Wed Dec 6 11:07:54 2017 From: msuraev at sysmocom.de (Max) Date: Wed, 6 Dec 2017 12:07:54 +0100 Subject: Classmark Testing In-Reply-To: References: Message-ID: <20b3b34b-6bf3-5e36-0074-76d4274fa54f@sysmocom.de> On 06.12.2017 12:03, Vadim Yanitskiy wrote: > This work is a part of "GSM and GPRS Security Using OsmocomBB" thesis > written by Francois Ponsgen and was published a quite time ago. Mixed up the author, sorry about that. > > Moreover, I already have the changes in my local repo, which is > mostly used for research purposes. I can push them, if it's really > required. It's not really required of course - just smth which would be nice to have in upstream since it's useful to the users. > > BTW: if I remember correctly, this work was done in NTNU ;) I know, read it quite some time ago :) -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From f12.sebastian at gmail.com Wed Dec 6 13:49:09 2017 From: f12.sebastian at gmail.com (Sebastian F) Date: Wed, 6 Dec 2017 19:19:09 +0530 Subject: Classmark Testing In-Reply-To: References: Message-ID: Hi I am able to set the encryption A5/1,2,3,4..... . My query is : my test network is supporting A5/1,2,3. Is it feasible to set A5/1 on MS1 (though it supports A5/2 and A5/3 also) and A5/2 for MS2 (though it supports A5/1 and A5/3 also) for a call in between them using "Early Classmark Sending" ??? Or even one side of it. And see the signalling taking place for this to happen !!! Regards. On Wed, Dec 6, 2017 at 4:15 PM, Duarte wrote: > Hi, > > You can take a look at the mobile application patch here > https://gitlab.com/francoip/thesis/blob/public/patch/thesis.patch which > allows you to setup in the vty what is the type of encryption supported by > the MS. > > Thank you. > > 2017-12-06 10:33 GMT+00:00 f12.sebastian : > >> Hi >> >> I am trying to test osmocom-bb/fixeria-Trx. >> After configuring test-sim the functions for receiver side like the " >> network selection mode " " select ARFCN" do work. >> But how to test or configure " Early Classmark Sending" for varying set >> of encryption (A5/1,2,3,4...). >> >> Regards. >> >> -- >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig at unreasonablefarm.org Wed Dec 6 14:31:50 2017 From: craig at unreasonablefarm.org (Craig Comstock) Date: Wed, 6 Dec 2017 08:31:50 -0600 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system In-Reply-To: References: Message-ID: <20171206143150.GA20145@localhost.localdomain> Sure Vadim, It seems the existing Makefile.mtk isn't compatible with the current makefile scheme so nothing would happen when it was called. I modified it to match better the other Makefile structure and now I can compile a loader_mtk.mtkram.bin file. Sadly the resulting binary doesn't yet work on the sciphone dream g2 hardware that I have. There are some compiler warnings that may need fixing or maybe the code needs more fundamental change after rotting a bit. My goal is to get back to the "last good state" for the schiphone dream g2 and then use that as a starting point for work with mtk6260 aka fernvale board and related devices. Thanks! Craig From axilirator at gmail.com Wed Dec 6 14:49:55 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Wed, 6 Dec 2017 21:49:55 +0700 Subject: Classmark Testing Message-ID: Hi Sebastian, > My query is : my test network is supporting A5/1,2,3. Is it feasible to > set A5/1 on MS1 (though it supports A5/2 and A5/3 also) and A5/2 for MS2 > (though it supports A5/1 and A5/3 also) for a call in between them using > "Early Classmark Sending" ??? I think it will work without any problems because the A5/X encryption is not 'end-to-end' (in our case MS-to-MS), but there are two separate encrypted sessions between MS1-BTS and MS2-BTS. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snehasish.cse at live.com Wed Dec 6 15:00:41 2017 From: snehasish.cse at live.com (Snehasish Kar) Date: Wed, 6 Dec 2017 15:00:41 +0000 Subject: Classmark Testing In-Reply-To: References: Message-ID: Hello everyone I have a doubt here from the DSP side, might be a silly one. While transmitting the classmark or any message from mobile on SDCCH during a call, does it transmit on the frequency we get after converting the ARFCN or is there a slight variation ? BR Snehasish ________________________________ From: baseband-devel on behalf of Vadim Yanitskiy Sent: Wednesday, December 6, 2017 8:19:55 PM To: f12.sebastian at gmail.com Cc: baseband-devel Subject: Re: Classmark Testing Hi Sebastian, > My query is : my test network is supporting A5/1,2,3. Is it feasible to > set A5/1 on MS1 (though it supports A5/2 and A5/3 also) and A5/2 for MS2 > (though it supports A5/1 and A5/3 also) for a call in between them using > "Early Classmark Sending" ??? I think it will work without any problems because the A5/X encryption is not 'end-to-end' (in our case MS-to-MS), but there are two separate encrypted sessions between MS1-BTS and MS2-BTS. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Wed Dec 6 16:30:23 2017 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 6 Dec 2017 17:30:23 +0100 Subject: OsmoDevCon 2018 schedule planning In-Reply-To: <20171204122347.GN14790@nataraja> References: <20171204122347.GN14790@nataraja> Message-ID: <20171206163023.GB19109@nataraja> Dear Osmocom Community, On Mon, Dec 04, 2017 at 01:23:47PM +0100, Harald Welte wrote: > == When, Who, Where == > > I propose the following date for OsmoDevCon 2018: > April 20 - April 23rd, 2018 > > * Who: Active developers/contributors of Osmocom projects (as usual) > * Where: IN-Berlin, Berlin (as usual) > > Please let me know ASAP if that proposed date works for everyone who'd > want to attend. We can still change it now, but I would want to nail > down the date pretty soon. > despite Holger indicating April would be difficult for him, I would still suggest to stay with the current proposed date: * nobody else has raised any concerns * several people have sent positive feedback * it's the usual time-frame as in previous years * IN-Berlin has already reserved that time slot without any conflict Sorry, Holger, I hope you will still be around as much as possible! Threfore, I hereby invite everyone interested to attend to register themselves in the usual fashion at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2018 i.e. by adding your name to the 'Requested' section. Please also start collecting topics on that same wiki page. And please do let me know if there is anything we can do to make the event better. Regards, Harald > == Format == > > After the experiment of reducing from 4 to 3 days last year (due to > OsmoCon), we will again go for *four days* in 2018. > > However, we should clearly divide the days in a way that e.g. "GSM/3G" > topics are on two days, while SDR+Other topics are on the other days, so > people not interested in some topics can skip one or two days, as > needed. Let's collect the suggested topics. I've added a "Thread" column to https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2018/edit?section=9 so we can see how many days / half-days we need for which thread. Regards, and looking forward to meeting you [again] in 2018, -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From felangga at gmail.com Wed Dec 6 17:41:55 2017 From: felangga at gmail.com (Felix Angga) Date: Thu, 7 Dec 2017 00:41:55 +0700 Subject: TX SUPPORT In-Reply-To: References: Message-ID: Hi, I already uncomment the tx support in Makefile file. But when I run on phone, it said this firmware was compiled without tx support. How to fix this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Wed Dec 6 18:13:19 2017 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 6 Dec 2017 19:13:19 +0100 Subject: TX SUPPORT In-Reply-To: References: Message-ID: <20171206181319.GA26582@nataraja> On Thu, Dec 07, 2017 at 12:41:55AM +0700, Felix Angga wrote: > Hi, > > I already uncomment the tx support in Makefile file. But when I run on > phone, it said this firmware was compiled without tx support. > > How to fix this? did you do "make clean"? Did you verify that you actually loaded the re-built file? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From felangga at gmail.com Wed Dec 6 18:21:07 2017 From: felangga at gmail.com (Felix Angga) Date: Thu, 7 Dec 2017 01:21:07 +0700 Subject: TX SUPPORT In-Reply-To: <20171206181319.GA26582@nataraja> References: <20171206181319.GA26582@nataraja> Message-ID: Resolved, I recloned the git and it work fine (y) Thanks On Dec 7, 2017 1:20 AM, "Harald Welte" wrote: > On Thu, Dec 07, 2017 at 12:41:55AM +0700, Felix Angga wrote: > > Hi, > > > > I already uncomment the tx support in Makefile file. But when I run on > > phone, it said this firmware was compiled without tx support. > > > > How to fix this? > > did you do "make clean"? Did you verify that you actually loaded the > re-built file? > > -- > - Harald Welte > http://laforge.gnumonks.org/ > ============================================================ > ================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig at unreasonablefarm.org Wed Dec 6 22:37:24 2017 From: craig at unreasonablefarm.org (Craig Comstock) Date: Wed, 6 Dec 2017 16:37:24 -0600 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system In-Reply-To: <20171206143150.GA20145@localhost.localdomain> References: <20171206143150.GA20145@localhost.localdomain> Message-ID: <20171206223724.GA6694@localhost.localdomain> Some good news, I played around with the device and the loader and found that things work "as they did" if I follow the instructions more carefully... press and hold the button UNTIL LOADING IS FINISHED! ;) It says it there but I didn't quite understand I had to hold it down the whole time. Anyhow... it works and gets to "Running on mt62xx in environment mtkram and HW_CODE = 0x6235" So I am back at square one with this small Makefile.mtk change and will proceed with experiments on bringing up sciphone and/or fernvale and friends. Thanks Craig From axilirator at gmail.com Thu Dec 7 01:25:12 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 7 Dec 2017 08:25:12 +0700 Subject: Classmark Testing Message-ID: Hi, > While transmitting the classmark or any message from mobile on > SDCCH during a call, does it transmit on the frequency we get > after converting the ARFCN or is there a slight variation ? I don't get this, what do you mean by 'converting the ARFCN'? There are two (as I know) possible types of call assignment: - Early Assignment, when the network allocates TCH/F or TCH/H right after getting RACH-request from a mobile phone. The frequency (or a set of them) is indicated in the Immediate Assignment message. - Late Assignment, when the network allocates an SDCCH channel first, where a mobile phone indicates a connection reason (Paging Response or Service Request) and also indicates the classmark. Then the network eventually sends the Assignment Command message, where just like in Immediate Assignment a new channel data (both FDMA and TDMA) are described. BTW: please choose a proper subject for this thread and don't interfere with the existing one because they are unrelated. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Dec 7 02:30:11 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 7 Dec 2017 09:30:11 +0700 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system In-Reply-To: <20171206223724.GA6694@localhost.localdomain> References: <20171206143150.GA20145@localhost.localdomain> <20171206223724.GA6694@localhost.localdomain> Message-ID: Hi Craig, > It seems the existing Makefile.mtk isn't compatible with the > current makefile scheme so nothing would happen when it was called. Your change is in Gerrit now: https://gerrit.osmocom.org/5217 > There are some compiler warnings that may need fixing or maybe the > code needs more fundamental change after rotting a bit. Sure, feel free to send new patches ;) > Some good news, I played around with the device and the loader and > found that things work "as they did" if I follow the instructions > more carefully... My congratulations! Could you please write a brief (or more detailed, if you wish) description of the work you're doing, so I could create a dedicated wiki page? Or is one already there? With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig at unreasonablefarm.org Thu Dec 7 02:39:02 2017 From: craig at unreasonablefarm.org (Craig Comstock) Date: Wed, 6 Dec 2017 20:39:02 -0600 Subject: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system In-Reply-To: References: <20171206143150.GA20145@localhost.localdomain> <20171206223724.GA6694@localhost.localdomain> Message-ID: <20171207023902.GA11707@localhost.localdomain> > My congratulations! Could you please write a brief (or more detailed, > if you wish) description of the work you're doing, so I could create > a dedicated wiki page? Or is one already there? https://osmocom.org/projects/baseband/wiki/SciphoneDreamG2 This wiki page would probably be good. It needs updating for sure since some of the git links for u-boot, linux kernel, initramfs image are dead. It seems they referred to git.osmocom.org projects which no longer exist. Not sure if those could be restored or not. I would be happy to make very small changes to that page. When I get something working on fernvale and others we could probably create a wiki page for mt6260 mt6261 fernvale and whatever others make sense. https://osmocom.org/projects/baseband/wiki/MT6235 Thanks, Craig From 07.shankar.ravi at gmail.com Thu Dec 7 06:01:22 2017 From: 07.shankar.ravi at gmail.com (Ravi Shankar) Date: Thu, 7 Dec 2017 11:31:22 +0530 Subject: Tx support in MS with a virtual SIM Message-ID: Hello Community Can we make usrp to behave like a normal MS with parameters of SIM in "test sim" feature from telnet. I am not using any real SIM or writer. As we pass the make command as " make nofirmware" from osmocombb/src directory after enabling the " CFLAGS += -DCONFIG_TX_ENABLE " in osmocom-bb/src/target/firmware, will it still be able to transmit ? -- Best Regards. Ravi -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Dec 7 06:20:55 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 7 Dec 2017 13:20:55 +0700 Subject: Tx support in MS with a virtual SIM Message-ID: Hi Ravi, > Can we make usrp to behave like a normal MS with parameters > of SIM in "test sim" feature from telnet. I am not using any > real SIM or writer. Yes, it's possible to use the virtual SIM-card, and this is exactly what we are doing during the SDR PHY development. Check out this example from FakeTRX: https://osmocom.org/projects/baseband/wiki/FakeTRX#Running-mobile-application > As we pass the make command as " make nofirmware" from osmocombb/src > directory after enabling the " CFLAGS += -DCONFIG_TX_ENABLE " in > osmocom-bb/src/target/firmware, will it still be able to transmit ? No need to change the 'CONFIG_TX_ENABLE'. This affects only the firmware for Calypso based hardware. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snehasish.cse at LIVE.COM Thu Dec 7 16:13:33 2017 From: snehasish.cse at LIVE.COM (Snehasish Kar) Date: Thu, 7 Dec 2017 16:13:33 +0000 Subject: help with burst_gen.py in faketrx Message-ID: Hello I tried using burst_gen.py with grgsmtrx, as I can see in the screen, it shows that it has sent the burst to to grgsm trx, but I dont see any transmission from grgsm trx. Please help. Below are the logs of both burst_send.py and grgsm trx. Please let me know where I am going wrong. burst_gen.py ~/Downgrader/osmocom-bb-fixeria-trx/src/target/fake_trx$ python burst_gen.py -b NB -p 5700 -m TRX Copyright (C) 2017 by Vadim Yanitskiy License GPLv2+: GNU GPL version 2 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. [i] Sending 1/1 NB burst (fn=1001550) to TRX... grgsm trx: ~/grgsmtrx_xenial/gr-gsm/apps$ sudo ./grgsm_trx Copyright (C) 2016-2017 by Vadim Yanitskiy License GPLv2+: GNU GPL version 2 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. [i] Init Radio interface [INFO] [UHDlinux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.git-215-g3b206caa] [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [INFO] [X300] X300 initialization sequence... [INFO] [X300] Connecting to niusrpriorpc at localhost:5444... [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [INFO] [X300] Using LVBITX bitfile /usr/local/share/uhd/images/usrp_x310_fpga_HG.lvbitx... [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [INFO] [X300] Setup basic communication... [INFO] [X300] Loading values from EEPROM... [INFO] [X300] Setup RF frontend clocking... [INFO] [X300] Radio 1x clock:200 [INFO] [RFNOC] [DMA FIFO] Running BIST for FIFO 0... [INFO] [DEBUG] [DMA FIFO] Clock rate for BIST calculation: 0 [INFO] [RFNOC] pass (Throughput: 0.0MB/s) [INFO] [RFNOC] [DMA FIFO] Running BIST for FIFO 1... [INFO] [DEBUG] [DMA FIFO] Clock rate for BIST calculation: 0 [INFO] [RFNOC] pass (Throughput: 0.0MB/s) [INFO] [RFNOC RADIO] Register loopback test passed [INFO] [RFNOC RADIO] Register loopback test passed [INFO] [RFNOC RADIO] Register loopback test passed [INFO] [RFNOC RADIO] Register loopback test passed [INFO] [CORES] Performing timer loopback test... [INFO] [CORES] Timer loopback test passed [INFO] [CORES] Performing timer loopback test... [INFO] [CORES] Timer loopback test passed [WARNING] [MULTI_USRP] The hardware does not support the requested RX sample rate: Target sample rate: 1.083333 MSps Actual sample rate: 1.086957 MSps [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [INFO] [NIRIO] rpc_client stopping... [INFO] [NIRIO] rpc_client stopped. [WARNING] [MULTI_USRP] The hardware does not support the requested TX sample rate: Target sample rate: 1.083333 MSps Actual sample rate: 1.086957 MSps [i] Init CTRL interface [i] Init complete BR Snehasish -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Wed Dec 13 18:57:11 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 14 Dec 2017 01:57:11 +0700 Subject: GSM 04.08 L2 pseudo length in ACCH System Information messages Message-ID: Hi everyone, I few days ago, during some usual R&D process, I noticed the following messages, appearing in the log output of OsmocomBB/mobile application: "ACCH message type 0xXX unknown." The network, a phone was connected to, was may own and based on more or less recent versions of OsmoNiTB, OsmoBTS, and OsmoTRX. Despite I used to see such messages before, I didn't pay too much attention. But this time I've decided to figure out, what's wrong there... The source of such messages is the gsm48_rr.c / gsm48_rr_rx_acch(): static int gsm48_rr_rx_acch(struct osmocom_ms *ms, struct msgb *msg) { // ... struct gsm48_system_information_type_header *sih = msgb_l3(msg); // ... switch (sih->system_information) { case GSM48_MT_RR_SYSINFO_5: return gsm48_rr_rx_sysinfo5(ms, msg); case GSM48_MT_RR_SYSINFO_5bis: return gsm48_rr_rx_sysinfo5bis(ms, msg); case GSM48_MT_RR_SYSINFO_5ter: return gsm48_rr_rx_sysinfo5ter(ms, msg); case GSM48_MT_RR_SYSINFO_6: return gsm48_rr_rx_sysinfo6(ms, msg); default: LOGP(DRR, LOGL_NOTICE, "ACCH message type 0x%02x unknown.\n", sih->system_information); return -EINVAL; } } To get I bit more details, I modified this function to print the whole L3 payload, and got some interesting results. As it turned out, the payloads were shifted one byte left - there was no 'l2_plen', which is assumed by: /* Section 9.1.3x System information Type header */ struct gsm48_system_information_type_header { uint8_t l2_plen; uint8_t rr_protocol_discriminator :4, skip_indicator:4; uint8_t system_information; } __attribute__ ((packed)); So, my first idea was that this is a bug of OsmocomBB, that would be fairly easy to fix, so after a quick look at the GSM 04.08 specification I wrote (and merged :/) this: https://gerrit.osmocom.org/#/c/5204/ And everything was great, until I connected a 'patched' mobile to a commercial mobile network... And all SI messages during a dedicated connection were false-identified as SI5ter. This seemed strange to me, so I decided to compare a SI message from commercial network with a message captured in my own one: https://habrastorage.org/webt/t8/zs/vv/t8zsvvjjglzfisnjqlnnsy4kgas.png And this confused me even more, then I've expected. Why there is 0x49? Wireshark false-identified this message as something related to SMS... What if this is exactly the 'l2_plen' assumed in OsmocomBB before? I looked at the specifications again, and found out that initially I refered an outdated 5.3.0 version, which was the first link in Google: http://www.etsi.org/deliver/etsi_gts/04/0408/05.03.00_60/gsmts_0408v050300p.pdf while the latest one is 7.21.0: http://www.etsi.org/deliver/etsi_ts/100900_100999/100940/07.21.00_60/ts_100940v072100p.pdf So, I compared the 9.1.37-40 sections of both versions, and bingo! In the higher version ACCH System Information messages do have the 'L2 Pseudo Length' (10.5.2.19) field. Finally, what I've learned: - OsmocomBB / mobile follows the new version here (with l2_plen); - OsmoNiTB generates the ACCH SI messages without the l2_plen; - Recent Wireshark versions fail to decode the ACCH SI messages with l2_plen, while older ones are able to do that; - I should not merge the changes so quick. My questions are: - Which way of composing the SI messages is correct? - If both are correct, how to parse them correctly? - Should we change OsmoNiTB / OsmoBSC to follow the latest specs? And of course, I have to revert the change I've merged. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marek.sebera at gmail.com Sun Dec 17 11:58:00 2017 From: marek.sebera at gmail.com (Marek Sebera) Date: Sun, 17 Dec 2017 12:58:00 +0100 Subject: Libre baseband In-Reply-To: References: Message-ID: Hello everyone, Silly idea maybe, but would it be possible to port osmocom-bb for mediatek/intel/qualcomm BBP and replace the current firmware with open one? I presume it will be a tremendous amount of work, no doubts, but apart from that, is it theoretically and technically possible? Given root and/or hardware acces of course, we do not need to preserve the old firmware or exploit the update process (ie. if specific cert signature is needed for bbp-soc firmware update) Note that we do not have to be limited by existing software access to baseband, and we could use jtag/testpoints/wiring to access the BBP in a way that will be necessary, similar to way libreboot is currently being flashed. Thank you Marek Sebera -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Sun Dec 17 12:33:20 2017 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 17 Dec 2017 13:33:20 +0100 Subject: Libre baseband In-Reply-To: References: Message-ID: <20171217123320.GQ17619@nataraja> Hi Marek! On Sun, Dec 17, 2017 at 12:58:00PM +0100, Marek Sebera wrote: > Silly idea maybe, but would it be possible to port osmocom-bb for > mediatek/intel/qualcomm BBP and replace the current firmware with open one? theoretically possible, yes. > I presume it will be a tremendous amount of work, no doubts, but apart from > that, is it theoretically and technically possible? Given root and/or > hardware acces of course, we do not need to preserve the old firmware or > exploit the update process (ie. if specific cert signature is needed for > bbp-soc firmware update) The biggest challenges, from my point of view, are: * using phones that don't use secure/authenticated boot for the BBP, or those where the certificates have leaked and/or exploits are known * finding significant enough amount of leaked sources or documentation and/or doing the reverse engineering required to understand how to talk to the DSP and/or related peripherals * finding the time to work on the protocol stack beyond classic 2G which is currently implemented in OsmocomBB. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From craig at unreasonablefarm.org Sun Dec 17 16:13:34 2017 From: craig at unreasonablefarm.org (craig at unreasonablefarm.org) Date: Sun, 17 Dec 2017 10:13:34 -0600 Subject: Libre baseband In-Reply-To: References: Message-ID: <20171217161334.GA13684@localhost> I am currently working on porting osmocom-bb to mtk6260/fernvale board available via open hardware and from sysmocom. My goal is to get a nuttx-bb + layer1 + mobile (osmocom-bb host software) working on fernvale and sim800h modules. I am also working on integrating the old mt6235 sciphone g2 code as well as look dforward to 3g/lte with mtk6735as in the ZTE Obsidian. I have some dreamy ideas about how to use fernly as a base for interactive creation and validation of board support and translate that into osmocom-bb firmware, nuttx application or library or even as a linux kernel driver or user space program (maybe in the ec20 qualcomm module case). I'm not very far along but will try and share as many small PRs as possible . I would encourage others to do the same. Cheers, Craig From craig at unreasonablefarm.org Sun Dec 17 16:17:41 2017 From: craig at unreasonablefarm.org (craig at unreasonablefarm.org) Date: Sun, 17 Dec 2017 10:17:41 -0600 Subject: Libre baseband In-Reply-To: <20171217123320.GQ17619@nataraja> References: <20171217123320.GQ17619@nataraja> Message-ID: <20171217161741.GA14232@localhost> > * finding significant enough amount of leaked sources or documentation > and/or doing the reverse engineering required to understand how to talk > to the DSP and/or related peripherals I have looked through leaked sources for mtk6260 and think there may be enough info tgere, but I lack deep gsm knowledge so maybe I am deceived. > * finding the time to work on the protocol stack beyond classic 2G which > is currently implemented in OsmocomBB. This is the work I intend to purse. Slowly I'm afraid. Craig From mawais.aslam985 at gmail.com Tue Dec 19 11:31:58 2017 From: mawais.aslam985 at gmail.com (Muhammad Awais Aslam) Date: Tue, 19 Dec 2017 16:31:58 +0500 Subject: Fwd: OSMOCOM-BB HandOver In-Reply-To: <02ad8a41-0952-91ca-4723-c924c6bdc635@sysmocom.de> References: <4B0B2FB7-BDA7-428F-B9DA-C0AE28F2C912@gnumonks.org> <02ad8a41-0952-91ca-4723-c924c6bdc635@sysmocom.de> Message-ID: Dear Max, Hi, Sorry for being so late for replying to this email. The person who was working with us on the handover code had left and we were not in the position to upload the code at that time. I have uploaded the code now on gerrit for review. I hope we would get some help to complete the handover implementation in osmocombb. Link to the uploaded code is: https://gerrit.osmocom.org/#/c/5490/ Regards M. Awais On Tue, Aug 15, 2017 at 4:40 PM, Max wrote: > Hi! > > Great to see you working on this. Is your current work-in-progress code > published > somewhere? That would make it easier for people to comment on it. > > Also, you can probably split out some patches/fixes and send them for > review to > gerrit already - see https://osmocom.org/projects/ > cellular-infrastructure/wiki/Gerrit > for details. > > -- > Max Suraev 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 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marek.sebera at gmail.com Thu Dec 21 08:48:17 2017 From: marek.sebera at gmail.com (Marek Sebera) Date: Thu, 21 Dec 2017 09:48:17 +0100 Subject: Libre baseband In-Reply-To: <20171217123320.GQ17619@nataraja> References: <20171217123320.GQ17619@nataraja> Message-ID: Hi Harald! * using phones that don't use secure/authenticated boot for the BBP, or those where the certificates have leaked and/or exploits are known <>> Do we currently have any candidates? Or list of potential candidates? Are ie. Nexus devices friendlier ? * finding the time to work on the protocol stack beyond classic 2G which is currently implemented in OsmocomBB. <>> Wild idea this might be, but do we need BBP with 2G stack ? Could we settle for LTE-only open BBP ? I'm thinking about doing some chip works and minimizing the software stack based on srsUE Cheers :) Marek On 12/17/2017 01:33 PM, Harald Welte wrote: > Hi Marek! > > On Sun, Dec 17, 2017 at 12:58:00PM +0100, Marek Sebera wrote: >> Silly idea maybe, but would it be possible to port osmocom-bb for >> mediatek/intel/qualcomm BBP and replace the current firmware with open one? > > theoretically possible, yes. > >> I presume it will be a tremendous amount of work, no doubts, but apart from >> that, is it theoretically and technically possible? Given root and/or >> hardware acces of course, we do not need to preserve the old firmware or >> exploit the update process (ie. if specific cert signature is needed for >> bbp-soc firmware update) > > The biggest challenges, from my point of view, are: > > * using phones that don't use secure/authenticated boot for the BBP, or > those where the certificates have leaked and/or exploits are known > * finding significant enough amount of leaked sources or documentation > and/or doing the reverse engineering required to understand how to talk > to the DSP and/or related peripherals > * finding the time to work on the protocol stack beyond classic 2G which > is currently implemented in OsmocomBB. > > Regards, > Harald > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 851 bytes Desc: OpenPGP digital signature URL: From marek.sebera at gmail.com Thu Dec 21 08:54:56 2017 From: marek.sebera at gmail.com (Marek Sebera) Date: Thu, 21 Dec 2017 09:54:56 +0100 Subject: Libre baseband In-Reply-To: <20171217161334.GA13684@localhost> References: <20171217161334.GA13684@localhost> Message-ID: <8515cd05-f03c-5db7-623c-7a5c49dcf8fc@gmail.com> Hello Craig! you're proper cool ! Do you anything of your works public already? is it possibly this? https://github.com/craigcomstock/osmocom-bb/tree/mt62xx https://osmocom.org/projects/cellular-infrastructure/wiki/Accelerate3g5_--_escogido I thought about MTK chipsets as good start-point for development, because they are less locked-down and there is bigger chance, they did not protect ie. the DSP codes enough. Also the dev-board (mtk6260/fernvale) what do you use specifically? Last thing, what I'm curious about, if Librem 5 (the phone) is willing to allocate some funds into BB(P) development and open-sourcing, because they sure want to open the software/firmware/hardware at some point, but so far I think, they rely more on BBP vendor to allow this, not so much opening it up / developing them-selves. Cheers Marek On 12/17/2017 05:13 PM, craig at unreasonablefarm.org wrote: > I am currently working on porting osmocom-bb to mtk6260/fernvale board available via open hardware and from sysmocom. My goal is to get a nuttx-bb + layer1 + mobile (osmocom-bb host software) working on fernvale and sim800h modules. > > I am also working on integrating the old mt6235 sciphone g2 code as well as look dforward to 3g/lte with mtk6735as in the ZTE Obsidian. > > I have some dreamy ideas about how to use fernly as a base for interactive creation and validation of board support and translate that into osmocom-bb firmware, nuttx application or library or even as a linux kernel driver or user space program (maybe in the ec20 qualcomm module case). > > I'm not very far along but will try and share as many small PRs as possible . I would encourage others to do the same. > > Cheers, > Craig > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 851 bytes Desc: OpenPGP digital signature URL: From craig at unreasonablefarm.org Thu Dec 21 12:30:46 2017 From: craig at unreasonablefarm.org (craig at unreasonablefarm.org) Date: Thu, 21 Dec 2017 06:30:46 -0600 Subject: Libre baseband In-Reply-To: <8515cd05-f03c-5db7-623c-7a5c49dcf8fc@gmail.com> References: <20171217161334.GA13684@localhost> <8515cd05-f03c-5db7-623c-7a5c49dcf8fc@gmail.com> Message-ID: <20171221123046.GA24783@localhost> I am currently making a fresh start. That branch is old and not much done. I will submit patches to baseband-devel as I make them. Right now I am working on porting fernly/fernvale-nuttx code to osmocom-bb in pursuit of making layer1 firmware. That is a very big project so would be happy for any help. I am focusing on the fernvale board for now. Cheers, Craig From xidianzhanghao at 126.com Mon Dec 25 02:56:42 2017 From: xidianzhanghao at 126.com (=?UTF-8?B?6KW/55S1X1/lvKDnmpM=?=) Date: Mon, 25 Dec 2017 02:56:42 -0000 Subject: Use osmocombb and openbsc to do man-in-the-middle attacks Message-ID: <787f4414.11f8.1608b99c5c0.Coremail.xidianzhanghao@126.com> Hello, I would like to use openbsc to do a fake base station and osmocombb to do an attack cell phone, to implement a man-in-the-middle attack. I have two questions: 1. How do I send location updates and authentication information between openbsc and osmocombb, 2. How to use imsi to initiate a location update thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: