Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - goodboytower

Pages: [1]
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?


YateBTS / Comprehensive list of compatible versions?
« on: November 06, 2018, 01:19:04 PM »
Hello all, I've been curious on what the current state of the art for YateBTS and BladeRF versions are. I've referenced a couple different guides, mainly hanging onto the evilsocket guide, but I'm coming across various different "you must use X version" and "as of 2018 you must use Y version". So I'm trying to avoid confusion and errors, so what are the "correct" compatible versions of everything involved in getting the BladeRF to broadcast with Yate? What's important to have the right version of, and what doesn't matter?

Thanks in advance!

YateBTS / Yate -s stops at initialization
« on: October 30, 2018, 08:11:21 PM »
Hello! I just got a BladeRF for a class project for use with my Raspberry Pi. I want to ethically broadcast as a BTS to make a call from my phone to my partner's phone (and nobody else, nor use it as an IMSI catcher). I'm in America and going to use Band 8 900MHZ so I don't trip over actual American phone frequencies. But I keep getting stuck on one problem that I can't get past while following the EvilSocket guide.

When I run yate -s as root, it hangs up on the "Yate engine is initialized and starting up on raspberrypi". It doesn't freeze or crash, it just stops until I Ctrl+C out of it. I'm assuming RTNETLINK has something to do with it since that's what comes next on all the documentation I've read. Any ideas on what's going wrong with it?

My BladeRF-cli version =1.6.1, libbladeRF=2.0.2, FW=1.6.1, and FPGA=0.1.2 and I'm using the evilbts.

Can anybody give some suggestions on even the simplest/dumbest things I might have missed? What files have to be in a specific place? Simple diagnostic things I should make sure of? The only thing I've deviated from in the EvilSocket guide is running everything as root instead of making a group with permissions for running.

Pages: [1]