Hi,
I'm trying to build a simple node that would encap/decap between IP and GTP
in the user plane. For this I have been using gtp-link and gtp-tunnel tools
of the libgtpnl, but with no luck so far. Could anyone please review my
setup and let me know what I'm doing wrong?
Topology:
node1 - DUT, I would like to be able to send a ping from this node such
that it is encapsulated into GTP tunnel towards node2.
2 interfaces:
- ens6 - represents interface towards MS, has address 20.1.1.1/24
- ens7 - represents interface towards GGSN, has address 10.1.1.1/24
node2
Just a single interface towards node1, address 10.1.1.2/24
Test:
On node2, I'm following these steps:
- creating a GTP device:
# ./gtp-link add gtp-u
- adding a GTP tunnel:
# ./gtp-tunnel add gtp-u v1 20 10 20.1.1.1 10.1.1.2
# ./gtp-tunnel list
version 1 tei 20/10 ms_addr 20.1.1.1 sgsn_addr 10.1.1.2
- adding a route to an address representing APN to use the GTP device:
# ip route add 8.8.8.8 src 20.1.1.1 dev gtp-u
- Trying to ping 8.8.8.8
Result:
I was expecting to see ECMP packets to 8.8.8.8 to be sent out via ens7
towards node2 and encapsulated in GTP. However, I can only see that these
packets appear on the gtp-u interface, but are not forwarded. Looking at
interface stats on gtp-u, I can see that the ping hits "tx_error" counter.
Is there anything I'm missing here? Are any parameters wrong? Or am I
misunderstanding the function of the GTP-U kernel support entirely?
Any help would be appreciated.
Thanks,
Michael
hello,Please forgive my childishness,Can you tell me how to compile and install libgtpnl?thanks
I saw that you wrote the libgtpnl project on github, but there is no readme above.
Hi,
We are using Honor 7X mobile phone with Huawei Kirin modem and observed that GPRS and EGPRS attach is not working with Huawei Kirin Modem phones.
There is no issue observed from OSMO-PCU. it seems either Huawei Kirin modem issue or OSMO-SGSN issue.
Please check below analysis for this issue.
1- UE send attach request with IMSI and invalid MCC and MNC to SGSN.
2- SGSN send Identity Request with IMEI to UE.
3- UE responded Identity Response with IMEI to SGSN.
4- SGSN sends ATTACH ACCEPT message to SGSN with new PMTSI but UE is not responding ATTACH COMPLETE message to SGSN and resend ATTACH REQUEST message to SGSN.
5- SO SGSN re transmit ATTACH ACCEPT message to UE and after max number of re transmission , SGSN is release UE MM context.
It seems that UE is not accepting ATTACH ACCEPT message.
We also observed that Huawei Kirin UE is sending wrong LLC data to SGSN.
UE had set more bit in RLC LME header and send invalid LLC data with 0x2B.
So OSMO-PCU had forward this data to SGSN because more bit is set and SGSN
is complaining LLC error for this LLC data.
Please look into this issue or let us know if we have fix for this issue.
Thanks,
Bipin Jaiswal
Dear all,
I would like to get your input as to when we should schedule OsmoDevCon 2019.
NOTE: OsmoDevCon is our "for developers by developers" event, not to be confused
with OsmoCon, our public conference.
If we want to stay with the usual "Friday through Monday in April" arrangement,
we have the following options:
April 05-08, 2019
April 12-15, 2019
April 26-29, 2019
The one missing weekend in the list above is the easter weekend, which is probably
a good idea to exclude as flights and hotels are more expensive during that time,
and people might have other plans during holidays.
I would like to invite anyone planning to attend the Osmocom Developer Conference 2019
to participate in the poll at https://dudle.inf.tu-dresden.de/OsmoDevCon2019/ to
state their availability/preference. The Dudle only shows the first day of the four
days of OsmoDevCon.
Looking forward to your feedback so we can settle on a date soon. Thanks!
Kind regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear all
We are facing the following problem and hope you can help us:
- We use OSMO as UMTS core emulation, working with our real NodeB
- During UE attach procedure we see from SGSN "Location Update
Reject"
and afterthat UE is released.
- We do the comparison test with real UMTS core and our real NodeB,
here
it works properly, UE can attach successful.
We assume there is some Osmo configuration problem but we have not
found the root cause, we very appreciate if you can take a look and give us
some advice.
Here is the current message flow of UE attach
10.2.9.200 10.2.9.139 RANAP 170 (RUA) InitialUE-Message
(DTAP) (MM) Location Updating Request
10.2.9.139 10.2.9.200 RANAP 158 SACK (RUA) DirectTransfer
(DTAP) (MM) Authentication Request
10.2.9.200 10.2.9.139 RANAP 222 SACK (RUA)
InitialUE-Message (DTAP) (GMM) Attach Request
10.2.9.139 10.2.9.200 RANAP 122 SACK (RUA) DirectTransfer
(DTAP) (GMM) Identity Request
10.2.9.200 10.2.9.139 RANAP 118 (RUA) DirectTransfer (DTAP)
(MM) Authentication Failure
10.2.9.139 10.2.9.200 RANAP 158 SACK (RUA) DirectTransfer
(DTAP) (MM) Authentication Request
10.2.9.200 10.2.9.139 RANAP 154 SACK (RUA) DirectTransfer
(DTAP) (GMM) Identity Response
10.2.9.139 10.2.9.200 RANAP 162 SACK (RUA) DirectTransfer
(DTAP) (GMM) Authentication and Ciphering Req
10.2.9.200 10.2.9.139 RANAP 110 (RUA) DirectTransfer (DTAP)
(MM) Authentication Response
10.2.9.139 10.2.9.200 RANAP 138 SACK (RUA)
SecurityModeCommand
10.2.9.200 10.2.9.139 RANAP 98 (RUA) SecurityModeComplete
10.2.9.139 10.2.9.200 RANAP 122 SACK (RUA) CommonID
10.2.9.200 10.2.9.139 RANAP 166 SACK (RUA) DirectTransfer
(DTAP) (GMM) Authentication and Ciphering Resp
10.2.9.139 10.2.9.200 RANAP 134 SACK (RUA) DirectTransfer
(DTAP) (MM) Location Updating Accept
10.2.9.139 10.2.9.200 RANAP 122 (RUA) SecurityModeCommand
--> 10.2.9.139 10.2.9.200 RANAP 106 (RUA) DirectTransfer (DTAP)
(MM) Location Updating Reject
10.2.9.139 10.2.9.200 RANAP 102 (RUA) Iu-ReleaseCommand
10.2.9.200 10.2.9.139 RANAP 114 SACK (RUA)
Iu-ReleaseComplete
10.2.9.200 10.2.9.139 RANAP 102 (RUA) SecurityModeReject
10.2.9.200 10.2.9.139 RANAP 102 (RUA) Iu-ReleaseRequest
10.2.9.139 10.2.9.200 RANAP 118 SACK (RUA)
Iu-ReleaseCommand
10.2.9.200 10.2.9.139 RANAP 114 SACK (RUA)
Iu-ReleaseComplete
Thanks and regards
Tuan Lam
Dear fellow Osmocom developers,
During the past hours, we've been experiencing master-osmo-sgsn build
failures. It coincides with some libosmocore.git vty change merge,
it would be great if people working on this and/or osmo-sgsn can have a look.
Thanks!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
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(a)entropysolution.com<mailto:ron.menez@entropysolution.com>