osmocom
/
libosmocore
mirror of https://gerrit.osmocom.org/libosmocore
11
0
Fork 1
Code Issues Releases Wiki Activity
libosmocore/tests/lapd/lapd_test.ok

22 lines
589 B
Plaintext
Raw Normal View History

lapdm: Create a simple test case to transmit data between both ends This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.
2011-12-11 19:25:12 +00:00
I do some very simple LAPDm test.
Establishing link.
ms_to_bts_l1_cb: MS(us) -> BTS prim message
bts_to_ms_tx_cb: MS->BTS(us) message 29
lapd_test: Look at the content of LAPD messages and compare them Verify the output, accept two known errors in the generation of it.
2011-12-11 23:29:50 +00:00
BTS: Verifying CM request.
lapdm: Create a simple test case to transmit data between both ends This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.
2011-12-11 19:25:12 +00:00
Confirming
ms_to_bts_tx_cb: BTS->MS(us) message 9
lapd_test: Look at the content of LAPD messages and compare them Verify the output, accept two known errors in the generation of it.
2011-12-11 23:29:50 +00:00
MS: Verifying incoming primitive.
lapdm: Create a simple test case to transmit data between both ends This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.
2011-12-11 19:25:12 +00:00
Sending back to MS
lapdm: Make sure that the msgb_l3len(msg) == length... This code should not play with the internals of the msgb like this, this code got introduced in af48bed55607931307 and is breaking the osmo-bts usecase of forwarding an RSL message. Add a test case that fails without the new code. I would prefer if we could get rid of the manipulating the msgb like this, it is prone to errors like this one.
2012-01-12 22:12:28 +00:00
ms_to_bts_tx_cb: BTS->MS(us) message 12
MS: Verifying incoming MM message: 3
lapdm: Create a simple test case to transmit data between both ends This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.
2011-12-11 19:25:12 +00:00
ms_to_bts_l1_cb: MS(us) -> BTS prim message
Sending back to BTS
ms_to_bts_l1_cb: MS(us) -> BTS prim message
bts_to_ms_tx_cb: MS->BTS(us) message 14
lapd_test: Look at the content of LAPD messages and compare them Verify the output, accept two known errors in the generation of it.
2011-12-11 23:29:50 +00:00
BTS: Verifying dummy message.
lapd: Check in rslms_rx_rll() if lapdm context was initialized earlier This was found while implementing handover on a sysmobts. When we receive a channel release request for a channel that was never really activated (set_lapdm_context() was not called) we segfault in lapd_recv_dlsap(). We now return early with -EINVAL in rslms_rx_rll() if we receive a message that assumes set_lapdm_context() was already called. These are: * RSL_MT_UNIT_DATA_REQ * RSL_MT_DATA_REQ * RSL_MT_SUSP_REQ * RSL_MT_REL_REQ A test case was added to trigger the issue.
2012-12-25 22:15:50 +00:00
I test RF channel release of an unestablished channel.
lapdm: Create a simple test case to transmit data between both ends This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.
2011-12-11 19:25:12 +00:00
Success.