osmocom-net-gprs

osmocom-net-gprs@lists.osmocom.org

6 participants
480 discussions

[PATCH net-next 0/2] constify nla_policy

by Stephen Hemminger

Almost all places that use nla_policy declare it const. A couple of drivers didn't but that is fixable. Stephen Hemminger (2): nbd: constify nla_policy gtp: constify nla_policy drivers/block/nbd.c | 6 +++--- drivers/net/gtp.c | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -- 2.18.0

6 years, 11 months

Data Rate of EGPRS is Too Low

by XINKE ZHANG

Hi all, I have set up the EGPRS network using software bundles (osmo-nitb + osmo-bts-trx + osmo-trx + osmo-pcu + osmo-sgsn + openggsn) based on the USRP B210 platform. Now the cell phone can connect to the EGPRS network, but the network is not stable and the data rate is too low (only about 8kbs). Is this data rate correct? If not, could you pls send me some working config files? Thank you. Best Regards, Xinke

6 years, 11 months

GPRS doesn't work

by weng alexa

Hi all, I set up the EGPRS network using software bundles (osmo-bts-trx + osmo-trx + osmo-pcu + osmo-sgsn + osmo-ggsn + osmo-bsc + osmo-msc + osmo-hlr) based on the USRP B210 platform. Now the cell phone can connect to the EGPRS network, but the phone has no IP address. All the config files are in the attachments, could you help we find what's wrong? Thanks sincerely All of the osmo-pcu's log is like the below: 20180625043250233 DRLCMACMEAS <0007> gprs_rlcmac_meas.cpp:183 DL Bandwitdh of IMSI=xxxxxxxxxxxxxxxx/ TLLI=0xb6ccf813: 190 KBits/s 20180625043250233 DTBFDL <0009> tbf_dl.cpp:863 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Scheduled Ack/Nack polling on FN=2035509, TS=4 20180625043250334 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250334 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250353 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250353 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250353 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250353 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250371 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250371 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250371 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250371 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250389 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250389 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250389 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250389 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250408 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250408 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250408 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250408 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250431 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250431 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250431 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250431 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250449 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250449 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250449 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250449 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250468 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250468 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250468 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250468 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250472 DTBF <0008> tbf_dl.cpp:648 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) changes poll state from GPRS_RLCMAC_POLL_SCHED to GPRS_RLCMAC_POLL_NONE 20180625043250472 DTBF <0008> pdch.cpp:407 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) RX: [PCU <- BTS] Packet Downlink Ack/Nack 20180625043250491 DTBFDL <0009> tbf_dl.cpp:863 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Scheduled Ack/Nack polling on FN=2035566, TS=4 20180625043250588 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250588 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250611 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250611 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250611 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250611 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250629 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250629 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250629 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250630 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250648 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250648 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250648 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250648 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250671 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250671 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250671 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250671 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250690 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250690 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250690 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250690 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250708 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250708 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250708 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250708 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250731 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250731 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250731 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250731 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250737 DTBF <0008> tbf_dl.cpp:648 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) changes poll state from GPRS_RLCMAC_POLL_SCHED to GPRS_RLCMAC_POLL_NONE 20180625043250737 DTBF <0008> pdch.cpp:407 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) RX: [PCU <- BTS] Packet Downlink Ack/Nack 20180625043250750 DTBFDL <0009> tbf_dl.cpp:863 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Scheduled Ack/Nack polling on FN=2035622, TS=4 20180625043250851 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250851 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250880 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250880 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250880 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250880 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250888 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250888 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250888 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250888 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250911 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250911 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250911 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250911 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250930 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250930 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250930 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250930 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250948 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250948 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250948 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250948 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043250971 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043250971 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043250971 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043250971 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251009 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251010 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251010 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251010 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251010 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251010 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251010 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251010 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251011 DTBF <0008> tbf_dl.cpp:648 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) changes poll state from GPRS_RLCMAC_POLL_SCHED to GPRS_RLCMAC_POLL_NONE 20180625043251011 DTBF <0008> pdch.cpp:407 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) RX: [PCU <- BTS] Packet Downlink Ack/Nack 20180625043251031 DTBFDL <0009> tbf_dl.cpp:863 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Scheduled Ack/Nack polling on FN=2035683, TS=4 20180625043251128 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251128 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251151 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251151 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251151 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251151 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251170 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251170 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251170 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251170 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251188 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251188 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251188 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251188 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251211 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251211 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251211 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251211 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251230 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251230 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251230 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251230 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251248 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251248 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251248 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251248 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251271 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 2 (first control TS 4) 20180625043251271 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 3 (first control TS 4) 20180625043251271 DTBF <0008> tbf.cpp:718 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling is already scheduled 20180625043251271 DTBF <0008> tbf.cpp:714 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) Polling cannot be scheduled in this TS 5 (first control TS 4) 20180625043251272 DTBF <0008> tbf_dl.cpp:648 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) changes poll state from GPRS_RLCMAC_POLL_SCHED to GPRS_RLCMAC_POLL_NONE 20180625043251272 DTBF <0008> pdch.cpp:407 TBF(TFI=0 TLLI=0xb6ccf813 DIR=DL STATE=FLOW) RX: [PCU <- BTS] Packet Downlink Ack/Nack 20180625043251290 DRLCMACMEAS <0007> gprs_rlcmac_meas.cpp:183 DL Bandwitdh of IMSI=xxxxxxxxxxxxxxxxxx/ TLLI=0xb6ccf813: 186 KBits/s Part of the osmo-sgsn's log is shown below: 20180625042017231 DMM <0002> gprs_gmm.c:1272 MM(---/ffffffff) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042017231 DMM <0002> gprs_sgsn.c:237 MM(/00000000) Allocated with GEA0 cipher. 20180625042017231 DLGLOBAL <001d> rate_ctr.c:88 validating counter group 0x558216d5ee00(sgsn:mmctx) with 11 counters 20180625042017233 DMM <0002> gprs_gmm.c:556 MM(/e35372d8) <- GPRS IDENTITY REQUEST: mi_type=IMEI 20180625042018409 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042018409 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x8b6c20 CMD=UI DATA 20180625042018410 DMM <0002> gprs_gmm.c:1195 MM(/e35372d8) -> GMM IDENTITY RESPONSE: MI(IMEI)=866049037683470 20180625042018410 DMM <0002> gprs_gmm.c:556 MM(/e35372d8) <- GPRS IDENTITY REQUEST: mi_type=IMSI 20180625042019133 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042019133 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0xa77256 CMD=UI DATA 20180625042019133 DMM <0002> gprs_gmm.c:1195 MM(/e35372d8) -> GMM IDENTITY RESPONSE: MI(IMSI)=xxxxxxxxxxxxxxx 20180625042019133 DMM <0002> sgsn_auth.c:161 MM(xxxxxxxxxxxxxxx/e35372d8) Requesting authorization 20180625042019133 DMM <0002> sgsn_auth.c:220 MM(xxxxxxxxxxxxxxx/e35372d8) Updating authorization (unknown -> accepted) 20180625042019133 DMM <0002> sgsn_auth.c:249 MM(xxxxxxxxxxxxxxx/e35372d8) Got authorization update: state unknown -> accepted 20180625042019133 DMM <0002> gprs_gmm.c:1119 MM(xxxxxxxxxxxxxxx/e35372d8) Authorized, continuing procedure, IMSI=xxxxxxxxxxxxxxx 20180625042019133 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042024027 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042024483 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 341 20180625042024615 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042024615 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042024615 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042024615 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042024615 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042024615 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042024615 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042024615 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042024615 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042025134 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042031136 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042034027 DNS <0010> gprs_ns.c:638 NSEI=1800 Timer expired in mode tns-test (30 seconds) 20180625042034027 DNS <0010> gprs_ns.c:571 NSEI=1800 Tx NS ALIVE (NSVCI=1800) 20180625042034027 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-alive (3 seconds) 20180625042034027 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042034028 DNS <0010> gprs_ns.c:584 NSEI=1800 Tx NS ALIVE_ACK (NSVCI=1800) 20180625042034028 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-test (30 seconds) 20180625042037138 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042037889 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042037889 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x5b3c8d CMD=UI DATA 20180625042037889 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/e35372d8) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042037889 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/e35372d8) Starting MM timer 3350 while old timer 3350 pending 20180625042037889 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042043889 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042044027 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042044616 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042044616 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042044616 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042044616 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042044616 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042044616 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042044616 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042044616 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042044616 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042047034 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042047034 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x75dfce CMD=UI DATA 20180625042047034 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/e35372d8) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042047034 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/e35372d8) Starting MM timer 3350 while old timer 3350 pending 20180625042047034 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042053036 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042054028 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042054484 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 371 20180625042059038 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042102113 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042102113 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x06fa0b CMD=UI DATA 20180625042102113 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/e35372d8) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042102113 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/e35372d8) Starting MM timer 3350 while old timer 3350 pending 20180625042102113 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042104028 DNS <0010> gprs_ns.c:638 NSEI=1800 Timer expired in mode tns-test (30 seconds) 20180625042104028 DNS <0010> gprs_ns.c:571 NSEI=1800 Tx NS ALIVE (NSVCI=1800) 20180625042104028 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-alive (3 seconds) 20180625042104028 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042104028 DNS <0010> gprs_ns.c:584 NSEI=1800 Tx NS ALIVE_ACK (NSVCI=1800) 20180625042104028 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-test (30 seconds) 20180625042104617 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042104617 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042104617 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042104617 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042104617 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042104617 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042104617 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042104617 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042104617 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042108114 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042114030 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042114116 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042120117 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042124030 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042124484 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 401 20180625042124617 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042124617 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042124617 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042124617 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042124617 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042124617 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042124617 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042124617 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042124617 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042126121 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/e35372d8) <- GPRS ATTACH ACCEPT (new P-TMSI=0xe35372d8) 20180625042132125 DMM <0002> gprs_gmm.c:2108 MM(xxxxxxxxxxxxxxx/e35372d8) T3350 expired >= 5 times 20180625042132125 DMM <0002> gprs_gmm.c:313 MM(xxxxxxxxxxxxxxx/e35372d8) Cleaning MM context due to T3350 20180625042132791 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042132791 DLLC <0012> gprs_llc.c:526 LLC RX: unknown TLLI 0xb6ccf813, creating LLME on the fly 20180625042132791 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0xe0b181 CMD=UI DATA 20180625042132791 DMM <0002> gprs_gmm.c:1272 MM(---/ffffffff) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042132791 DMM <0002> gprs_sgsn.c:237 MM(/00000000) Allocated with GEA0 cipher. 20180625042132791 DLGLOBAL <001d> rate_ctr.c:88 validating counter group 0x558216d5ee00(sgsn:mmctx) with 11 counters 20180625042132791 DMM <0002> gprs_gmm.c:556 MM(/f2d9d8dd) <- GPRS IDENTITY REQUEST: mi_type=IMEI 20180625042133968 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042133968 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x607d37 CMD=UI DATA 20180625042133968 DMM <0002> gprs_gmm.c:1195 MM(/f2d9d8dd) -> GMM IDENTITY RESPONSE: MI(IMEI)=866049037683470 20180625042133968 DMM <0002> gprs_gmm.c:556 MM(/f2d9d8dd) <- GPRS IDENTITY REQUEST: mi_type=IMSI 20180625042134028 DNS <0010> gprs_ns.c:638 NSEI=1800 Timer expired in mode tns-test (30 seconds) 20180625042134028 DNS <0010> gprs_ns.c:571 NSEI=1800 Tx NS ALIVE (NSVCI=1800) 20180625042134028 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-alive (3 seconds) 20180625042134028 DNS <0010> gprs_ns.c:584 NSEI=1800 Tx NS ALIVE_ACK (NSVCI=1800) 20180625042134028 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-test (30 seconds) 20180625042134030 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042134685 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042134685 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0xfe7d5b CMD=UI DATA 20180625042134685 DMM <0002> gprs_gmm.c:1195 MM(/f2d9d8dd) -> GMM IDENTITY RESPONSE: MI(IMSI)=xxxxxxxxxxxxxxx 20180625042134685 DMM <0002> sgsn_auth.c:161 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Requesting authorization 20180625042134685 DMM <0002> sgsn_auth.c:220 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Updating authorization (unknown -> accepted) 20180625042134685 DMM <0002> sgsn_auth.c:249 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Got authorization update: state unknown -> accepted 20180625042134685 DMM <0002> gprs_gmm.c:1119 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Authorized, continuing procedure, IMSI=xxxxxxxxxxxxxxx 20180625042134685 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042140686 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042144031 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042144618 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042144618 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042144618 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042144618 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042144618 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042144618 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042144618 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042144618 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042144618 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042146689 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042147289 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042147289 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x939444 CMD=UI DATA 20180625042147289 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/f2d9d8dd) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042147289 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Starting MM timer 3350 while old timer 3350 pending 20180625042147289 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042153290 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042154031 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042154485 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 431 20180625042159292 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042202149 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042202149 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x5b3c8d CMD=UI DATA 20180625042202149 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/f2d9d8dd) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042202149 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Starting MM timer 3350 while old timer 3350 pending 20180625042202149 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042204029 DNS <0010> gprs_ns.c:638 NSEI=1800 Timer expired in mode tns-test (30 seconds) 20180625042204029 DNS <0010> gprs_ns.c:571 NSEI=1800 Tx NS ALIVE (NSVCI=1800) 20180625042204029 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-alive (3 seconds) 20180625042204029 DNS <0010> gprs_ns.c:584 NSEI=1800 Tx NS ALIVE_ACK (NSVCI=1800) 20180625042204029 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-test (30 seconds) 20180625042204031 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042204619 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042204619 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042204619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042204619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042204619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042204619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042204619 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042204619 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042204619 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042208149 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042214031 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042214150 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042216947 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042216947 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x75dfce CMD=UI DATA 20180625042216947 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/f2d9d8dd) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042216947 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Starting MM timer 3350 while old timer 3350 pending 20180625042216947 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042222948 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042224031 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042224486 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 461 20180625042224619 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042224619 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042224619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042224619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042224619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042224619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042224619 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042224619 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042224619 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042228950 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042232086 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042232086 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x06fa0b CMD=UI DATA 20180625042232086 DMM <0002> gprs_gmm.c:1272 MM(xxxxxxxxxxxxxxx/f2d9d8dd) -> GMM ATTACH REQUEST MI(4140627987) type="GPRS attach" 20180625042232086 DMM <0002> gprs_gmm.c:228 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Starting MM timer 3350 while old timer 3350 pending 20180625042232086 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042234029 DNS <0010> gprs_ns.c:638 NSEI=1800 Timer expired in mode tns-test (30 seconds) 20180625042234029 DNS <0010> gprs_ns.c:571 NSEI=1800 Tx NS ALIVE (NSVCI=1800) 20180625042234029 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-alive (3 seconds) 20180625042234029 DNS <0010> gprs_ns.c:584 NSEI=1800 Tx NS ALIVE_ACK (NSVCI=1800) 20180625042234030 DNS <0010> gprs_ns.c:610 NSEI=1800 Starting timer in mode tns-test (30 seconds) 20180625042234032 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042238087 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042244032 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042244090 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042244619 DLGSUP <0027> gsup_client.c:244 GSUP ping callback (connected, got PONG) 20180625042244619 DLGSUP <0027> gsup_client.c:264 GSUP sending PING 20180625042244619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042244619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042244619 DLINP <001f> input/ipa.c:142 127.0.0.1:4222 connected write 20180625042244619 DLINP <001f> input/ipa.c:92 127.0.0.1:4222 sending data 20180625042244620 DLINP <001f> input/ipa.c:138 127.0.0.1:4222 connected read 20180625042244620 DLINP <001f> input/ipa.c:56 127.0.0.1:4222 message received 20180625042244620 DLGSUP <0027> gsup_client.c:201 GSUP receiving PONG 20180625042250092 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042254032 DBSSGP <0011> gprs_bssgp.c:806 BSSGP BVCI=1800 Rx Flow Control BVC 20180625042254487 DGPRS <000f> gprs_sgsn.c:912 Checking for inactive LLMEs, time = 491 20180625042256094 DMM <0002> gprs_gmm.c:437 MM(xxxxxxxxxxxxxxx/f2d9d8dd) <- GPRS ATTACH ACCEPT (new P-TMSI=0xf2d9d8dd) 20180625042302097 DMM <0002> gprs_gmm.c:2108 MM(xxxxxxxxxxxxxxx/f2d9d8dd) T3350 expired >= 5 times 20180625042302097 DMM <0002> gprs_gmm.c:313 MM(xxxxxxxxxxxxxxx/f2d9d8dd) Cleaning MM context due to T3350 20180625042302304 DBSSGP <0011> gprs_bssgp.c:392 BSSGP TLLI=0xb6ccf813 Rx UPLINK-UNITDATA 20180625042302304 DLLC <0012> gprs_llc.c:526 LLC RX: unknown TLLI 0xb6ccf813, creating LLME on the fly 20180625042302304 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0xe0b181 CMD=UI DATA Thanks, Alexa

6 years, 11 months

osmo-pcu build failures on Debian 8.0

by Harald Welte

For quite some time, osmo-pcu has been causing build failures on Debian 8. You can find a build log e.g. at https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… The visible sign is that for some reasson there are additional log lines present in the output of our unit tests, like: [ 127s] TBF(TFI=0 TLLI=0xffeeddcc DIR=DL STATE=FLOW EGPRS) downlink acknowledge [ 127s] TBF(TFI=0 TLLI=0xffeeddcc DIR=DL STATE=FLOW EGPRS) Final ACK received. [ 127s] +DL packet loss of IMSI= / TLLI=0xffeeddcc: 0% [ 127s] TBF(TFI=0 TLLI=0xffeeddcc DIR=DL STATE=FLOW EGPRS) changes state from FLOW to WAIT RELEASE [ 127s] TBF(TFI=0 TLLI=0xffeeddcc DIR=DL STATE=WAIT RELEASE EGPRS) starting timer T3193 [release (DL-TBF)] with 0 sec. 0 microsec, cur_fn=0 where the "+" is the unexpected additional line. Does anyone have any information about why that is? I don't see any related changes recently. -- - 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)

7 years

GTP-U support for a UE with multiple bearers (LTE)

by Shashank Prasad

Hi, I just started exploring the GTP-U module (maintained in the kernel) for LTE. In LTE, a UE can be associated with multiple bearers. This implies that an MS IP address can be associated with multiple TEIDs (one for each bearer). Based on browsing the kernel GTP implementation[1], it looks like the GTP-U (maintained in the kernel) can only support 1 TEID per MS IP address. In which case, the GTP implementation, as is, may NOT be usable by LTE modules. Is this a correct interpretation? - Shashank [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/dr…

7 years, 2 months

GTP-U support for a UE with multiple bearers

by Shashank Prasad

Hi, I just started exploring the GTP-U module (maintained in the kernel) for LTE scenarios. In LTE, a UE can be associated with multiple bearers. This implies that an MS IP address can be associated with multiple TEIDs (one for each bearer). Based on browsing the kernel GTP implementation[1], it looks like the GTP-U (maintained in the kernel) can only support 1 TEID per MS IP address. In which case, the GTP implementation, as is, may NOT be usable by LTE modules. Is it an correct interpretation? - Shashank [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/dr…

7 years, 2 months

Save the Date: OsmoCon 2018 on October 18-19, 2018

by Harald Welte

== OsmoCon 2018 == OsmoCon (Osmocom Conference) 2018 is the technical conference for Osmocom users, operators and developers! We are happy to announce the date of OsmoCon 2018. It has been scheduled on October 18 + 19, 2018 and will happen in Berlin, Germany. For the second time, the Osmocom Conference brings together users, operators and developers of the Osmocom Open Source cellular infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN and others. Join us for two days of presentations and discussions with the main developers behind Open Source Mobile Communications, as well as commercial and non-profit users of the Osmocom cellular infrastructure software. You can find some initial information in our wiki at http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018 which will be updated as more information becomes available. == Call for Participation == We're also at the same time announcing the Call for Participation and call on everyone with experiences to share around the Osmocom member projects to submit talks, workshops, discussions or other proposals. You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp We are particularly looking for contributions about: * updates on features/functionality/status of individual Osmocom projects * success stories on how Osmocom projects are deployed in practice * migration from OsmoNITB to the post-NITB architecture * tutorials / workshops on how to setup / analyze Osmocom projects * statistics, reporting, operations aspects of Osmocom projects * third-party open source utilities to be used with Osmocom projects Looking forward to meeting many existing and new Osmocom users at OsmCon this October! Regards, Harald Welte -- - 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)

7 years, 2 months

Data throughput issues. Increasing throughput.

by Dave Ellis

Hi, I need to increase the throughput through the GTP tunnels to around 9Gb/s. I have two servers and they are connected using two GTP tunnels over a Mellanox 25Gb/s link. Via the tunnels I am seeing a total of 4.2 Gb/s to 4.5 Gb/s using iPerf. If data is sent without the tunnels I see a throughput of around 24.5Gb/s. I have tried various tweaks to improve the throughput over the GTP tunnels and have only made marginal gains. I have tried iPerf 2.0.9 and iPerf3 and see the same results. Wireshark shows the iPerf MTU is reflected in the pcap logs. I have tried changing the txqueuelen on the tunnels, changing osmo-ggsn niceness, network buffer sizes etc. The restriction seems to be osmo-ggsn as that is taking up to 92% CPU on one of the cores when the throughput tests are running. I'm hoping I have made a mistake in the configuration of OsmoGGSN and sgsnemu. -- The servers are running Ubuntu 16.04 desktop. 16GB RAM - 12.6GB free when running throughput tests. Intel E52620v3. Mellanox MCX516A-CCAT network adapter. 25Gb direct attach copper connecting the two servers OsmoGGSN version 1.1.0.75-3e44-dirty. For one of the servers: - Mellanox interface details ens3f0 Link encap:Ethernet HWaddr ec:0d:9a:a0:1d:7c inet addr:172.16.8.1 Bcast:172.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::8f38:33e3:bd46:dd65/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:142373677 errors:0 dropped:0 overruns:0 frame:0 TX packets:157500406 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10000 RX bytes:793825609487 (793.8 GB) TX bytes:879898325287 (879.8 GB) Tunnel interface details S1Utun Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.1.1.2 P-t-P:10.1.1.2 Mask:255.255.255.0 inet6 addr: fe80::b3fc:3d43:b751:bcbf/64 Scope:Link UP POINTOPOINT RUNNING MTU:9000 Metric:1 RX packets:4640412 errors:0 dropped:0 overruns:0 frame:0 TX packets:2272797 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:37729672063 (37.7 GB) TX bytes:118866016 (118.8 MB) X2Utun Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.1.2.2 P-t-P:10.1.2.2 Mask:255.255.255.0 inet6 addr: fe80::6ed8:8a79:b3e9:a51d/64 Scope:Link UP POINTOPOINT RUNNING MTU:9000 Metric:1 RX packets:1824011 errors:0 dropped:0 overruns:0 frame:0 TX packets:3856238 errors:0 dropped:4229 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:95648485 (95.6 MB) TX bytes:31367266755 (31.3 GB) client side iperf server1 iperf3 -c 10.1.2.1 -i1 -t 30 -M8100 -w 2048K -P8 server2 iperf3 -c 10.1.2.1 -i1 -t 30 -M8100 -w 2048K -P8 server1 and 2 iperf server iperf3 -s -i1 osmo-ggsn -c /home/osmo-ggsn.cfg -g 172.16.1.1 contents of osmo-ggsn.cfg ! ! OpenGGSN (0.94.1-adac) configuration saved from vty !! ! log stderr logging filter all 1 logging color 1 logging print category 0 logging timestamp 0 logging level ip info logging level tun info logging level ggsn info logging level sgsn notice logging level icmp6 notice logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp info logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice ! stats interval 5 ! line vty no login ! ggsn X2Uggsn gtp state-dir /tmp gtp bind-ip 172.16.8.1 gtp gtp0-port 3386 gtp gtp1c-port 2123 gtp gtp1u-port 2153 gtp gtp1uremot-port 2153 apn X2U gtpu-mode tun tun-device X2Utun type-support v4 ip prefix dynamic 10.1.2.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 ip ifconfig 10.1.2.2/24 no shutdown default-apn X2U no shutdown ggsn ggsn S1Uggsn gtp state-dir /tmp gtp bind-ip 172.16.8.1 gtp gtp0-port 3387 gtp gtp1c-port 2124 gtp gtp1u-port 2152 gtp gtp1uremot-port 2152 apn S1U gtpu-mode tun tun-device S1Utun type-support v4 ip prefix dynamic 10.1.1.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 ip ifconfig 10.1.1.2/24 no shutdown default-apn S1U no shutdown ggsn sgsnemu -l 127.0.0.2 -r 172.16.8.1 --contexts 1 -a S1U -m 4412345678 -q 0x00000000000b921f --defaultroute --pingcount 0 --gtpteid=8 --gtpversion=1 --gsnuip 172.16.1.1 --enduserip 10.1.1.1 --gtp0port 3387 --gtp1cport 2124 --nsapi 1 sgsnemu -l 127.0.0.3 -r 172.16.8.1 --contexts 1 -a X2U -m 4412345678 -q 0x00000000000b921f --defaultroute --pingcount 0 --gtpteid=3 --gtpversion=1 --gsnuip 172.16.1.1 --enduserip 10.1.2.1 --gtp0port 3386 --gtp1cport 2123 --nsapi 2 Hopefully I have provided enough information. Any ideas on how to increase tunnel throughput? Thanks Dave

7 years, 2 months

Interfering with the GTP-u Kernel module

by Thomas Boros

Hello, I would like to implement a command line tool, which will be able to open / close , read / write to gtp tunnels. I was able to install the libgtpnl library, but due to lack of documentation I have no idea where to start. Is there some sort of documentation available for this library? I need to be able to create and delete tunnels without the GTP-C communication, so just basic command line tool like create-gtp-tunnel + arguments like IPs, version and teid. The GTP-U tunnels must be kernel based. I have the latest kernel with the gtp kernel module loaded. Any help is appreciated. Thank you, Tomas

7 years, 4 months

Problem when building OsmoSGSN

by XINKE ZHANG

Hi all, I built OsmoSGSN with the these following instructions. <build instructions> git clone git://git.osmocom.org/osmo-sgsn cd osmo-sgsn autoreconf -fi ./configure --enable-iu make -j5 make check make install sudo ldconfig <build instructions> And no error came out during building process, but no “osmo-sgsn” executable was found. Pls help me. Thank you in advance. Best Regards, Xinke

7 years, 4 months

← Newer
1
...
19
20
21
22
23
24
25
...
48
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

osmocom-net-gprs