summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHarald Welte <laforge@osmocom.org>2021-01-18 18:52:49 +0100
committerHarald Welte <laforge@osmocom.org>2021-01-18 18:55:59 +0100
commitf3f2e25864ff6858abb7e1d47e75551e2a4671fc (patch)
tree23c3e5e5f29f61007f6323a5adefa0ae9088587d
parente393c1f7c660aac76ee2f33f86a452edcbc57441 (diff)
gbproxy: Use separate NS-VC for data / signalling on SGSN sidelaforge/os4953
As we know, many production deployments have SGSN architectures with clear control / user plane split. In such situations, IP-SNS of the SGSN informs us of two (classes of) IP endpoints: some that have control_weight > 0 and data_weight 0 some that have control_weight 0 and data_weight > 0 Let's adjust the GBProxy_Tests.ttcn to use such a configuration for each of the two simulated SGSNs. Change-Id: If0e404bdf2c30a5e18748695608611be83f61109 Closes: OS#4953
-rw-r--r--gbproxy/GBProxy_Tests.ttcn26
1 files changed, 26 insertions, 0 deletions
diff --git a/gbproxy/GBProxy_Tests.ttcn b/gbproxy/GBProxy_Tests.ttcn
index 39d7432f..2fa1670e 100644
--- a/gbproxy/GBProxy_Tests.ttcn
+++ b/gbproxy/GBProxy_Tests.ttcn
@@ -73,6 +73,19 @@ modulepar {
}
},
nsvci := 101
+ }, {
+ provider := {
+ ip := {
+ address_family := AF_INET,
+ local_udp_port := 7770,
+ local_ip := "127.0.0.10",
+ remote_udp_port := 23000,
+ remote_ip := "127.0.0.1",
+ data_weight := 1,
+ signalling_weight := 0
+ }
+ },
+ nsvci := 201
}
}
@@ -94,6 +107,19 @@ modulepar {
}
},
nsvci := 102
+ }, {
+ provider := {
+ ip := {
+ address_family := AF_INET,
+ local_udp_port := 8880,
+ local_ip := "127.0.0.11",
+ remote_udp_port := 23000,
+ remote_ip := "127.0.0.1",
+ data_weight := 1,
+ signalling_weight := 0
+ }
+ },
+ nsvci := 202
}
}
}