aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-bscnat-test/BSCNAT_Tests.cfg
AgeCommit message (Collapse)AuthorFilesLines
2019-05-27ttcn3-bscnat: Prepare cfgs for VTY & Osmux supportPau Espin Pedrol1-0/+1
* 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-23ttcn3-bscnat-test: Use unique sub-network 172.18.15.0/24Harald Welte1-5/+5
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
2018-11-09Add ttcn3-bscnat-test docker imageDaniel Willmann1-0/+30
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