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
3 files changed
tree: 63a1847334f87b637f57b46056ef131c381c0355
  1. contrib/
  2. debian/
  3. doc/
  4. include/
  5. m4/
  6. src/
  7. tests/
  8. .gitignore
  9. .gitreview
  10. .mailmap
  11. AUTHORS
  12. configure.ac
  13. COPYING
  14. git-version-gen
  15. Makefile.am
  16. osmoappdesc.py
  17. README.md
  18. README.vty-tests
  19. TODO-RELEASE
README.md

About osmo-gbproxy

osmo-gbproxy is a proxy for the Gb interface within the 3GPP GERAN (GPRS/EDGE RAN) architecture. It is part of the Osmocom Open Source Mobile Communications projects.

It allows you to aggregate many Gb links/connections into one. It also has the ability to convert between different Gb interface protocol stacking, such as from Gb-over-FrameRelay to Gb-over-IP.

Until 2021 it used to be part of the osmo-sgsn git repository, and before that (until 2017) part of openbsc.git

Homepage and Issue Tracker

Find the issue tracker and wiki online at https://osmocom.org/projects/osmo-gbproxy and https://osmocom.org/projects/osmo-gbproxy/wiki, respectively.

Documentation

You can find the user manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-usermanual.pdf and the VTY reference manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-vty-reference.pdf.