Project

General

Profile

Actions

Bug #4891

open

gbproxy2: Implement processing of BVC-Flow-Control via BVC FSM

Added by laforge almost 2 years ago. Updated about 1 year ago.

Status:
Stalled
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/08/2020
Due date:
% Done:

90%

Spec Reference:

Description

This is a FIXME in the new post-rewrite, pool-capable gbproxy code base


Files

flow-control-50.pcapng flow-control-50.pcapng 1.97 KB laforge, 12/12/2020 06:15 PM

Related issues

Related to osmo-gbproxy - Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling)Resolveddaniel03/29/2020

Actions
Actions #1

Updated by laforge almost 2 years ago

  • Related to Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling) added
Actions #2

Updated by laforge almost 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30
Actions #3

Updated by laforge almost 2 years ago

  • % Done changed from 30 to 80

Initial impleemntatin in https://gerrit.osmocom.org/c/osmo-sgsn/+/21616 together with https://gerrit.osmocom.org/c/libosmocore/+/21611

We still need to adjust the actual values, i.e. if the BSS advertiseds 1 Mbps overall bucket leak rate, then each SGSN should probably only get part of that, i.e. half in case of 2 SGSN. Possibly with some kind of overcommittment?

Actions #5

Updated by laforge almost 2 years ago

splitting / dividing the advertised capacity is implemented in https://gerrit.osmocom.org/c/osmo-sgsn/+/21696

There is no automatic testing yet for this feature, but it has been manually verified, as can be seen in attached pcap file (two SGSN with each 50% of the capacity)

Actions #6

Updated by laforge about 1 year ago

  • Status changed from In Progress to Stalled
  • Assignee changed from laforge to daniel
  • Priority changed from Urgent to Normal

just the test is missing

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)