Commit Graph

8 Commits

Author SHA1 Message Date
Alexander Couzens 26003afcbc make osmo-gbproxy.cfg in ttcn3-gbproxy and ttcn3-gbproxy-fr to look similiar
Reduces human error when changing the configruation for both
cases.

Change-Id: I807589cc04f23d483695467320d34d79eaf5d290
2021-01-12 12:20:24 +01:00
Alexander Couzens 460e3070d3 ttcn3-gbproxy-test-fr: fix SNS ip address
Change-Id: Iba5aee47fb237884d4b0238b9cef4e2370e7ce09
2021-01-12 12:20:15 +01:00
Alexander Couzens 663c77203b gbproxy-fr: Enable IP-SNS towards SGSN
Change-Id: Id59cc404c355a3f494ad60be8d3a499b217084ec
2021-01-11 22:50:59 +01:00
Daniel Willmann da8c47ecb5 ttcn3-gbproxy-test: Fix osmo-gbproxy config
Change-Id: If6fd41d0cecb807f002d87e18d4b0d80f41977ef
2021-01-05 18:48:46 +01:00
Harald Welte a6fc3bf44c osmo-gbproxy: Change config file to comply with change in upstream
In osmo-sgsn Change-Id Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e we
have changed the config file syntax and must adjust here accordingly.

Change-Id: I8770baac2298ee9a71d7428ea30600751783b4f9
Depends: osmo-sgsn Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e
2020-12-30 00:15:25 +01:00
Harald Welte 233d37ee88 ttcn3-gbproxy-test-fr: Fix hdlcnet device names
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we introduced
the wrong hdlcnetX device names.  We must use each devoce only once,
rather than trying to use hdlcnet1..4 twice.

Change-Id: I56f75995fe94b46b0210de2a4f83e384b4e4ca4f
2020-12-09 19:28:51 +01:00
Daniel Willmann 2689304aa5 ttcn3-gbproxy-test-fr: Catch up with config changes
Change-Id: I80de01c96185c60fe2de7a8ffa9daed2669658e1
Related: SYS#5226
Depends: I698a932b3dc78c776e9350283109463bcdc40e6b (osmo-ttcn3-hacks)
2020-12-04 20:09:04 +01:00
Harald Welte b83c28fc34 Add ttcn3-gbproxy-test-fr for FR related testing
Testing FR support in osmo-gbproxy is a bit more complicated
as it involves the "hdlc" net-devices privded by the hdlc_fr.ko
kernel module.

So we need to
* run on a host with actual hdlc net-devices (e.g. dahdi_dyamic_loc)
* move those net-devices into the containers after starting them
* wait for the net-devices to appear in the containers before starting
  either gbproxy or the test suite

Change-Id: Id4b52877db53cb6e59f6d0d3f754aaae633949e8
2020-11-30 15:50:31 +01:00