From zero-kelvin at gmx.de Wed Jun 5 09:10:47 2013 From: zero-kelvin at gmx.de (dexter) Date: Wed, 05 Jun 2013 11:10:47 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <51AF0097.10402@gmx.de> Hi folks. My time is very limited at the moment and i can observe a decreasing interest in the Osmocom Berlin meetings so i will no longer organize meetings in the future. The main problem is that somebody must be there to open the door and let you in. If somebody else wants to organize future meetings it has to be someone with a key to the CCCB location. Regards, Philipp Maier From laforge at gnumonks.org Wed Jun 5 12:14:28 2013 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 5 Jun 2013 14:14:28 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <51AF0097.10402@gmx.de> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> Message-ID: <20130605121428.GA10030@nataraja.gnumonks.org> Hi Dexter, On Wed, Jun 05, 2013 at 11:10:47AM +0200, dexter wrote: > My time is very limited at the moment and i can observe a decreasing > interest in the Osmocom Berlin meetings so i will no longer organize > meetings in the future. I'm sorry to hear this. Regarding the decreasing interest: Maybe we should go back one step and look at a monthly rather than bi-weekly schedule? > The main problem is that somebody must be there to open the door and > let you in. If somebody else wants to organize future meetings it > has to be someone with a key to the CCCB location. [which is available to every CCCB member, like Peter, Holger, dexter, myself] 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 zero-kelvin at gmx.de Wed Jun 5 15:54:48 2013 From: zero-kelvin at gmx.de (dexter) Date: Wed, 05 Jun 2013 17:54:48 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <20130605121428.GA10030@nataraja.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> <20130605121428.GA10030@nataraja.gnumonks.org> Message-ID: <51AF5F48.1050304@gmx.de> Hi All. > I'm sorry to hear this. Regarding the decreasing interest: Maybe we > should go back one step and look at a monthly rather than bi-weekly > schedule? Sounds like a good idea. If enough people would be interested in a meeting i would continue doing it but maybe there is no more a need for a regular meeting i don't know... Maybe we should do a survey now. All ones who are interested in a monthly meeting (lets say every last Wednesday) should write an email (+1). > > [which is available to every CCCB member, like Peter, Holger, dexter, > myself] Sure, but the CCCB is not so much frequented at the moment. You have to be lucky to meet others when you come on another day than tuesday or thursday. regards. Philipp From ml at mail.tsaitgaist.info Tue Jun 11 15:31:40 2013 From: ml at mail.tsaitgaist.info (Kevin Redon) Date: Tue, 11 Jun 2013 08:31:40 -0700 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <51AF5F48.1050304@gmx.de> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> <20130605121428.GA10030@nataraja.gnumonks.org> <51AF5F48.1050304@gmx.de> Message-ID: <1370964691-sup-9608@dennou> +1 Excerpts from dexter's message of 2013-06-05 08:54:48 -0700: > Hi All. > > > I'm sorry to hear this. Regarding the decreasing interest: Maybe we > > should go back one step and look at a monthly rather than bi-weekly > > schedule? > Sounds like a good idea. If enough people would be interested in a meeting > i would continue doing it but maybe there is no more a need for a regular > meeting i don't know... > > Maybe we should do a survey now. All ones who are interested in a monthly > meeting (lets say every last Wednesday) should write an email (+1). > > > > > [which is available to every CCCB member, like Peter, Holger, dexter, > > myself] > Sure, but the CCCB is not so much frequented at the moment. You have to > be lucky to meet others when you come on another day than tuesday or > thursday. > > regards. > Philipp From osmocom at ngolde.de Tue Jun 18 15:59:40 2013 From: osmocom at ngolde.de (Nico Golde) Date: Tue, 18 Jun 2013 17:59:40 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <1370964691-sup-9608@dennou> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> <20130605121428.GA10030@nataraja.gnumonks.org> <51AF5F48.1050304@gmx.de> <1370964691-sup-9608@dennou> Message-ID: <20130618155940.GJ26707@ngolde.de> Hi, * Kevin Redon [2013-06-11 17:51]: > +1 > > Excerpts from dexter's message of 2013-06-05 08:54:48 -0700: > > Hi All. > > > > > I'm sorry to hear this. Regarding the decreasing interest: Maybe we > > > should go back one step and look at a monthly rather than bi-weekly > > > schedule? > > Sounds like a good idea. If enough people would be interested in a meeting > > i would continue doing it but maybe there is no more a need for a regular > > meeting i don't know... > > > > Maybe we should do a survey now. All ones who are interested in a monthly > > meeting (lets say every last Wednesday) should write an email (+1). I guess I was busy for quite some time traveling etc. Anyway, +1! Cheers Nico -- Nico Golde - XMPP: nion at jabber.ccc.de - GPG: 0xA0A0AAAA From Max.Suraev at fairwaves.ru Tue Jun 11 16:39:21 2013 From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=) Date: Tue, 11 Jun 2013 18:39:21 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <51AF5F48.1050304@gmx.de> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> <20130605121428.GA10030@nataraja.gnumonks.org> <51AF5F48.1050304@gmx.de> Message-ID: <51B752B9.5020606@fairwaves.ru> 05.06.2013 17:54, dexter ?????: > a good idea. If enough people would be interested in a meeting > i would continue doing it but maybe there is no more a need for a regular > meeting i don't know... > > Maybe we should do a survey now. All ones who are interested in a monthly > meeting (lets say every last Wednesday) should write an email (+1). I'd love to come to regular meetings too - be it monthly, weekly or whatever so +1 too. -- best regards, Max, http://fairwaves.ru From khorben at defora.org Sat Jun 15 10:38:17 2013 From: khorben at defora.org (Pierre Pronchery) Date: Sat, 15 Jun 2013 12:38:17 +0200 Subject: Osmocom Berlin User Group meeting -- discontinued In-Reply-To: <51AF5F48.1050304@gmx.de> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <51AF0097.10402@gmx.de> <20130605121428.GA10030@nataraja.gnumonks.org> <51AF5F48.1050304@gmx.de> Message-ID: <51BC4419.2010409@defora.org> On 05/06/2013 17:54, dexter wrote: > >> I'm sorry to hear this. Regarding the decreasing interest: Maybe we >> should go back one step and look at a monthly rather than bi-weekly >> schedule? > Sounds like a good idea. If enough people would be interested in a meeting > i would continue doing it but maybe there is no more a need for a regular > meeting i don't know... > > Maybe we should do a survey now. All ones who are interested in a monthly > meeting (lets say every last Wednesday) should write an email (+1). I should be able to join from time to time but never on Wednesdays, where I already have something else every week :/ Cheers, -- khorben From zero-kelvin at gmx.de Tue Jun 11 06:48:36 2013 From: zero-kelvin at gmx.de (dexter) Date: Tue, 11 Jun 2013 08:48:36 +0200 Subject: Osmocom Berlin User Group meeting -- still interest? In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <51B6C844.3050007@gmx.de> Hi folks. I am willing to take care of a meeting every end of the month. Please set me a private email that contains a "+1" if you are still interested in a regular meeting. Regards, Philipp Maier From akibsayyed at gmail.com Sun Jun 2 15:48:00 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Sun, 2 Jun 2013 21:18:00 +0530 Subject: sim reading hanged Message-ID: while running mobile app. mobile app stuck giving following output <000f> sim.c:151 sending result to callback function (type=0) <0005> subscriber.c:379 received KEY from SIM <0005> subscriber.c:601 Requesting SIM file 0x6f30 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:241 SELECT (file=0x6f30) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000f> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f) <000f> sim.c:949 command successfull <000f> sim.c:571 GET RESPONSE (len=15) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000f> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00) <000f> sim.c:949 command successfull <000f> sim.c:1065 selected file (len 249) <000f> sim.c:277 READ BINARY (offset=0 len=249) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xb0) output of layer1 is SIM Response (17): 00 00 00 0b 6f 7e 04 00 11 ff 1b 21 02 00 00 90 00 LOST 1923! LOST 1827! SIM Request (5): a0 b0 00 00 0b SIM Response (13): ff ff ff ff ff ff ff 00 00 ff 01 90 00 SIM Request (7): a0 a4 00 00 02 6f 20 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1878! LOST 1873! SIM Response (17): 00 00 00 09 6f 20 04 00 11 ff bb 01 02 00 00 90 00 SIM Request (5): a0 b0 00 00 09 SIM Response (11): ff ff ff ff ff ff ff ff 07 90 00 SIM Request (7): a0 a4 00 00 02 6f 30 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1880! LOST 1870! SIM Response (17): 00 00 00 f9 6f 30 04 00 11 ff bb 21 02 00 00 90 00 SIM Request (5): a0 b0 00 00 f9 LOST 1880! LOST 1870! Please help me solve this issue -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gandguladze at hotmail.com Tue Jun 4 17:40:35 2013 From: gandguladze at hotmail.com (George Andguladze) Date: Tue, 4 Jun 2013 17:40:35 +0000 Subject: Cannot open serial device /dev/ttyUSB0 Message-ID: Cannot open serial device /dev/ttyUSB0 I am getting this error message when I try to connect to my C155 phone and upload hello_world.compalram.bin using this command: ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/hello_world.compalram.bin Even though device ttyUSB0 exists in my /dev/ directory, and I have set modprobe cp210x, and chmod 777 /dev/ttyUSB0. Here is an output from dmesg: [ 105.110818] usb 6-3: USB disconnect, device number 2 [ 105.111098] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 105.111131] cp210x 6-3:1.0: device disconnected [ 113.728075] usb 6-3: new full speed USB device number 3 using ohci_hcd [ 113.901042] cp210x 6-3:1.0: cp210x converter detected [ 114.040085] usb 6-3: reset full speed USB device number 3 using ohci_hcd [ 114.206030] usb 6-3: cp210x converter now attached to ttyUSB0 Here is an output from ls -l /dev/tty : crw-rw-rw- 1 root tty 5, 0 2013-06-04 21:27 /dev/tty crw--w---- 1 root tty 4, 0 2013-06-04 20:40 /dev/tty0 crw------- 1 root root 4, 1 2013-06-04 20:40 /dev/tty1 crw--w---- 1 root tty 4, 10 2013-06-04 20:40 /dev/tty10 crw--w---- 1 root tty 4, 11 2013-06-04 20:40 /dev/tty11 crw--w---- 1 root tty 4, 12 2013-06-04 20:40 /dev/tty12 crw--w---- 1 root tty 4, 13 2013-06-04 20:40 /dev/tty13 crw--w---- 1 root tty 4, 14 2013-06-04 20:40 /dev/tty14 crw--w---- 1 root tty 4, 15 2013-06-04 20:40 /dev/tty15 crw--w---- 1 root tty 4, 16 2013-06-04 20:40 /dev/tty16 crw--w---- 1 root tty 4, 17 2013-06-04 20:40 /dev/tty17 crw--w---- 1 root tty 4, 18 2013-06-04 20:40 /dev/tty18 crw--w---- 1 root tty 4, 19 2013-06-04 20:40 /dev/tty19 crw------- 1 root root 4, 2 2013-06-04 20:40 /dev/tty2 crw--w---- 1 root tty 4, 20 2013-06-04 20:40 /dev/tty20 crw--w---- 1 root tty 4, 21 2013-06-04 20:40 /dev/tty21 crw--w---- 1 root tty 4, 22 2013-06-04 20:40 /dev/tty22 crw--w---- 1 root tty 4, 23 2013-06-04 20:40 /dev/tty23 crw--w---- 1 root tty 4, 24 2013-06-04 20:40 /dev/tty24 crw--w---- 1 root tty 4, 25 2013-06-04 20:40 /dev/tty25 crw--w---- 1 root tty 4, 26 2013-06-04 20:40 /dev/tty26 crw--w---- 1 root tty 4, 27 2013-06-04 20:40 /dev/tty27 crw--w---- 1 root tty 4, 28 2013-06-04 20:40 /dev/tty28 crw--w---- 1 root tty 4, 29 2013-06-04 20:40 /dev/tty29 crw------- 1 root root 4, 3 2013-06-04 20:40 /dev/tty3 crw--w---- 1 root tty 4, 30 2013-06-04 20:40 /dev/tty30 crw--w---- 1 root tty 4, 31 2013-06-04 20:40 /dev/tty31 crw--w---- 1 root tty 4, 32 2013-06-04 20:40 /dev/tty32 crw--w---- 1 root tty 4, 33 2013-06-04 20:40 /dev/tty33 crw--w---- 1 root tty 4, 34 2013-06-04 20:40 /dev/tty34 crw--w---- 1 root tty 4, 35 2013-06-04 20:40 /dev/tty35 crw--w---- 1 root tty 4, 36 2013-06-04 20:40 /dev/tty36 crw--w---- 1 root tty 4, 37 2013-06-04 20:40 /dev/tty37 crw--w---- 1 root tty 4, 38 2013-06-04 20:40 /dev/tty38 crw--w---- 1 root tty 4, 39 2013-06-04 20:40 /dev/tty39 crw------- 1 root root 4, 4 2013-06-04 20:40 /dev/tty4 crw--w---- 1 root tty 4, 40 2013-06-04 20:40 /dev/tty40 crw--w---- 1 root tty 4, 41 2013-06-04 20:40 /dev/tty41 crw--w---- 1 root tty 4, 42 2013-06-04 20:40 /dev/tty42 crw--w---- 1 root tty 4, 43 2013-06-04 20:40 /dev/tty43 crw--w---- 1 root tty 4, 44 2013-06-04 20:40 /dev/tty44 crw--w---- 1 root tty 4, 45 2013-06-04 20:40 /dev/tty45 crw--w---- 1 root tty 4, 46 2013-06-04 20:40 /dev/tty46 crw--w---- 1 root tty 4, 47 2013-06-04 20:40 /dev/tty47 crw--w---- 1 root tty 4, 48 2013-06-04 20:40 /dev/tty48 crw--w---- 1 root tty 4, 49 2013-06-04 20:40 /dev/tty49 crw------- 1 root root 4, 5 2013-06-04 20:40 /dev/tty5 crw--w---- 1 root tty 4, 50 2013-06-04 20:40 /dev/tty50 crw--w---- 1 root tty 4, 51 2013-06-04 20:40 /dev/tty51 crw--w---- 1 root tty 4, 52 2013-06-04 20:40 /dev/tty52 crw--w---- 1 root tty 4, 53 2013-06-04 20:40 /dev/tty53 crw--w---- 1 root tty 4, 54 2013-06-04 20:40 /dev/tty54 crw--w---- 1 root tty 4, 55 2013-06-04 20:40 /dev/tty55 crw--w---- 1 root tty 4, 56 2013-06-04 20:40 /dev/tty56 crw--w---- 1 root tty 4, 57 2013-06-04 20:40 /dev/tty57 crw--w---- 1 root tty 4, 58 2013-06-04 20:40 /dev/tty58 crw--w---- 1 root tty 4, 59 2013-06-04 20:40 /dev/tty59 crw------- 1 root root 4, 6 2013-06-04 20:40 /dev/tty6 crw--w---- 1 root tty 4, 60 2013-06-04 20:40 /dev/tty60 crw--w---- 1 root tty 4, 61 2013-06-04 20:40 /dev/tty61 crw--w---- 1 root tty 4, 62 2013-06-04 20:40 /dev/tty62 crw--w---- 1 root tty 4, 63 2013-06-04 20:40 /dev/tty63 crw--w---- 1 root tty 4, 7 2013-06-04 20:40 /dev/tty7 crw--w---- 1 root tty 4, 8 2013-06-04 20:40 /dev/tty8 crw--w---- 1 root tty 4, 9 2013-06-04 20:40 /dev/tty9 crw------- 1 root root 5, 3 2013-06-04 20:40 /dev/ttyprintk crw-rw---- 1 root dialout 4, 64 2013-06-04 20:40 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 2013-06-04 20:40 /dev/ttyS1 crw-rw---- 1 root dialout 4, 74 2013-06-04 20:40 /dev/ttyS10 crw-rw---- 1 root dialout 4, 75 2013-06-04 20:40 /dev/ttyS11 crw-rw---- 1 root dialout 4, 76 2013-06-04 20:40 /dev/ttyS12 crw-rw---- 1 root dialout 4, 77 2013-06-04 20:40 /dev/ttyS13 crw-rw---- 1 root dialout 4, 78 2013-06-04 20:40 /dev/ttyS14 crw-rw---- 1 root dialout 4, 79 2013-06-04 20:40 /dev/ttyS15 crw-rw---- 1 root dialout 4, 80 2013-06-04 20:40 /dev/ttyS16 crw-rw---- 1 root dialout 4, 81 2013-06-04 20:40 /dev/ttyS17 crw-rw---- 1 root dialout 4, 82 2013-06-04 20:40 /dev/ttyS18 crw-rw---- 1 root dialout 4, 83 2013-06-04 20:40 /dev/ttyS19 crw-rw---- 1 root dialout 4, 66 2013-06-04 20:40 /dev/ttyS2 crw-rw---- 1 root dialout 4, 84 2013-06-04 20:40 /dev/ttyS20 crw-rw---- 1 root dialout 4, 85 2013-06-04 20:40 /dev/ttyS21 crw-rw---- 1 root dialout 4, 86 2013-06-04 20:40 /dev/ttyS22 crw-rw---- 1 root dialout 4, 87 2013-06-04 20:40 /dev/ttyS23 crw-rw---- 1 root dialout 4, 88 2013-06-04 20:40 /dev/ttyS24 crw-rw---- 1 root dialout 4, 89 2013-06-04 20:40 /dev/ttyS25 crw-rw---- 1 root dialout 4, 90 2013-06-04 20:40 /dev/ttyS26 crw-rw---- 1 root dialout 4, 91 2013-06-04 20:40 /dev/ttyS27 crw-rw---- 1 root dialout 4, 92 2013-06-04 20:40 /dev/ttyS28 crw-rw---- 1 root dialout 4, 93 2013-06-04 20:40 /dev/ttyS29 crw-rw---- 1 root dialout 4, 67 2013-06-04 20:40 /dev/ttyS3 crw-rw---- 1 root dialout 4, 94 2013-06-04 20:40 /dev/ttyS30 crw-rw---- 1 root dialout 4, 95 2013-06-04 20:40 /dev/ttyS31 crw-rw---- 1 root dialout 4, 68 2013-06-04 20:40 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 2013-06-04 20:40 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 2013-06-04 20:40 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 2013-06-04 20:40 /dev/ttyS7 crw-rw---- 1 root dialout 4, 72 2013-06-04 20:40 /dev/ttyS8 crw-rw---- 1 root dialout 4, 73 2013-06-04 20:40 /dev/ttyS9 crwxrwxrwx 1 root dialout 188, 0 2013-06-04 21:07 /dev/ttyUSB0 What is it that I am doing wrong? Thanks, George -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mail.tsaitgaist.info Tue Jun 4 18:29:13 2013 From: ml at mail.tsaitgaist.info (Kevin Redon) Date: Tue, 04 Jun 2013 11:29:13 -0700 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: Message-ID: <1370370139-sup-5708@dennou> Excerpts from George Andguladze's message of 2013-06-04 10:40:35 -0700: > Cannot open serial device /dev/ttyUSB0 > > I am getting this error message when I try to connect to my C155 phone and upload hello_world.compalram.bin using this command: > > ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/hello_world.compalram.bin > > Even though device ttyUSB0 exists in my /dev/ directory, and I have set modprobe cp210x, and chmod 777 /dev/ttyUSB0. instead of setting 777 permissions on this device, you can simply add yourself to the dialout group (it's the more proper way) here the debian command (don't forget to log out and in again for this to take effect) sudo adduser $USER dialout > crw-rw---- 1 root dialout 4, 71 2013-06-04 20:40 /dev/ttyS7 > crw-rw---- 1 root dialout 4, 72 2013-06-04 20:40 /dev/ttyS8 > crw-rw---- 1 root dialout 4, 73 2013-06-04 20:40 /dev/ttyS9 > crwxrwxrwx 1 root dialout 188, 0 2013-06-04 21:07 /dev/ttyUSB0 > > > What is it that I am doing wrong? does it work with root rights (using sudo)? kevin From gandguladze at hotmail.com Tue Jun 4 19:09:12 2013 From: gandguladze at hotmail.com (George Andguladze) Date: Tue, 4 Jun 2013 19:09:12 +0000 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: , <1370370139-sup-5708@dennou>, Message-ID: No it doesn't. > From: ml at mail.tsaitgaist.info > To: baseband-devel at lists.osmocom.org > Subject: Re: Cannot open serial device /dev/ttyUSB0 > Date: Tue, 4 Jun 2013 11:29:13 -0700 > > Excerpts from George Andguladze's message of 2013-06-04 10:40:35 -0700: > > Cannot open serial device /dev/ttyUSB0 > > > > I am getting this error message when I try to connect to my C155 phone and upload hello_world.compalram.bin using this command: > > > > ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/hello_world.compalram.bin > > > > Even though device ttyUSB0 exists in my /dev/ directory, and I have set modprobe cp210x, and chmod 777 /dev/ttyUSB0. > > instead of setting 777 permissions on this device, you can simply add yourself to the dialout group (it's the more proper way) > here the debian command (don't forget to log out and in again for this to take effect) > sudo adduser $USER dialout > > > crw-rw---- 1 root dialout 4, 71 2013-06-04 20:40 /dev/ttyS7 > > crw-rw---- 1 root dialout 4, 72 2013-06-04 20:40 /dev/ttyS8 > > crw-rw---- 1 root dialout 4, 73 2013-06-04 20:40 /dev/ttyS9 > > crwxrwxrwx 1 root dialout 188, 0 2013-06-04 21:07 /dev/ttyUSB0 > > > > > > What is it that I am doing wrong? > > does it work with root rights (using sudo)? > > kevin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at steve-m.de Wed Jun 5 18:19:57 2013 From: steve at steve-m.de (Steve Markgraf) Date: Wed, 05 Jun 2013 20:19:57 +0200 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: Message-ID: <51AF814D.4040908@steve-m.de> Hi, On 04.06.2013 19:40, George Andguladze wrote: > Cannot open serial device /dev/ttyUSB0 > What is it that I am doing wrong? If you're using a recent version of Ubuntu/Debian, modem-manager opens serial devices when connected and probes for a modem. Also, on older versions of Ubuntu brltty might block the port. To work around the modem-manager issue either uninstall it, or put a udev blacklist rule in place (where you insert the VID/PID of your adapter): http://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/77-mm-usb-device-blacklist.rules Regards, Steve From gandguladze at hotmail.com Tue Jun 11 08:07:19 2013 From: gandguladze at hotmail.com (George Andguladze) Date: Tue, 11 Jun 2013 08:07:19 +0000 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: <51AF814D.4040908@steve-m.de> References: , <51AF814D.4040908@steve-m.de> Message-ID: Hi Steve, Thanks for help, but ModemManager doesn't seem to be an issue. Question: Does "Cannot open serial device /dev/ttyUSB0" error mean that it is unable to connect to my USB adapter or that there might not be a phone connected on the other end of the adapter? George > Date: Wed, 5 Jun 2013 20:19:57 +0200 > From: steve at steve-m.de > To: gandguladze at hotmail.com > Subject: Re: Cannot open serial device /dev/ttyUSB0 > CC: baseband-devel at lists.osmocom.org > > Hi, > > On 04.06.2013 19:40, George Andguladze wrote: > > Cannot open serial device /dev/ttyUSB0 > > What is it that I am doing wrong? > > If you're using a recent version of Ubuntu/Debian, modem-manager opens > serial devices when connected and probes for a modem. > Also, on older versions of Ubuntu brltty might block the port. > > To work around the modem-manager issue either uninstall it, or put a > udev blacklist rule in place (where you insert the VID/PID of your > adapter): > > http://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/77-mm-usb-device-blacklist.rules > > Regards, > Steve > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Jun 11 08:39:16 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 11 Jun 2013 10:39:16 +0200 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: <51AF814D.4040908@steve-m.de> Message-ID: Hi, > Thanks for help, but ModemManager doesn't seem to be an issue. Question: > Does "Cannot open serial device /dev/ttyUSB0" error mean that > it is unable to connect to my USB adapter or that there might not be a phone > connected on the other end of the adapter? It means it can't open the char device ... basically the call to open("/dev/ttyUSB0") failed somehow. nothing to do with the phone. Cheers, Sylvain From gandguladze at hotmail.com Tue Jun 11 08:44:20 2013 From: gandguladze at hotmail.com (George Andguladze) Date: Tue, 11 Jun 2013 08:44:20 +0000 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: , <51AF814D.4040908@steve-m.de>, , Message-ID: I can read/write baud rates to EEPROM of the device using cp210x-program. Basically I have tried everything apart from reinstalling the OS (Ubuntu 10.04). What might be the issue? (for more info refer to the older conversations) > Date: Tue, 11 Jun 2013 10:39:16 +0200 > Subject: Re: Cannot open serial device /dev/ttyUSB0 > From: 246tnt at gmail.com > To: gandguladze at hotmail.com > CC: steve at steve-m.de; baseband-devel at lists.osmocom.org > > Hi, > > > Thanks for help, but ModemManager doesn't seem to be an issue. Question: > > Does "Cannot open serial device /dev/ttyUSB0" error mean that > > it is unable to connect to my USB adapter or that there might not be a phone > > connected on the other end of the adapter? > > It means it can't open the char device ... basically the call to > open("/dev/ttyUSB0") failed somehow. nothing to do with the phone. > > Cheers, > > Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Jun 11 09:21:23 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 11 Jun 2013 11:21:23 +0200 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: <51AF814D.4040908@steve-m.de> Message-ID: On Tue, Jun 11, 2013 at 10:44 AM, George Andguladze wrote: > I can read/write baud rates to EEPROM of the device using cp210x-program. > Basically I have tried everything apart from reinstalling the OS (Ubuntu > 10.04). What might be the issue? (for more info refer to the older > conversations) Try to strace it. strace osmocon .... Cheers, Sylvain From gandguladze at hotmail.com Tue Jun 11 10:27:11 2013 From: gandguladze at hotmail.com (George Andguladze) Date: Tue, 11 Jun 2013 10:27:11 +0000 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: , <51AF814D.4040908@steve-m.de>, , , , Message-ID: Hi Sylvain, thanks for that, already getting somewhere. Here are last several lines from strace output: open("/dev/ttyUSB0", O_RDWR|O_NOCTTY) = 3 14:21:07.712932 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B115200 opost isig icanon echo ...}) = 0 14:21:07.713657 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B115200 opost isig icanon echo ...}) = 0 14:21:07.713847 ioctl(3, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0 14:21:07.715039 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0 14:21:07.715261 ioctl(3, TIOCMBIS, [TIOCM_DTR|TIOCM_RTS]) = -1 EPIPE (Broken pipe) 14:21:07.717054 close(3) = 0 14:21:07.720986 write(2, "Cannot open serial device /dev/t"..., 39Cannot open serial device /dev/ttyUSB0 I got -1 at ioctl(3, TIOCMBIS, [TIOCM_DTR|TIOCM_RTS]) (Broken pipe). But it was actually able to open "/dev/ttyUSB0" (returned 3). Have to find out what -1 means at this point. > Date: Tue, 11 Jun 2013 11:21:23 +0200 > Subject: Re: Cannot open serial device /dev/ttyUSB0 > From: 246tnt at gmail.com > To: gandguladze at hotmail.com > CC: baseband-devel at lists.osmocom.org > > On Tue, Jun 11, 2013 at 10:44 AM, George Andguladze > wrote: > > I can read/write baud rates to EEPROM of the device using cp210x-program. > > Basically I have tried everything apart from reinstalling the OS (Ubuntu > > 10.04). What might be the issue? (for more info refer to the older > > conversations) > > Try to strace it. > > strace osmocon .... > > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter at stuge.se Tue Jun 11 10:53:58 2013 From: peter at stuge.se (Peter Stuge) Date: Tue, 11 Jun 2013 12:53:58 +0200 Subject: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: Message-ID: <20130611105358.25916.qmail@stuge.se> George Andguladze wrote: > 14:21:07.715261 ioctl(3, TIOCMBIS, [TIOCM_DTR|TIOCM_RTS]) = -1 EPIPE (Broken pipe) This is what you get for using a three year old kernel. Get a modern kernel, I'm sure the problem will go away. //Peter From edachleger at yahoo.com Tue Jun 11 09:27:19 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Tue, 11 Jun 2013 10:27:19 +0100 (BST) Subject: Vedr: Cannot open serial device /dev/ttyUSB0 In-Reply-To: References: , <51AF814D.4040908@steve-m.de>, , Message-ID: <1370942839.242.YahooMailNeo@web171202.mail.ir2.yahoo.com> ________________________________ I had some problems with similar error message,they occurred when I wanted to restart osmocom-apps after having removed phone with its usb cable from pc and then reinserting phone and usb-cable. But when I just remove the phone from the usb-cable and then reconnect phone to the cable the "Cannot open serial device /dev/ttyUSB0" messages no longer occur and one can then rerun the osmocom-apps without error messages. Regards Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From akibsayyed at gmail.com Thu Jun 6 11:48:02 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Thu, 6 Jun 2013 17:18:02 +0530 Subject: TOA in burst_ind Message-ID: Hi Sylvain I wanted to know unit for TOA means, is it in miliseconds,nanoseconds etc. help is appreciated -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Thu Jun 6 12:08:51 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 6 Jun 2013 14:08:51 +0200 Subject: TOA in burst_ind In-Reply-To: References: Message-ID: > I wanted to know unit for TOA means, is it in miliseconds,nanoseconds etc. In symbols. Or quarter-symbol depend where. Usually can be deduced by looked where the value is used. Cheers, Sylvain From akibsayyed at gmail.com Thu Jun 6 13:49:30 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Thu, 6 Jun 2013 19:19:30 +0530 Subject: TOA in burst_ind In-Reply-To: References: Message-ID: I am sorry for direct reply. I am refering to toa in burst ind How can we convert them to sec. I am willing to develop u-tdoa with osmocom. Will this value help me in u-tdoa sent from android On Jun 6, 2013 5:43 PM, "Sylvain Munaut" <246tnt at gmail.com> wrote: > > I wanted to know unit for TOA means, is it in miliseconds,nanoseconds > etc. > > In symbols. Or quarter-symbol depend where. Usually can be deduced by > looked where the value is used. > > Cheers, > > Sylvain > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Max.Suraev at fairwaves.ru Mon Jun 10 16:33:46 2013 From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=) Date: Mon, 10 Jun 2013 18:33:46 +0200 Subject: umts rrc question Message-ID: <51B5FFEA.3060704@fairwaves.ru> Hi all. I've problem reading umts standard etsi ts 125.331 - for example 10.2.11 DOWNLINK DIRECT TRANSFER does not specify length of "message type" or "rrc transaction id", it only references 10.3.3.36 which do not specify length as well - only "Integer (0..3)". Where do I look up the actual bit lengths? As far as I recall in gsm spec it was given right away. I've tried to read asn in wireshark/asn1/rrc but got myself only same "Integer (0..3)" and attempt to read generated code makes my brain reboot. I've tried to compile it with erlc and use parsers as is but hit "function not exported" - I don't know enough erlang yet to fix this. -- best regards, Max, http://fairwaves.ru From noselasd at fiane.dyndns.org Mon Jun 10 17:43:28 2013 From: noselasd at fiane.dyndns.org (noselasd at fiane.dyndns.org) Date: Mon, 10 Jun 2013 19:43:28 +0200 Subject: umts rrc question In-Reply-To: <51B5FFEA.3060704@fairwaves.ru> References: <51B5FFEA.3060704@fairwaves.ru> Message-ID: <51B61040.9080400@fiane.dyndns.org> On 06/10/2013 06:33 PM, ? wrote: > Hi all. > > I've problem reading umts standard etsi ts 125.331 - for example 10.2.11 DOWNLINK > DIRECT TRANSFER does not specify length of "message type" or "rrc transaction id", it > only references 10.3.3.36 which do not specify length as well - only "Integer > (0..3)". Where do I look up the actual bit lengths? > > As far as I recall in gsm spec it was given right away. > > I've tried to read asn in wireshark/asn1/rrc but got myself only same "Integer > (0..3)" and attempt to read generated code makes my brain reboot. > > I've tried to compile it with erlc and use parsers as is but hit "function not > exported" - I don't know enough erlang yet to fix this. The protocol is specified in ASN.1. However ASN.1 can be encoded in different ways. RRC is encoded using unaligned PER , so refer to X.691 and other relevant ASN.1 specs. From 0b5cur4nt15t at gmail.com Mon Jun 10 17:12:49 2013 From: 0b5cur4nt15t at gmail.com (Obscura) Date: Mon, 10 Jun 2013 20:12:49 +0300 Subject: Getting burst in binary format for Kraken Message-ID: I sniffed some data in UDP (GSMTAP) format using osmocon, ccch_scan and Wireshark . Next step is "feeding" recived data to Kraken. But i need it in binary format. How can i get data in suitable format (114 bit per burst)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From akibsayyed at gmail.com Tue Jun 11 13:41:35 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Tue, 11 Jun 2013 19:11:35 +0530 Subject: decoding raw sdcch Message-ID: I am trying to decode raw bits god from burst_ind to get detail info about channel assignment. but i am unable to do so. here are steps i used. take raw bites (23 bits) create lapdm entity and then provide message and try to decode (fails) i get correct system information but not asssignment message. can some one please list details on decoding sdcch. i am using burst_ind branch. -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwjohn0 at gmail.com Wed Jun 12 00:31:03 2013 From: jwjohn0 at gmail.com (John Wu) Date: Wed, 12 Jun 2013 08:31:03 +0800 Subject: osmocombb not stable Message-ID: Hi list, I test osmocombb with C118. At the beginning everything seems ok. but after some minutes osmocombb can not camp to any cell. osmocon print the all cell rssi are -138dbm. Then I reload the ram firmware it camp the cell again. since osmocombb do not do release. So anyone know which version in the git is stable version. Regards From miguelrios35 at yahoo.com Thu Jun 13 14:28:55 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Thu, 13 Jun 2013 07:28:55 -0700 (PDT) Subject: no transceiver binary inside src/host/layer23/src/transceiver folder after running make Message-ID: <1371133735.39807.YahooMailNeo@web161603.mail.bf1.yahoo.com> Hi list, I'm trying to experiment with Sylvain's transceiver as per the wiki here?http://bb.osmocom.org/trac/wiki/Software/Transceiver I think that I may be doing something wrong when making in that I can see no transceiver binary inside /osmocom-bb/src/host/layer23/src/transceiver. The?host/layer23/src/transceiver?folder is created properly. ?After running ?make HOST_layer23_CONFARGS=--enable-transceiver, ?I don't see any transceiver binary in there, so naturally OpenBTS fails when I execute the?exec /src/host/layer23/src/transceiver/transceiver 1 script. I also don't see any errors when running make, although it scrolls by so fast it is hard to be sure. Thanks, Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguelrios35 at yahoo.com Thu Jun 13 15:22:33 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Thu, 13 Jun 2013 08:22:33 -0700 (PDT) Subject: no transceiver binary inside src/host/layer23/src/transceiver folder after running make In-Reply-To: <1371133735.39807.YahooMailNeo@web161603.mail.bf1.yahoo.com> References: <1371133735.39807.YahooMailNeo@web161603.mail.bf1.yahoo.com> Message-ID: <1371136953.85395.YahooMailNeo@web161604.mail.bf1.yahoo.com> Further to my post, here's the log from?make HOST_layer23_CONFARGS=--enable-transceiver? ?http://pastebin.com/DRb1RmJi I double checked that I indeed did checkout the correct sylvain/testing branch. And I can run other osmocom applications like mobile, so it seems I'm having only a problem with the transceiver app. Any help is appreciated. Thanks ________________________________ From: Miguel Rios To: "baseband-devel at lists.osmocom.org" Sent: Thursday, June 13, 2013 3:28 PM Subject: no transceiver binary inside src/host/layer23/src/transceiver folder after running make Hi list, I'm trying to experiment with Sylvain's transceiver as per the wiki here?http://bb.osmocom.org/trac/wiki/Software/Transceiver I think that I may be doing something wrong when making in that I can see no transceiver binary inside /osmocom-bb/src/host/layer23/src/transceiver. The?host/layer23/src/transceiver?folder is created properly. ?After running ?make HOST_layer23_CONFARGS=--enable-transceiver, ?I don't see any transceiver binary in there, so naturally OpenBTS fails when I execute the?exec /src/host/layer23/src/transceiver/transceiver 1 script. I also don't see any errors when running make, although it scrolls by so fast it is hard to be sure. Thanks, Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Thu Jun 13 15:57:54 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 13 Jun 2013 17:57:54 +0200 Subject: no transceiver binary inside src/host/layer23/src/transceiver folder after running make In-Reply-To: <1371136953.85395.YahooMailNeo@web161604.mail.bf1.yahoo.com> References: <1371133735.39807.YahooMailNeo@web161603.mail.bf1.yahoo.com> <1371136953.85395.YahooMailNeo@web161604.mail.bf1.yahoo.com> Message-ID: On Thu, Jun 13, 2013 at 5:22 PM, Miguel Rios wrote: > Further to my post, here's the log from make > HOST_layer23_CONFARGS=--enable-transceiver http://pastebin.com/DRb1RmJi You need to do a make distclean Those options are only taken into account when during the configure so if you already built once without that option, it won't do anything. Cheers, Sylvain From miguelrios35 at yahoo.com Thu Jun 13 16:18:23 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Thu, 13 Jun 2013 09:18:23 -0700 (PDT) Subject: no transceiver binary inside src/host/layer23/src/transceiver folder after running make In-Reply-To: References: <1371133735.39807.YahooMailNeo@web161603.mail.bf1.yahoo.com> <1371136953.85395.YahooMailNeo@web161604.mail.bf1.yahoo.com> Message-ID: <1371140303.23236.YahooMailNeo@web161605.mail.bf1.yahoo.com> Thanks Sylvain, That did the trick. I had previously only run make clean, which obviously wasn't enough. I appreciate your work in all this. I can't wait to explore some more. Cheers, Miguel ________________________________ From: Sylvain Munaut <246tnt at gmail.com> To: Miguel Rios Cc: "baseband-devel at lists.osmocom.org" Sent: Thursday, June 13, 2013 4:57 PM Subject: Re: no transceiver binary inside src/host/layer23/src/transceiver folder after running make On Thu, Jun 13, 2013 at 5:22 PM, Miguel Rios wrote: > Further to my post, here's the log from make > HOST_layer23_CONFARGS=--enable-transceiver? http://pastebin.com/DRb1RmJi You need to do a make distclean Those options are only taken into account when during the configure so if you already built once without that option, it won't do anything. Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguelrios35 at yahoo.com Sat Jun 15 13:30:01 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Sat, 15 Jun 2013 06:30:01 -0700 (PDT) Subject: scapy gsm-um with trx firmware? Message-ID: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> Hi list, Since getting Sylvain's transceiver to work with my C118, I started to look at scapy and specifically the gsm-um code as another interesting tool in the fuzzer's arsenal. I see that Laurent Weber's personal website, http://0xbadcab1e.lu/scapy_gsm_um-howto.txt, where he apparently had posted some examples and tips on playing with his code, is no longer available. Does anyone have a copy of those instructions? Has anyone tried running gsm-um with the TRX firmware? Any tips or pointers before I dive in? Cheers, Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From edachleger at yahoo.com Sun Jun 16 09:44:03 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Sun, 16 Jun 2013 10:44:03 +0100 (BST) Subject: scapy gsm-um with trx firmware? In-Reply-To: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> Message-ID: <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> ________________________________ But isn't it possible also to use the weber-code with the standard osmocombb-package,prior to the trx firmware? Since scapy was mentioned in some of the first talks about osmocombb with the only caveat that there is not a nice integration with scapy yet? Also if you need the testcall functionality? one possibly must use an earlier version of openbts. // Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguelrios35 at yahoo.com Sun Jun 16 15:22:07 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Sun, 16 Jun 2013 08:22:07 -0700 (PDT) Subject: scapy gsm-um with trx firmware? In-Reply-To: <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> Message-ID: <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> Thanks for the reply Erich. I'm not really sure about that. I'm going to experiment a bit if I can find the time this week. I see the gsm-um python code mentions it is possible to send out the scapy packets using udp, tcp and unix domain sockets, so I imagine it should be fairly easy to integrate with openbts and osmocom, either using the trx firmware or the older "regular" layer1 firmware. Anyone that has played around with this before have any tips? Cheers ________________________________ From: Erich Dachleger To: Miguel Rios ; "baseband-devel at lists.osmocom.org" Sent: Sunday, June 16, 2013 10:44 AM Subject: scapy gsm-um with trx firmware? ________________________________ But isn't it possible also to use the weber-code with the standard osmocombb-package,prior to the trx firmware? Since scapy was mentioned in some of the first talks about osmocombb with the only caveat that there is not a nice integration with scapy yet? Also if you need the testcall functionality? one possibly must use an earlier version of openbts. // Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From Max.Suraev at fairwaves.ru Mon Jun 17 09:31:41 2013 From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=) Date: Mon, 17 Jun 2013 11:31:41 +0200 Subject: scapy gsm-um with trx firmware? In-Reply-To: <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> Message-ID: <51BED77D.10505@fairwaves.ru> 16.06.2013 17:22, Miguel Rios ?????: > Thanks for the reply Erich. > > I'm not really sure about that. I'm going to experiment a bit if I can find the time > this week. > I see the gsm-um python code mentions it is possible to send out the scapy packets > using udp, tcp and unix domain sockets, so I imagine it should be fairly easy to > integrate with openbts and osmocom, either using the trx firmware or the older > "regular" layer1 firmware. > > Anyone that has played around with this before have any tips? > works for me using 'milenage' branch in https://github.com/zabbal/openbts-p2.8 I've ported testcall patches from previous version of openbts. -- best regards, Max, http://fairwaves.ru From miguelrios35 at yahoo.com Mon Jun 17 16:15:21 2013 From: miguelrios35 at yahoo.com (Miguel Rios) Date: Mon, 17 Jun 2013 09:15:21 -0700 (PDT) Subject: scapy gsm-um with trx firmware? In-Reply-To: <51BED77D.10505@fairwaves.ru> References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> <51BED77D.10505@fairwaves.ru> Message-ID: <1371485721.83063.YahooMailNeo@web161605.mail.bf1.yahoo.com> Thanks Max, I'll take a look at that branch soon. Offtopic: By the way, I'm looking forward to buying the um-TRX to play around with. Is it still due to start shipping the new batch in July? Does the standard um-trx work well with GSM or do we have to also purchase the clocktamer? Cheers, Miguel ________________________________ From: ? To: baseband-devel at lists.osmocom.org Sent: Monday, June 17, 2013 10:31 AM Subject: Re: scapy gsm-um with trx firmware? 16.06.2013 17:22, Miguel Rios ?????: > Thanks for the reply Erich. > > I'm not really sure about that. I'm going to experiment a bit if I can find the time > this week. > I see the gsm-um python code mentions it is possible to send out the scapy packets > using udp, tcp and unix domain sockets, so I imagine it should be fairly easy to > integrate with openbts and osmocom, either using the trx firmware or the older > "regular" layer1 firmware. > > Anyone that has played around with this before have any tips? > works for me using 'milenage' branch in https://github.com/zabbal/openbts-p2.8 I've ported testcall patches from previous version of openbts. -- best regards, Max, http://fairwaves.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Mon Jun 17 16:36:35 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 17 Jun 2013 18:36:35 +0200 Subject: scapy gsm-um with trx firmware? In-Reply-To: <1371485721.83063.YahooMailNeo@web161605.mail.bf1.yahoo.com> References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> <51BED77D.10505@fairwaves.ru> <1371485721.83063.YahooMailNeo@web161605.mail.bf1.yahoo.com> Message-ID: > Offtopic: By the way, I'm looking forward to buying the um-TRX to play > around with. > Is it still due to start shipping the new batch in July? Does the standard > um-trx work well with GSM or do we have to also purchase the clocktamer? The UmTRX comes standard with a high quality VCTXO (or optionally OCXO IIRC) based clock source and supports GPS calibration. No need for external clocking. Cheers, Sylvain From alexander.chemeris at gmail.com Mon Jun 17 16:54:46 2013 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Mon, 17 Jun 2013 20:54:46 +0400 Subject: scapy gsm-um with trx firmware? In-Reply-To: References: <1371303001.85816.YahooMailNeo@web161605.mail.bf1.yahoo.com> <1371375843.46270.YahooMailNeo@web171205.mail.ir2.yahoo.com> <1371396127.95734.YahooMailNeo@web161605.mail.bf1.yahoo.com> <51BED77D.10505@fairwaves.ru> <1371485721.83063.YahooMailNeo@web161605.mail.bf1.yahoo.com> Message-ID: On Jun 17, 2013 8:47 PM, "Sylvain Munaut" <246tnt at gmail.com> wrote: > > > Offtopic: By the way, I'm looking forward to buying the um-TRX to play > > around with. > > Is it still due to start shipping the new batch in July? Does the standard Yes, planned shipping by July. > > um-trx work well with GSM or do we have to also purchase the clocktamer? > > The UmTRX comes standard with a high quality VCTXO (or optionally OCXO > IIRC) based clock source and supports GPS calibration. > No need for external clocking. Yep, correct. VCTCXO with GPS by default, OCXO for big batches per request. External clocking is not needed in both cases. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO/Founder Fairwaves LLC http://fairwaves.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: From akibsayyed at gmail.com Sun Jun 30 06:45:55 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Sun, 30 Jun 2013 12:15:55 +0530 Subject: Sdcch to TCH Message-ID: can current master perform BCCH-> SDCCH->TCH? -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: