Actions
Bug #3178
closedgbproxy: failed to parse invalid BSSGP-UNITDATA message
Start date:
04/16/2018
Due date:
% Done:
0%
Spec Reference:
Description
Today while checking log output (debug all) of osmo-gbproxy 8343b4adbbe9afd4294232429696ee9736ec1004 in a testing/production set up:
<000f> gb_proxy_patch.c:154 Patching TLLIs: Replacing e5225438 -> da1d5ada <000f> gb_proxy.c:767 NSEI=110 proxying BTS->SGSN (NS_BVCI=9108, NSEI=9108) <0012> gprs_llc_parse.c:82 LLC SAPI=9 C U GEA? IOV-UI=0x000000 FCS=0x62a1a7 CMD=UI DATA <0012> gprs_gb_parse.c:408 Got LLC message, CRC: 62a1a7 (computed 62a1a7) <000f> gprs_gb_parse.c:535 LLC: Got TLLI e5225438, BSSGP RAID 274-8-4120-0 <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = e5225438, assigned = 00000000, net_vld = 1, bss_vld = 1}, e5225438) <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = da1d5ada, assigned = 00000000, net_vld = 1, bss_vld = 1}, da1d5ada) <000f> gb_proxy_patch.c:154 Patching TLLIs: Replacing e5225438 -> da1d5ada <000f> gb_proxy.c:767 NSEI=110 proxying BTS->SGSN (NS_BVCI=9108, NSEI=9108) <000f> gprs_gb_parse.c:535 BSSGP: Got BSSGP RAID 274-8-4120-0, BSSGP PTMSI f3687732, IMSI 274080000004803 <000f> gb_proxy_patch.c:184 Patching BSSGP P-TMSIs: Replacing f3687732 -> e155cfea <000f> gb_proxy.c:1080 NSEI=9108(SGSN) BSSGP PAGING routing by RAI to peer BVCI=9108 <000f> gb_proxy.c:791 NSEI=9108 proxying SGSN->BSS (NS_BVCI=0, NSEI=110) <0012> gprs_llc_parse.c:82 LLC SAPI=1 C U GEA? IOV-UI=0x000000 FCS=0x38436c CMD=UI DATA <0012> gprs_gb_parse.c:408 Got LLC message, CRC: 38436c (computed 38436c) <000f> gb_proxy.c:575 NSEI=110(BSS) patching: failed to parse invalid BSSGP-UNITDATA message <000f> gprs_gb_parse.c:535 BSSGP-UNITDATA: Got TLLI 00000000, BSSGP RAID 274-8-4120-0 <000f> gb_proxy.c:579 NSEI=110(BSS) invalid message was: [L2]> 00 00 23 94 01 e1 55 cf ea 00 00 04 08 88 72 f4 80 10 18 00 9c 40 00 80 0e 00 06 01 c0 41 6c 43 38 <0012> gprs_llc_parse.c:82 LLC SAPI=9 C U GEA? IOV-UI=0x000000 FCS=0xa65d4d CMD=UI DATA <0012> gprs_gb_parse.c:408 Got LLC message, CRC: a65d4d (computed a65d4d) <000f> gprs_gb_parse.c:535 LLC: Got TLLI e5225438, BSSGP RAID 274-8-4120-0 <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = e5225438, assigned = 00000000, net_vld = 1, bss_vld = 1}, e5225438) <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = da1d5ada, assigned = 00000000, net_vld = 1, bss_vld = 1}, da1d5ada) <000f> gb_proxy_patch.c:154 Patching TLLIs: Replacing e5225438 -> da1d5ada <000f> gb_proxy.c:767 NSEI=110 proxying BTS->SGSN (NS_BVCI=9108, NSEI=9108) <0012> gprs_llc_parse.c:82 LLC SAPI=9 C U GEA? IOV-UI=0x000000 FCS=0x2bbfe2 CMD=UI DATA <0012> gprs_gb_parse.c:408 Got LLC message, CRC: 2bbfe2 (computed 2bbfe2) <000f> gprs_gb_parse.c:535 LLC: Got TLLI e5225438, BSSGP RAID 274-8-4120-0 <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = e5225438, assigned = 00000000, net_vld = 1, bss_vld = 1}, e5225438) <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = da1d5ada, assigned = 00000000, net_vld = 1, bss_vld = 1}, da1d5ada) <000f> gb_proxy_patch.c:154 Patching TLLIs: Replacing e5225438 -> da1d5ada <000f> gb_proxy.c:767 NSEI=110 proxying BTS->SGSN (NS_BVCI=9108, NSEI=9108) <0012> gprs_llc_parse.c:82 LLC SAPI=9 R U GEA? IOV-UI=0x000000 FCS=0x376834 CMD=UI DATA <0012> gprs_gb_parse.c:408 Got LLC message, CRC: 376834 (computed 376834) <000f> gprs_gb_parse.c:535 LLC: Got TLLI da1d5ada, IMSI 274085000030459 <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = da1d5ada, assigned = 00000000, net_vld = 1, bss_vld = 1}, da1d5ada) <000f> gb_proxy_tlli.c:317 gbproxy_validate_tlli({current = e5225438, assigned = 00000000, net_vld = 1, bss_vld = 1}, e5225438) <000f> gb_proxy_patch.c:154 Patching TLLIs: Replacing da1d5ada -> e5225438
So it seems there are some messages we are not handling correctly.
Actions