Bug #5788
closedPossible regression with TTCN3 8.2.0
0%
Description
In Docker/Jenkins we use TTCN-3 8.0.0 while my Debian machine is at 8.2.0.
When running the ttcn3 gbproxy tests I noticed that some messages that were generated are corrupted:
Wed Nov 23 16:38:01 2022 DGPRS tlv_parser.c:728 NSE(00101/SGSN)-BVC(20011/??) BSSGP DL-UNITDATA: TLV parser error -2
One example is TC_dl_unitdata where the LLC_PDU seems to be encoded as bf 02 00 instead of 0e 80 (see the first DL_UNITDATA in each pcap trace for comparison no.969 vs. no.1885).
Files
Updated by fixeria about 1 year ago
Hi Daniel,
I am using v8.2.0 since it was tagged (in May 2022). No regressions seen so far.
I am mostly running ttcn3-{bsc,bts,pcu}-tests, will try running the gbproxy tests.
Updated by laforge about 1 year ago
FYI, I can reproduce the issue 1:1 on my debian unstable with titan 8.2.0
Updated by fixeria about 1 year ago
fixeria wrote in #note-1:
I am mostly running ttcn3-{bsc,bts,pcu}-tests, will try running the gbproxy tests.
Problem reproduced.
Updated by fixeria about 1 year ago
fixeria wrote in #note-1:
I am using v8.2.0 since it was tagged (in May 2022). No regressions seen so far.
The TC_dl_unitdata passes for me after upgrading titan to v8.3.0 (95e50c02f).
While looking into this, I submitted a couple of patches:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30285 library/Osmocom_Gb_Types: fix wrong IEI in ts_BSSGP_LLC_PDU [NEW]
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30286 {sgsn,gbproxy}: do not link non-existent TCCConversion.hh [NEW]
