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
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 <your path to osmocom-bb>/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
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
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(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
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
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)?
Hi Sylvain
I wanted to know unit for TOA means, is it in miliseconds,nanoseconds etc.
help is appreciated
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
No it doesn't.
> From: ml(a)mail.tsaitgaist.info
> To: baseband-devel(a)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
>