summaryrefslogtreecommitdiffstats
path: root/tests/lapd
diff options
context:
space:
mode:
authorAndreas.Eversberg <jolly@eversberg.eu>2012-01-10 13:02:01 +0100
committerSylvain Munaut <tnt@246tNt.com>2012-01-10 13:02:01 +0100
commit301f01e938e72423079afe1a1836937053481fd6 (patch)
tree21c94408582bc542f1384fb7e5efb24cb686f8da /tests/lapd
parent4b6bc3b4b562ec6faf4f8fd9a31457c49ecac748 (diff)
libosmocore/lapd: Fixed handling of sequence errors at lapd_core.c
If a sequence error is received, the N(R) variable must still be used to acknowledge previously transmitted frames. If there are two subsequent sequence errors received, ignore it. (Ignore every second subsequent error.) This happens if our reply with the REJ is too slow, so the remote gets a T200 timeout and sends another frame with a sequence error. Test showed that replying with two subsequent REJ messages could the remote L2 process to abort. Replying too slow shouldn't happen, but may happen over serial link between BB and LAPD. Written-by: Andreas.Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
Diffstat (limited to 'tests/lapd')
0 files changed, 0 insertions, 0 deletions