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.