Daniel Willmann dc763fdf39 gbproxy: Avoid sending STATUS on unexpected BLOCK_ACK ... Handle SGSN BVCs that are gone from the BSS differently. The previous patch removed the gbproxy_bvc on the SGSN-side after it was gone on the BSS-side. This caused a STATUS response to BVC_BLOCK_ACK messages that should be valid. Instead of removing the BVC this patch marks it as inactive so we can still handle BVC_BLOCK_ACK correctly, but ignore other messages - especially BVC_RESET from the SGSN. Related: SYS#5628. OS#5236 Change-Id: Ic9f34a27412d6e15ca1198ee140f66a076b5c6b6		2021-09-29 11:35:06 +02:00
..
osmocom	gbproxy: Avoid sending STATUS on unexpected BLOCK_ACK	2021-09-29 11:35:06 +02:00
Makefile.am	=== Split osmo-gbproxy from osmo-sgsn ===	2021-01-29 16:57:29 +01:00