From 2e78f900cfd5d62f885900d1c58b1d1e6bb79756 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sat, 1 Jun 2019 11:44:27 +0200 Subject: lapdm: Don't truncate L3 payload at 200 bytes length 3GPP TS 04.06 is quite clear that the [segmented] L3 payload can be as long as 251 bytes. Our libosmocore lapdm implementation truncated already at 200 bytes :( Change-Id: I6769986f27dda1d429ed7b2e32c36d34663acba9 Closes: OS#4035 --- src/gsm/lapdm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gsm/lapdm.c b/src/gsm/lapdm.c index d76175bf..f1651d6d 100644 --- a/src/gsm/lapdm.c +++ b/src/gsm/lapdm.c @@ -136,7 +136,7 @@ static void lapdm_dl_init(struct lapdm_datalink *dl, { memset(dl, 0, sizeof(*dl)); dl->entity = entity; - lapd_dl_init(&dl->dl, 1, 8, 200); + lapd_dl_init(&dl->dl, 1, 8, 251); /* Section 5.8.5 of TS 04.06 */ dl->dl.reestablish = 0; /* GSM uses no reestablish */ dl->dl.send_ph_data_req = lapdm_send_ph_data_req; dl->dl.send_dlsap = send_rslms_dlsap; -- cgit v1.2.3