Messages

1

YateBTS / Re: bladeRF2 a4 and yate

« on: October 08, 2019, 02:04:39 PM »

Someone should pin this....

This will help with the current error but it still may not fully work

https://nuand.com/forums/viewtopic.php?f=5&t=5094#p9358

2

YateBTS / Re: Phone doesn't auto connect to yatebts

« on: September 04, 2019, 02:10:00 PM »

from your logs:

Code: [Select]

2019-06-18_20:26:40.712131 <mbts:NOTE> proc 6384 RadioResource.cpp:243:AccessGrantResponder: thread 140629409253120: RACH burst for unsupported service RA=194
I believe we are running into the same issue. see https://forum.yate.ro/index.php?topic=2066.0 I suspect a compatibility between the phone and the version of Yates being used in the package.

I'm trying to gather a little more info. What phones have you tested with?  What phoneOS/version/carrier/SIMcard is being tested?
Do you get the previous mentioned log every time it fails?

Thanks

3

YateBTS / Re: band indicator = 1800 even though frequency set to 900

« on: August 19, 2019, 03:28:52 PM »

I'm still trying to find what this error exactly means. Does this error mean the packet sent by the phone is corrupted?

If so what phones should work, that are still available? I've tested multiple phones without any luck.

thank you

4

YateBTS / Re: Yate Failed to open usb Device

« on: June 05, 2019, 11:50:30 AM »

Hi
I have the same problem
please help me step by step

Unfortunately no one has time to help users step by step here. Maybe not me, I just started, but users who know a lot about this are in demand.  But if you provide the steps you have taken and exactly where the issue then some users including myself can help if we know the answer. logs also help a lot.

Have you carefully read there this post and fallowed the steps? https://nuand.com/forums/viewtopic.php?f=5&t=5094#p9358
Where are you stuck at?

5

YateBTS / Re: band indicator = 1800 even though frequency set to 900

« on: May 23, 2019, 05:17:31 PM »

A small update to this. I think this is where my issue is

I'm getting this log line.

"RACH burst for unsupported service RA="

looking at the code (../Control/RadioResource.cpp) it seems to reference the cell tower receiving a bad frame from the phone. However a PCAP as I have done in the past doesn't show the frame so I have no idea what is wrong with it. Adding -v's to start yates doesn't seem to show any additional errors.

Is there a way to get more information on what is wrong with this incoming frame?

6

YateBTS / Re: band indicator = 1800 even though frequency set to 900

« on: May 22, 2019, 05:16:05 PM »

I don't know if the attachment got removed but I see there is none. I have added it again.

After further testing I've found a bug related to the issue I am having. It's already been filed but doesn't effect operation of the cell tower.

I am able to see a strong signal from the cellphone at the correct uplink frequency using a SDR-RTL. For some reason I'm unable to read any packets received on the cell tower or see the cell name on the phone.

What logs can I look at to see if there is any signal received by the BladeRF from the phone?

7

YateBTS / band indicator = 1800 even though frequency set to 900

« on: March 29, 2019, 11:59:51 AM »

I'm having a problem with the phone connecting to the cell station. I have set the BladeRF station to broadcast on the 900MHz range and verified this with another SDR. My cellphone sees the station but can't connect.

Troubleshooting:
Attempted to connect to station then inspected for rejected IMSI numbers. none found.

Code: [Select]

nipc list rejected
IMSI            No attempts register
--------------- ---------------
Here is my configuration from ybts.conf

Code: [Select]

Radio.Band=900
Radio.C0=975
Identity.MCC=510
Identity.MNC=01
Here is the wired part. I performed a pcap for GMS traffic. I only see downlink traffic no uplink traffic. In the downlink traffic I see the band indicator field says 1800 even though I have set this to 900MHz. Please see attached pcap.

no. 426 > GSM CCCH > SI 6 Rest Octets > Band Indicator = 1800

I remember seeing a bug that was posted a few years ago about the wrong frequency being broadcast. I'm not sure if this is related.

Is this expected? It would of course help if I got a working pcap as well. I would like to review a pcap on a working configuration.

Here are the commands to get a pcap.

Code: [Select]

telnet localhost 5038
mbts config Control.GSMTAP.GSM on
quitconnect phone

Code: [Select]

sudo tcpdump -i any udp port 4729 -w GSMtraffic.pcap

8

YateBTS / Re: Yate Failed to open usb Device

« on: February 22, 2019, 03:58:53 PM »

@rockthestreet81 @silodk I was able to get yate communicating with BladeRF2 xA4 fallowing this post and paying special attention to the versions. I used Firmware version: 2.2.0, because I couldn't find 2.1.0  https://nuand.com/forums/viewtopic.php?f=5&t=5094#p9358 

The device with id 2cf0:5250 is not currently detected by bladerf module as supported.

For nonce: you also don't have the bladerf module.
See the log line: Failed to create radio interface: Message not handled.
Most probably it wasn't built at all.

Thanks for the feedback, however I do have the bladerf module installed. Gqrx runs without issue and requires this module.  Perhaps there is a linking issue? Anyways at this time it doesn't really matter.

9

YateBTS / Re: Yate Failed to open usb Device

« on: February 21, 2019, 01:36:26 PM »

I appear to be running into the same issue. I get the same errors and am using BladeRF xA4. I have fallowed this setup. https://github.com/Nuand/bladeRF/wiki/Setting-up-Yate-and-YateBTS-with-the-bladeRF

The biggest difference I see is I'm using Ubuntu 18.04.
I have also setup the configuration.

Code: [Select]

Radio.Band 900
Radio.C0 975

Code: [Select]

bladeRF> version

  bladeRF-cli version:        1.7.1-2018.12-rc3-2-ppabionic
  libbladeRF version:         2.2.0-2018.12-rc3-2-ppabionic

  Firmware version:           2.2.0-git-47f93fe1
  FPGA version:               0.10.2

Code: [Select]

bladeRF> info

  Board:                    Nuand bladeRF 2.0 (bladerf2)
  Serial #:                 617161f770ef45bca2e08a433ed771e6
  VCTCXO DAC calibration:   0x1eeb
  FPGA size:                49 KLE
  FPGA loaded:              yes
  Flash size:               32 Mbit (assumed)
  USB bus:                  4
  USB address:              4
  USB speed:                SuperSpeed
  Backend:                  libusb
  Instance:                 0

Code: [Select]

root@ubuntu:/home/bladerf#yate -vv -CDoa

Release 6.1.1 formal build date Feb 20 2019 rev668
2019-02-21_11:25:15.019084 <mbts:NOTE> proc 30764 GSMConfig.cpp:80:regenerateBeacon: thread 139651856996160: regenerating system information messages, changemark 1
Starting MBTS...
2019-02-21_11:25:15.019166 <mbts:NOTE> proc 30764 TRXManager.cpp:127:sendCommandPacket: thread 139651856996160: this:0x563665ca05c0 command CMD RESET 1
2019-02-21_11:25:15.019477 <gsmtrx:CRIT> Failed to create radio interface: Message not handled
ALERT 139651856996160 11:25:15.0 proc 30764 TRXManager.cpp:224:sendCommand: thread 139651856996160: RESET failed with status 2
2019-02-21_11:25:15.019770 <mbts:NOTE> proc 30764 TRXManager.cpp:152:sendCommandPacket: thread 139651856996160: this:0x563665ca05c0 response RSP RESET 2 to command CMD RESET 1
2019-02-21_11:25:15.019847 <mbts:WARN> proc 30764 TRXManager.cpp:224:sendCommand: thread 139651856996160: RESET failed with status 2
ALERT 139651856996160 11:25:15.0 proc 30764 OpenBTS.cpp:251:main: thread 139651856996160: Failed to reset transceiver
2019-02-21_11:25:15.020129 <mbts:WARN> proc 30764 OpenBTS.cpp:251:main: thread 139651856996160: Failed to reset transceiver

Troubleshooting
Installed libusb-1.0-0-dev before compiling yate

Code: [Select]

root@ubuntu:/home/bladerf# lsusb
Bus 004 Device 004: ID 2cf0:5250 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub