Bug #5092
ns2: Restricting an NSE with ip-sns-bind still considers all binds when creating NSVCs
Start date:
03/24/2021
Due date:
% Done:
100%
Spec Reference:
Description
The SNS-CONFIG only contain the correct Endpoints as can be seen in VTY. However, all configured binds seem to be used when creating the mesh of NSVCs:
OsmoGbProxy# show ns nsei 34 NSEI 00034: UDP, ALIVE FSM Instance Name: 'GPRS-NS2-SNS-SGSN(NSE00034-SNS)[0x5639244dc250]', ID: 'NSE00034-SNS' Log-Level: 'DEBUG', State: 'CONFIGURED' Timer: 4 Maximum number of remote NS-VCs: 8, IPv4 Endpoints: 1, IPv6 Endpoints: 0 Local IPv4 Endpoints: 192.168.0.180:1234, Signalling Weight: 1, Data Weight: 1 Remote IPv4 Endpoints: 192.168.0.240:1234, Signalling Weight: 100, Data Weight: 100 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1231<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1232<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1233<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1235<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1236<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1237<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1238<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1239<>[192.168.0.240]:1234 NSVCI none: UNBLOCKED DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1234<>[192.168.0.240]:1234
The config looks roughly like this:
ns bind udp foo-1231 listen 192.168.0.180 1231 ip-sns signalling-weight 1 data-weight 1 [...] nse 31 ip-sns-role-sgsn ip-sns-bind foo-1231 [...]
Associated revisions
gprs_ns2_sns: Don't create NS-VCs for binds outside the NSE
We may very well have any number of binds configured, but which
are not part of the current NSE. When creating the "full mesh" of
NS-VCs after SNS-CONFIG, we must only iterate over those binds that
are part of the NSE (or 'ipa-sns-default bind' in cae of SGSN role),
but not over all the other binds that may exist in the system.
Closes: OS#5092
Change-Id: Ida361fa02ad1d86844d54c8f0664c996ed28e30a
History
#2 Updated by laforge 29 days ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset libosmocore|21ce1a39fb78426a1ab80273fbc5e0adeb7bda35.
gprs_ns2_sns: Don't create NS-VCs for binds outside the NSE
We may very well have any number of binds configured, but which
are not part of the current NSE. When creating the "full mesh" of
NS-VCs after SNS-CONFIG, we must only iterate over those binds that
are part of the NSE (or 'ipa-sns-default bind' in cae of SGSN role),
but not over all the other binds that may exist in the system.
Closes: OS#5092
Change-Id: Ida361fa02ad1d86844d54c8f0664c996ed28e30a