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.


Messages - rainnw

Pages: [1]
1
Hello,

I am running YateBTS build 503 with BladeRF on Ubuntu. Devices are able to register and attach. They have IP addresses and they can send packets, as seen on sgsntun:

Code: [Select]
root@sheldon-B85M-D3H:/home/sheldon# tcpdump -ni sgsntun
tcpdump: WARNING: sgsntun: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sgsntun, link-type RAW (Raw IP), capture size 65535 bytes
18:14:51.308269 IP 10.1.255.11.39078 > 8.8.8.8.53: 12748+ A? google.com. (28)
18:14:51.308296 IP 10.1.255.11.3833 > 8.8.8.8.53: 29513+ A? google.com. (28)
18:14:52.287408 IP 10.1.255.11.24805 > 8.8.8.8.53: 1136+ A? google.com. (28)
18:14:52.329324 IP 10.1.255.11.2474 > 8.8.4.4.53: 30185+ A? google.com. (28)
18:14:52.385379 IP 10.1.255.11.10889 > 8.8.8.8.53: 7742+ A? www.googleapis.com. (36)

I have the following configured:

Code: [Select]
# cat /proc/sys/net/ipv4/ip_forward
1

And I am using the OpenBTS IP Tables and loading them in with iptables-restore:

Code: [Select]
# Generated by iptables-save v1.4.4
*nat
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -o eth0 -j MASQUERADE
COMMIT
# Generated by iptables-save v1.4.4
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT

However, as you can see above, traffic goes nowhere. There is no traffic routed from the mobile devices onto eth0 with nat turned on or off. The packets just seem to die on the sgsntun interface.

Any idea what the problem could be?

2
YateBTS / Re: RACH burst for unsupported device?
« on: August 10, 2015, 02:44:49 PM »
Thank you. I downgraded and now devices are registering.

3
YateBTS / RACH burst for unsupported device?
« on: August 03, 2015, 01:21:25 PM »
Hello,

I am trying to get YateBTS working on a BladeRF with Ubuntu. Everything is built and my unlocked phone can see the BTS in its network list. However, when I select this network, it hangs for a while and fails. I get this in the logs when this happens:

Quote
2015-07-28_21:55:26.084593 <gsmtrx:ALL> ARFCN[0]: Slot 5. Excessive TOA error=-3 peak/mean=5.20339 count=1 [0x7f86f0016440]
2015-07-28_21:55:26.092936 <gsmtrx:ALL> ARFCN[0]: Slot 3. Excessive TOA errors 18 [0x7f86f0016440]
2015-07-28_21:55:26.194235 <gsmtrx:ALL> ARFCN[0]: Slot 3. Excessive TOA error=4 peak/mean=5.91555 count=1 [0x7f86f0016440]
2015-07-28_21:55:26.244821 <gsmtrx:ALL> ARFCN[0]: Slot 2. Excessive TOA error=4 peak/mean=3.41899 count=20 [0x7f86f0016440]
2015-07-28_21:55:26.271317 <mbts:NOTE> RadioResource.cpp:243:AccessGrantResponder: RACH burst for unsupported service RA=186
2015-07-28_21:55:26.271360 <gsmtrx:ALL> Handling command 'CMD 0 NOHANDOVER 0' arfcn=0 [0x7f86f0009d10]
2015-07-28_21:55:26.271381 <gsmtrx:ALL> Command 'CMD 0 NOHANDOVER 0' (ARFCN=0) RSP '0'
2015-07-28_21:55:26.271486 <gsmtrx:ALL> Handling command 'CMD 0 NOHANDOVER 0' arfcn=0 [0x7f86f0009d10]
2015-07-28_21:55:26.271491 <gsmtrx:ALL> Command 'CMD 0 NOHANDOVER 0' (ARFCN=0) RSP '0'
2015-07-28_21:55:26.284302 <gsmtrx:ALL> ARFCN[0]: Slot 7. Excessive TOA errors 31 [0x7f86f0016440]
2015-07-28_21:55:26.307710 <gsmtrx:ALL> ARFCN[0]: Slot 7. Excessive TOA error=5 peak/mean=3.94474 count=1 [0x7f86f0016440]
2015-07-28_21:55:26.445563 <gsmtrx:ALL> ARFCN[0]: Slot 6. Excessive TOA error=-5 peak/mean=7.12925 count=24 [0x7f86f0016440]

I am not sure what these other errors are, but any idea what "2015-07-28_21:55:26.271317 <mbts:NOTE> RadioResource.cpp:243:AccessGrantResponder: RACH burst for unsupported service RA=186" means?


Pages: [1]