Messages

1

YateBTS / Re: BladeRF File or Device I/O failure when running YateBTS

« on: March 19, 2019, 04:05:25 PM »

What is the bladerf version and FPGA ?

My firmware version is 1.6.1 and FPGA is 0.1.2

2

YateBTS / Re: can not change MNC and MCC

« on: December 28, 2018, 01:40:22 PM »

I've gotten it to work with other values, you may be using the wrong broadcast frequency if your phone isn't detecting. Look up your phone's supported frequencies and then fine-tune it from there.

3

YateBTS / Re: BladeRF File or Device I/O failure when running YateBTS

« on: December 27, 2018, 02:33:29 PM »

1. Yes it functions correctly and makes calls from one phone to another.
2. Yes, for power cycling both the Raspberry Pi and the BladeRFx40.
3. Yes.

It isn't a huge deal, the behavior just appears strange to me and if I can optimize then that would be fantastic.

4

YateBTS / Re: RuntimeError: SW match failed ! Expected 9000 and got 6a86.

« on: November 27, 2018, 06:07:27 PM »

I had this same problem. I was never able to write a SIM from the NIB web gui, but I was able to do it from the command line. Here is a command that may be helpful to you that uses the pySim script itself instead of doing it through NIB.

Code: [Select]

./pySim-prog.py -p0 -t [card type] -a [ADM Pin] -x [mobile country code] -y [mobile network code] -i [IMSI] -s [iccid] -k [ki] -o [opc] -n [whatever name]

5

YateBTS / BladeRF File or Device I/O failure when running YateBTS

« on: November 27, 2018, 06:02:38 PM »

Hello, I'm having a strange issue. I'm using the BladeRFx40 with Yate and YateBTS. When I print the frequency, bandwidth, etc of the Blade, I see my correct settings. However, after running "sudo yate -s" and going to the BladeRF to print the values again, all correct values are replaced with "File or Device I/O failure". Is this normal operation or is this something I need to try and fix somehow?

Thanks!

6

YateBTS / Re: Yate -s stops at initialization

« on: November 22, 2018, 11:13:51 AM »

Here is the log. Am I using the compatible versions of BladeRFx40? My firmware is 1.6.1 but I read that Yate works best with 1.8.0. I'm using the evilbts from EvilSocket which uses Yate 5.5.1, would I be better off using different versions that play nicer with each other?

7

YateBTS / Re: Yate -s stops at initialization

« on: November 21, 2018, 03:23:22 PM »

That seems to have corrected it! However, now when I run yate -s, I get repeated BladeRF warnings of timestamp jumps.

Code: [Select]

Release 5.0.1 formal build date Nov 16 2016 rev
Starting MBTS...
Yate Engine is initialized and starting up on raspberrypi
RTNETLINK answers: File exists
MBTS ready
2018-11-21_21:11:54.487401 <bladerf/1:WARN> RX: timestamp jumped by 3774 to 21464984 in buffer 6/8 [0x753009f8]
2018-11-21_21:11:54.493851 <bladerf/1:WARN> RX: timestamp jumped by 2209 to 21480854 in buffer 6/8 [0x753009f8]

// This timestamp jump excessively occurs multiple times a second until I Ctrl+C out of Yate
I'm also seeing in the BladeRF CLI that after writing the "print" command, valid values are given when Yate is not running, but when I print while Yate is running, every value reads as "File or device I/O failure". Can you shed some light on what's going on now?

I appreciate your help so much in getting me this far!

8

YateBTS / Re: Which c++ standard should we compile YateBTS with ?

« on: November 19, 2018, 05:21:54 PM »

Will this patch function with Yate 5,x? I'm working with the BladeRF and was told there are specific versions of Yate, YBTS and BladeRF firmware/FPGA that "play well" together, do you know what versions of BladeRF are compatible with Yate 6.x?

9

YateBTS / Re: yateBTS network operator name of 712712

« on: November 16, 2018, 01:13:49 PM »

I may not be much help, but the one thing I do know is that when you telnet localhost 5038 and run "status engine" you can view where yate is pulling your config files from. That may point you in the right direction if you're wondering what directories Yate is pulling its files from.

10

YateBTS / Re: Yate -s stops at initialization

« on: November 15, 2018, 09:02:35 PM »

I attached screenshots of each directory the engine points to, does everything look alright?

Code: [Select]

%%+status:engine
name=engine,type=system,version=5.5.1,revision=,nodename=raspberrypi;plugins=67,inuse=1,handlers=490,hooks=3,messages=0,supervised=true,runattempt=1,lastsignal=0,threads=27,workers=1,mutexes=232,semaphores=0,acceptcalls=accept,congestion=0;sharedpath=/usr/local/share/yate,configpath=/usr/local/etc/yate,usercfgpath=/root/.yate,modulepath=/usr/local/lib/yate,workpath=/home/pi
%%-status

Notice that I don't have anything located at /root/.yate, but I'm not sure how to remedy this.

I ran "which -a yate-config" and got version 5.5.1 located in /usr/local/bin, is it a problem that I have it installed from sources instead of packages? I'm not seeing anything that refers to the ybladeRF module at all in the ./configure output or the modules folder, is there a way to verify or manually load it to the right location? Also, I checked the Prerequisites and I didn't have libgsm1-dev, subversion or doxygen, so those have been installed but I'm still getting the same errors. I also uploaded an attachment of some of the output when running "make install" for yatebts, which seems to be failing.

What all seems to be going wrong? I may just reinstall my Raspberry Pi OS and start over again without any of the EvilSocket guide. He listed a specific firmware and FPGA for the BladeRF, what is the latest "correct" versions of Yate/YateBTS/BladeRF compatibility?

11

YateBTS / Re: Yate -s stops at initialization

« on: November 14, 2018, 04:28:20 PM »

Sorry about the large chunk of text, I've edited my posts to have a txt file instead.

What is the correct placement of all the conf files? I've seen different sources saying different locations, either usr/local or etc/share and I'm not well versed enough on Linux to know the correct placement. I was suspicious that the conf files weren't being pulled from the right location. I followed the EvilSocket guide and installed and configured both Yate and YateBTS in usr/local by running ./configure --prefix=/usr/local. What conf files exist that need to point to the correct places?

12

YateBTS / Re: Yate -s stops at initialization

« on: November 13, 2018, 07:32:04 PM »

All I'd like to be able to do is make a call from one handset to another (both owned by me with sysmo USIMs configured by nibweb). Any tips or pointers? Even the simplest things I could be missing, like having yate point to the wrong location of files or something silly like that.

After running yate --version I'm seeing Yate 5.5.1 devel1 r. Here is my BladeRF info:   
bladeRF-cli version:        1.6.1-git-c9a2230c
libbladeRF version:         2.0.2-git-c9a2230c
Firmware version:           1.6.1-git-053fb13-buildomatic
FPGA version:               0.1.2

13

YateBTS / Re: Yate -s stops at initialization

« on: November 13, 2018, 07:28:43 PM »

And here is the output after running yate -s as root in /usr/local/etc/yate after running bladeRF-cli -i in another PuTTY session.

14

YateBTS / Re: Yate -s stops at initialization

« on: November 13, 2018, 07:19:22 PM »

Here is my ybts.conf, in /usr/local/etc/yate.

15

YateBTS / Re: Yate -s stops at initialization

« on: November 06, 2018, 01:20:29 PM »

When you say config files and a log, do you mean the ybts.conf and a verbose output of running yate?