Neels Hofmeyr 2f5a5b689c fix ttcn3-bsc-test: osmo-bsc.cfg: add mgw IP ... The osmo-bsc-main docker container is run in a separate docker container and cannot reach the virtual MGW set up by the ttcn3-bsc-tests. From ttcn3-bsc-tests/jenkins.sh it is clear that the tests are run at IP 172.18.2.203. Add this as the 'mgw remote-ip' setting in ttcn3-bsc-tests/osmo-bsc.cfg. This fixes the first half of the disconnect between BSC and virtual MGW in this docker setup. The second half is I3038481ed0bba1084b63dc6a6d2ff6e970100890. Change-Id: Ib53f000ec7e717b14a3e5df6e803d3d0950b937f		2018-03-20 00:42:45 +01:00
..
.release	add ttcn3-bsc-test container with osmo-bsc test suite	2017-12-17 17:21:04 +01:00
BSC_Tests.cfg	Add *.control to the [EXECUTE] statement of all ttcn3 test suites	2018-03-13 13:26:51 +00:00
Dockerfile	ttcn*test: use log_merge.sh to generate per-testcase merged logs	2018-03-18 13:33:39 +00:00
Makefile	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
jenkins.sh	ttcn3-bsc-test: Fix location of respawn.sh script	2018-03-19 07:47:10 +00:00
osmo-bsc.cfg	fix ttcn3-bsc-test: osmo-bsc.cfg: add mgw IP	2018-03-20 00:42:45 +01:00
osmo-stp.cfg	bsc/msc test: Make sure we create text log files	2018-02-06 20:22:39 +01:00