aboutsummaryrefslogtreecommitdiffstats
path: root/ggsn_tests
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2018-04-26 10:21:49 +0200
committerHarald Welte <laforge@gnumonks.org>2018-04-26 09:09:32 +0000
commitd2394e9032dbc31d023b15038b48282e8f6d3936 (patch)
treee00f2988fc3ba59684146b38d2a82fde75bccdcd /ggsn_tests
parent3e0b039c56b2ac4b65fd830f1762d6420580fb01 (diff)
ggsn: Disable GTP-U tx sequence number by default
GTP-U transmit sequence numbers are entirely optional and probably don't serve any real purpose in real-world deployments. While OsmoGGSN in userspace implements support for it, the kernel GTP-U implementation doesn't. This means a number of tests fail against kernel GTP-U only for that reason. Let's switch all tests to disable GTP-U sequence numbers, and only enable it in one specific test. This way, we can execute the tests also against kernel GTP-U. Related: OS#3215 Change-Id: I666f5276749ef6a1a4dc170a3b9a747f626f6b2c
Diffstat (limited to 'ggsn_tests')
-rw-r--r--ggsn_tests/GGSN_Tests.ttcn2
1 files changed, 1 insertions, 1 deletions
diff --git a/ggsn_tests/GGSN_Tests.ttcn b/ggsn_tests/GGSN_Tests.ttcn
index cb6aabf9..d0996810 100644
--- a/ggsn_tests/GGSN_Tests.ttcn
+++ b/ggsn_tests/GGSN_Tests.ttcn
@@ -93,7 +93,7 @@ module GGSN_Tests {
var uint16_t g_d_seq_nr;
port TELNETasp_PT GGSNVTY;
- var boolean use_gtpu_txseq := true;
+ var boolean use_gtpu_txseq := false;
}
private function f_init_vty() runs on GT_CT {