Project

General

Profile

Bug #3626

LAPDm code pulls both 'l1h' and 'l2h' of msgb

Added by fixeria 2 months ago. Updated 14 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
libosmogsm
Target version:
-
Start date:
10/04/2018
Due date:
% Done:

0%

Spec Reference:

Description

In some cases, it's required to keep some data before the actual MAC-block, e.g. in order to indicate
the FDMA/TDMA info (frame number, ARFCN, etc.) to the upper layers, but the current implementation
doesn't allow this, because it calls msgb_pull_to_l3() stripping all headers. In other words,
when a message buffer is being passed through the current LAPDm code, everything before the
data frame is getting lost.

History

#1 Updated by laforge 2 months ago

you can consider using the msgb->cb for this?

#2 Updated by fixeria 14 days ago

you can consider using the msgb->cb for this?

Possible but not flexible. In case of OsmocomBB, I would like to keep the whole 'l1ctl_info_dl' header.
What is the purpose / reason of stripping both 'l1h' and 'l2h' message parts out?

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)