10 Aug
2018
10 Aug
'18
5:48 p.m.
Hi Community,
We tried to used the GPRS capability of OSMOCOM.
Installation and configuration were based in the URL provided below:
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…
We successfully installed the needed elements to run GPRS and we were able to run the
following:
osmo-msc
osmo-stp
osmo-hnbgw (optional)
osmo-ggsn
osmo-sgsn
osmo-mgw
osmo-bsc
osmo-trx-uhd
osmo-hlr
osmo-pcu
UE were able to camp but IP Address is unavailable (checked it under Settings > About
Phone > Status)
No session / request coming in the OSMO-SGSN.
We are also flooded with this log in OSMO-PCU:
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
Any suggestion / comments what seems to be the problem with our setup?
TIA.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
24 Aug
24 Aug
6:08 a.m.
Hi Community,
We were able to remove the error logs flooding in OSMO-PCU by upgrading to the latest
version of OSMO Elements and doing the IPV4 forwarding and masquerading ad-hoc as per
OpenGGSN documentation (“http://ftp.osmocom.org/docs/latest/osmoggsn-usermanual.pdf”).
Now, UE still not able to obtain an IP address. We made the “auth-policy accept-all” in
OSMO-SGSN to accept all request.
Below are the ifconfig and config files used for the testing.
IFCONFIG:
# ifconfig
apn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.42.0 P-t-P:192.168.42.0 Mask:255.255.255.0
UP POINTOPOINT RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:7c:eb:f0
inet addr:192.168.1.175 Bcast:0.0.0.0 Mask:255.255.255.255
inet6 addr: fe80::baae:edff:fe7c:ebf0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:622663 errors:0 dropped:0 overruns:0 frame:0
TX packets:605604 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:902447377 (902.4 MB) TX bytes:897214804 (897.2 MB)
Interrupt:20 Memory:aa100000-aa120000
enp0s25.60 Link encap:Ethernet HWaddr b8:ae:ed:7c:eb:f0
inet addr:192.168.10.3 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::baae:edff:fe7c:ebf0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:603890 errors:0 dropped:0 overruns:0 frame:0
TX packets:600040 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:880955628 (880.9 MB) TX bytes:891260801 (891.2 MB)
enp0s25.80 Link encap:Ethernet HWaddr b8:ae:ed:7c:eb:f0
inet addr:192.168.1.170 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::baae:edff:fe7c:ebf0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18701 errors:0 dropped:0 overruns:0 frame:0
TX packets:5462 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7789419 (7.7 MB) TX bytes:1101655 (1.1 MB)
OSMO-HLR:
# more osmo-hlr.cfg
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-MGW:
# more osmo-mgw-for-bsc.cfg
mgcp
bind ip 192.168.1.170
# default port is 2427 (is used for MSC's MGW)
bind port 12427
line vty
# default VTY interface is on 127.0.0.1 (used for MSC's MGW)
bind 127.0.0.2
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-STP:
# more osmo-stp.cfg
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
listen m3ua 2905
accept-asp-connections dynamic-permitted
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-GGSN:
# more osmo-ggsn.cfg
log stderr
logging level all debug
logging filter all 1
logging print category 1
ggsn ggsn0
gtp bind-ip 192.168.1.175
apn internet
tun-device apn0
type-support v4
ip dns 0 192.168.1.1
ip dns 1 8.8.8.8
ip ifconfig 192.168.42.0/24
ip prefix dynamic 192.168.42.0/24
no shutdown
default-apn internet
no shutdown ggsn
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-HNBGW:
# more osmo-hnbgw.cfg
hnbgw
iuh
local-ip 192.168.1.170
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-SGSN:
# more osmo-sgsn.cfg
sgsn
gtp local-ip 192.168.1.170
ggsn 0 remote-ip 192.168.1.175
ggsn 0 gtp-version 1
auth-policy accept-all
gsup remote-ip 127.0.0.1
ns
encapsulation udp local-ip 192.168.1.170
encapsulation udp local-port 23001
encapsulation framerelay-gre enabled 0
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-MSC:
# more osmo-msc.cfg
network
network country code 515
mobile network code 94
short name testNETWORK
long name testNETWORK
encryption a5 0
! encryption a5 1
msc
mgw remote-ip 192.168.1.170
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
logging level ref debug
OSMO-BSC:
# more osmo-bsc.cfg
network
network country code 515
mobile network code 94
encryption a5 0
! encryption a5 1
bts 0
type sysmobts
band GSM900
location_area_code 23
ip.access unit_id 0 0
gprs mode gprs
gprs nsvc 0 remote ip 192.168.1.170
gprs nsvc 0 remote udp port 23001
gprs nsvc 0 local udp port 23000
gprs nsvc 0 nsvci 1800
gprs nsei 1800
gprs cell bvci 1800
trx 0
rf_locked 0
arfcn 115
nominal power 23
timeslot 0
phys_chan_config CCCH+SDCCH4
timeslot 1
phys_chan_config SDCCH8
timeslot 2
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 3
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 4
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 5
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 6
phys_chan_config TCH/F_TCH/H_PDCH
timeslot 7
phys_chan_config PDCH
e1_input
e1_line 0 driver ipa
msc 0
mgw remote-ip 192.168.1.170
mgw remote-port 12427
allow-emergency deny
codec-list hr3
log stderr
logging print extended-timestamp 1
logging level all debug
logging filter all 1
logging print category 1
OSMO-TRX:
# more osmo-trx-umtrx.cfg
log stderr
logging filter all 1
logging color 1
logging print category 1
logging timestamp 1
logging print file basename
logging level all info
!
line vty
no login
!
trx
bind-ip 127.0.0.1
remote-ip 127.0.0.1
base-port 5700
dev-args
addr=192.168.10.2,pa=NONE,pa_power_max_dbm=23,fifo_ctrl_window=0,status_port=12345
! egprs enable
tx-sps 4
rx-sps 4
rssi-offset 38
rt-prio 18
chan 0
OSMO-PCU:
# more osmo-pcu.cfg
!pcu
! flow-control-interval 10
! cs 2
! alloc-algorithm dynamic
! alpha 0
! gamma 0
pcu
flow-control-interval 10
cs 2
alloc-algorithm dynamic
alpha 0
gamma 0
two-phase-access
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
On Aug 10, 2018, at 11:48 PM, Ron
<ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>> wrote:
Hi Community,
We tried to used the GPRS capability of OSMOCOM.
Installation and configuration were based in the URL provided below:
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…
We successfully installed the needed elements to run GPRS and we were able to run the
following:
osmo-msc
osmo-stp
osmo-hnbgw (optional)
osmo-ggsn
osmo-sgsn
osmo-mgw
osmo-bsc
osmo-trx-uhd
osmo-hlr
osmo-pcu
UE were able to camp but IP Address is unavailable (checked it under Settings > About
Phone > Status)
No session / request coming in the OSMO-SGSN.
We are also flooded with this log in OSMO-PCU:
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
<000c> gprs_bssgp_pcu.cpp:848 Sending unblock on BVCI 1800
<000c> gprs_bssgp_bss.c:274 BSSGP (BVCI=1800) Tx BVC-BLOCK
<000c> gprs_bssgp.c:288 Cell 001-01-23-0 CI 0 on BVCI 1800
<000c> gprs_bssgp_bss.c:294 BSSGP (BVCI=1800) Tx BVC-RESET CAUSE=O&M
intervention
<000c> gprs_bssgp.c:550 BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:354 Rx BSSGP BVCI=0 (SIGN) PDU type BVC-UNBLOCK unknown
<000c> gprs_bssgp_util.c:238 BSSGP BVCI=0 Tx STATUS, cause=Protocol error -
unspecified
<000c> gprs_bssgp_pcu.cpp:304 Rx BSSGP BVCI=0 (SIGN) BVC_RESET_ACK
Any suggestion / comments what seems to be the problem with our setup?
TIA.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
1:19 p.m.
Hi Ron,
Handing an IP address to the subscriber is done by the GGSN. For me, that was
the easy part, the hard part being to get packets sent and received through the
tunnel on the GGSN machine.
Here's what I use for osmo-ggsn.cfg and how I set up the APN:
dev="eth0"
apn="apn0"
sudo iptables -t nat -A POSTROUTING -s 192.168.42.0/24 -o $dev -j MASQUERADE
sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
sudo ip tuntap add dev $apn mode tun user $USER group $USER
sudo ip addr add 192.168.42.0/24 dev $apn
sudo ip link set $apn up
ggsn ggsn0
apn internet
tun-device apn0
type-support v4
ip dns 0 192.168.0.1
ip dns 1 9.9.9.9
ip prefix dynamic 192.168.42.0/24
no shutdown
default-apn internet
no shutdown ggsn
With this config, the apn0 tun device is set up as root, hence osmo-ggsn
doesn't need to create a tun device itself and can run as a non-privileged
user.
HTH,
~N
2095
days inactive
2109
days old
osmocom-net-gprs@lists.osmocom.org
2 comments
2 participants
participants (2)
-
Neels Hofmeyr -
Ron