Bug #67
gb_proxy keeps stale PTP-BVCI <-> NSVCI mappings
Start date:
Due date:
% Done:
0%
Spec Reference:
Description
When BVCI A first establishes a connection through NSVCI/NSEI B, then later establishes a connection through NSVCI/NSEI A, gb_proxy permanently keeps a stale proxy mapping associating BVCI A with NSVCI B.
This causes all downlink messages from the SGSN to be routed still through NSVCI B, despite now NSVCI A being the correct one.
History
#1 Updated by laforge over 8 years ago
- Status changed from New to In Progress
#2 Updated by laforge almost 5 years ago
- Priority changed from High to Normal
#3 Updated by laforge over 4 years ago
- Status changed from In Progress to New
#4 Updated by laforge over 4 years ago
- Priority changed from Normal to Low
#5 Updated by laforge about 3 years ago
- Project changed from OpenBSC to OsmoSGSN
- Category deleted (
osmo-gb_proxy)
#6 Updated by laforge about 3 years ago
- Category set to osmo-gbproxy
#8 Updated by laforge about 2 months ago
- Assignee changed from laforge to daniel
- Priority changed from Low to Normal
#10 Updated by daniel 7 days ago
Yeah, the BVCI <-> NSVCI mapping doesn't even make sense now that one NSE could have multiple NSVCs.
Not sure if we have a similar issue in the new gbproxy or if it is already taken care of. Some code related to this got #if 0'd in rx_bvc_reset_from_bss() (gbproxy.c line 793).
