The Iu/UMTS specific test cases in ttcn3-msc-test expect no
encryption in Security Mode Command by default (only integrity),
while osmo-msc would permit both UEA1 and UEA2 unless configured
explicitly. This causes the related test cases to fail.
A similar change was merged to osmo-ttcn3-hacks, updating the
osmo-msc.cfg in there, however the actual configuration file
that is used to execute test cases on Jenkins was not updated.
Change-Id: I43f80e3fbd73be21fb89006e16de0e1df9ba03f5
Related: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/26389
Fixes: OS#5333
it has been deprecated in libosmocore.git 2.5 years ago:
commit 7e0686c6b4b456ec4e6e15689694b1bcf96c301f
Author: Neels Hofmeyr <neels@hofmeyr.de>
Date: Mon Sep 10 20:58:52 2018 +0200
Change-Id: Ia6946fae497319a894d4e664ac8642340620822e
When introducing IPv6 support, we map the third digit of the IPv4
address (X) to the 6th byte of an IPv6 prefix "fd02:db8:X::/64"
However, the docker daemon seems to use "fd02:db8:1::/64" internally
for its default network, so creating a docker network with the same
IP address is failing.
Let's move the MSC test suite to another sub-net (1->20) to avoid
related problems.
Change-Id: I9c5f9b96d5523eae09f3f2e6c813e9e0d047f9ab
Unfortunately, we have to revert a part of change [1], because it
broke ttcn3-msc-test-latest. The reason is that the latest release
of osmo-msc does not support 'timer vlr T3212 30'.
Change-Id: Iaeb6f1ffee9286394654bc3cf9d985ace7829110
Configure each osmo-* program to send GSMTAP log output to the IP of the
docker container, which runs the testsuite (and therefore runs tcpdump).
Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html
Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
We need to update the MSC_Tests.cfg as well as the osmo-stp.cfg
to provsion a virtual RNC link. As the new RNC uses routing key 2,
we shift the MSC routing key to 3.
Change-Id: I10a249b1a851436fd3c20face6ccc94b304bd3e4
In the past, MM INFO transmission was broken, so the tests were
written without expecting it. Now, the bug in osmo-msc has been
fixed.
With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg
MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots
of test failures.
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.
The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks. This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.
If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.