Commit Graph

3 Commits

Author SHA1 Message Date
Pau Espin 808801a9fa ttcn3-bscnat: Prepare cfgs for VTY & Osmux support
* Adding "osmux on" for each BSC will be required to enable Osmux later
on, but still it doesn't change behavior now because Osmux must be
enabled globally too (will be done through VTY).

* Set up correct bind and remote IP addr to have VTY working later on.

* Use extended timestamp to have subsecond accuracy to match with pcap
easily.

Change-Id: I794a17bdeaff9ab9316d7a6acb1e58dfd815b645
2019-05-27 18:06:06 +00:00
Harald Welte 317aba0226 ttcn3-bscnat-test: Use unique sub-network 172.18.15.0/24
For some reason, the bscnat tests were using the same subnet as the
sip-connector tests, causing address clashes when trying to execute
both test suites simultaneously:

+ echo Creating network ttcn3-sip-test
Creating network ttcn3-sip-test
+ docker network create --internal --subnet 172.18.11.0/24 ttcn3-sip-test
Error response from daemon: Pool overlaps with other one on this address space

Change-Id: I62b01b4b291ed9d729139fcf9b0102459e7f5a6a
2019-05-23 16:00:26 +02:00
Daniel Willmann 6870d87345 Add ttcn3-bscnat-test docker image
Run the bscnat ttcn3 tests in docker. This uses the osmo-nitb-master
image since osmo-bsc_nat is built there as well.

Change-Id: Ibeebb0325d3d1976225666eb28db0741df2e66f0
2018-11-09 17:22:05 +01:00