Notably LCS tests are still disabled, just routing BSSMAP-LE/SCCP via STP to
the virtual SMLC is now possible.
Change-Id: Ic296291886ce18fd3ff34d45c519de605ba827cc
This only enables ttcn to be able to connect multiple MSCs. To be able to use
this in the BSC_Tests, osmo-bsc.cfg needs adjusting in an upcoming patch; tests
using this are in osmo-ttcn3-hacks I21cbab193cd0de2e5692665442eae113d5f61904.
Depends: Ibb36695b7c31f7b04eec6c5d59522fc0779b3c2f (osmo-ttcn3-hacks)
Change-Id: I1986e4ef43beee161c82193694421b56136c1afe
Since libosmo-sccp.git 89407619a31a4332bdb59e7921b99a29b7d6e00c it is
not allowed to use routing ctx != 0 for IPA AS.
Change-Id: If3e883aa988ffa1686f1363d5d5d4dbb21ce36c7
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
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.
Neels Hofmeyr
Pau Espin
Oliver Smith
Harald Welte