Changes

Common.cfg: Logging: add %p to LogFile format

Add the process ID at the end of the log file that ttnc3 writes, to
avoid potential conflicts:

> Otherwise if you have eg TC_foobar in STP_Tests_M3UA and
> STP_Tests_IPA, you may end up rewriting one of them since both would be
> written with the same file name.

%e is the name of the TTCN-3 executable, e.g. STP_Tests even if the test
case is in STP_Tests_M3UA. It is not possible to get STP_Tests_M3UA into
the file name with any of the meta characters, I've tried it out.

Related: https://gitlab.eclipse.org/eclipse/titan/titan.core/-/blob/9.0.0/usrguide/referenceguide/7-the_run-time_configuration_file.adoc#L632-666
Change-Id: I0a2a376cd11784addff8ca228e3cc3e831b418a2

Cosmetic: log_merge: modernize

Move license and copyright up and use an SPDX license identifier.

Change-Id: Iedd4f575edeaf47852f073d04d8cd8ffd92920dc

log_merge: ensure we don't overwrite the log file

Add a safety check that ensures we don't overwrite an existing log file
by accident.

Change-Id: Ieda3d95c60dfae208959b80d55a1e8c3925a9dad

log_merge: use same prefix as for pcap files

In some testsuites we have tests in ttcn3 files other than the main
testsuite executable. In that case we save the pcap files with the name
of the ttcn3 file with the test, but before this patch the merged log
file has the name of the main testsuite. This is inconsistent and may
lead to a conflict if a test exists in multiple ttcn3 files.

Fix this by getting the same prefix as we use for the pcap from the
logfile itself. Fall back to using the same prefix as without this patch
in case we can't parse the log line.

Fixes: OS#6787
Change-Id: Id2937d711a54a34c0d87d080199b4c3d5a5d6e06

M3UA_Templates: Allow passing multiple Routing Context values

Change-Id: I117c63786d71aea683b554cf294fee0ceed665e0

stp: Update TC_rkm_unreg_active to expect multiple routing contexts

That test is registering a new routcing context (AS) into an
existing/pre-configured ASP.
As a result, the ASP serves 2 AS. When we receive notifications on that
ASP then we'll be receiving info on 2 routing contexts, one for the
pre-confgiured AS and one for the dynamically registered one.

Depends: libosmo-sigtran.git I646301ec3d08ef98f227cf4d19da1039e40cedd2
Change-Id: I2dc4d197e6de38781b63e3079ada4c4b4a0db31d

stp: Store asp name in array of m3ua cfgs

This way we keep STP specific config in one place instead of having to
figure out the ASP name on each test where we want to modify that ASP.

Change-Id: I1d5d9113dc95a8da911a7a99260c9bfe6e9de7c9

stp: Introduce test TC_clnt_sctp_adm_shutdown

Related: OS#6752
Change-Id: I8b1c8b633afc1515dedfccd43e642401896b167e

stp: Introduce test TC_m3ua_sctp_srv_adm_shutdown

Related: OS#6752
Change-Id: Iad34af7e7758fbd3a0d686a261ccce53bc705817

hnbgw: HNBGW_Tests.default: Drop unused LLSK config

That's only used in osmo-hnodeb, and it's probably a leftover when
copy-pasting from hnodeb directory to create the hnbgw testsuite.

Change-Id: Ic04ded35f64b5dac0c5f36ebdf066d751013c438

hnbgw: Add missing plmn config in osmo-hnbgw.cfg

Change-Id: Ie360247b7be9cf5ac4feeab2a8957131896f7721

hnbgw: Configure local ASP/AS in osmo-hnbgw.cfg

This allows us using known port for the SCTP assoc, which can then be
used to look up ASP in osmo-stp VTY.

Change-Id: Ic04702b597f7217890ee58734c11b866fb14af8b

hnbgw: Introduce test TC_{cs,ps}_rua_dt_during_sccp_wait_cc

Related: SYS#7453
Change-Id: I97767db5560edf951202c876726d0c52b5b5b49f

gbproxy/testenv: initial

Change-Id: I75265eb0765da85bffd76f8d64d278ed008d9b47

gbproxy: sync configs with docker-playground

Change-Id: Ibef7e870c5c90d1cc861c89904950b1ac68dc9b2

hnbgw: Introduce altstep as_pfcp_handle_del_req()

Change-Id: I94101b5f0ad8634db68f0a9d5230c00926b02061

hnbgw: Introduce tests TC_ps_rab_release(_abnormal)

Same as their existing CS counterparts TC_rab_release(_abnormal).

Related: SYS#7451
Change-Id: Ia25efc2d6bf01d4a13e7fd1ce0563d20dd2e321e

testenv: podman_install: show checked out commits

When running with --podman --binary-repo and a testsuite needs a
component for which we don't have a binary package (such as
sccp_demo_user), we need to clone the source and build it.

Show the commit from which we are building / have already built the
component.

Suggested-by: Pau Espin Pedrol <pespin@sysmocom.de>
Change-Id: I2837a41c919a9f7ef8c315ce5aa48fb4fe3f9a85

testenv: podman_install: tweak git commands

* Do not run them in podman: git is required to run testenv, by not
  running it through podman the command in the log is shorter.
* Set advice.detachedHead=false for the git clone to avoid printing the
  "You are in 'detached HEAD' state. You can look around ..." text block
  that isn't useful in this context.

Change-Id: I2ee26764d1471e54eff748e11ec2cce6fb662667

testenv: no python trace for setup script failures

Do not print a python trace when a setup script fails, usually it is
unrelated and just clutters the output.

Change-Id: Icbec52befa268547906fdbe9b52bdbc9e94722e6

testenv: podman: add erlang-dev

Add the full erlang-dev package to the podman container, so we can build
osmo-epdg from source. Without this it fails with ei.h missing.

Change-Id: I4ca9d1823037889315f50de629e5581964cda079

testenv: podman: add missing tree command

The tree command is used by the testenv scripts when building QEMU
initrds to quickly show the contents of the initrd before packing it.

Fix for:
  + tree -a /tmp/testenv-ggsn_tests-osmo_ggsn_v4_only-20250509-1151-745e3562-dxt_lu1f/ggsn/_initrd
  osmo-ggsn/run.sh: 140: tree: not found

That the build initramfs logic did not abort here is another bug that
gets fixed in a follow-up patch in this series.

Change-Id: I75fcd210db9e5c9364cb98ee09ebf754790aa55f

testenv: qemu: fix adding kernel modules

Without this patch qemu_initrd_add_file fails to add kernel modules
with "No such file or directory" when running in podman, even though the
files exist:

  ./testenv.py run ggsn -Dp -c osmo_ggsn_v4_only
  …
  + cp -a --parents /lib/modules/6.1.0-34-amd64/kernel/drivers/net/net_failover.ko /tmp/testenv-ggsn_tests-osmo_ggsn_v4_only-20250509-1146-cd82caba-wegi5i98/ggsn/_initrd/usr
  cp: 'lib/modules/6.1.0-34-amd64/kernel/drivers/net': No such file or directory
  …

When looking at it with strace it became clear that this comes from a
getxattr that fails in the podman filesystem and returns a misleading
error:

  getxattr("lib/modules/6.1.0-34-amd64/kernel/drivers/net", "system.posix_acl_access", 0x7ffc012054e0, 132) = -1 ENOENT (No such file or directory)

Fix it by modifying the cp command to not try to preserve any attributes
(they don't matter in the initramfs).

Change-Id: Ic32318da169ee8ebf867937782be5cf8a15f9f2f

testenv: fix not aborting on build_initrd error

Without this patch the build_initrd function keeps going on errors:

  + cp -a --parents /lib/modules/6.1.0-34-amd64/kernel/drivers/net/net_failover.ko /tmp/testenv-ggsn_tests-osmo_ggsn_v4_only-20250509-1040-a21668df-euc9e2fs/ggsn/_initrd/usr
  cp: 'lib/modules/6.1.0-34-amd64/kernel/drivers/net': No such file or directory
  + cp -a --parents /lib/modules/6.1.0-34-amd64/kernel/drivers/net/virtio_net.ko /tmp/testenv-ggsn_tests-osmo_ggsn_v4_only-20250509-1040-a21668df-euc9e2fs/ggsn/_initrd/usr
  …

The reason for that is that even though the script runs with set -e, the
-e flag gets ignored between if…then where the build_initrd shell
function gets called:

  if ! build_initrd >build_initrd.log 2>&1; then
  qemu_initrd_exit_error "build_initrd.log"
  fi

Fix it by using a trap instead.

Related: https://unix.stackexchange.com/a/65564
Change-Id: I2870b7e7ba28b2afc72e86b7a3bc389103564c80

testenv: qemu: initrd build fail: stop immediately

Let qemu_wait.sh fail immediately when building the initrd has failed,
instead of waiting until it runs into a timeout.

Change-Id: I6de4d1c31385af52ee0fd55378adb10a9e2c2154

testenv: qemu: add modules.alias

Fix loading the sctp module, which is needed to run osmo-epdg in QEMU:
  modprobe: can't load module libcrc32c (kernel/lib/libcrc32c.ko): unknown symbol in module, or unknown parameter

Change-Id: I475176734b994e7abda63badda0983ab6534b682

testenv: support qemu=required in testenv.cfg

Make it possible to set qemu=required in addition to the existing
possibility of qemu=optional in the testenv configs and verify that
either the debian kernel (from the podman container) or a custom kernel
gets used for such configs.

This is in preparation for adding a testenv config for osmo-epdg, which
uses kernel-gtp and unlike osmo-ggsn doesn't have userspace fallback
code. With testenv using the hosts gtp kernel device for this is not
supported (it would have several downsides anyway, such as not being in
control what exact kernel version is used leading to different test
outcomes for different users, not being easily able to compare different
kernel versions, having a harder time getting debug logs from the module
etc.).

Change-Id: If4abdf1f9248fee0915603a9b3c6e3e5e5083057

testenv: qemu_initrd_add_bin: support adding so

Erlang has its own library loading mechanism, so we need to explicitly
add the depending libraries to the initramfs instead of just pointing at
binaries.

Change-Id: I1b9f06e7bff22b9260fbe0bd765177a25e97b557

testenv: cfg: check for multiple spaces in lists

Pau ran into an unexpected bug while having entries in copy= separated
by multiple spaces ("copy=osmo-stp.cfg  osmo-stp-m3ua.confmerge"):

  [testenv][m3ua] + ['cp', '-a', 'osmo-stp.cfg', '', 'osmo-stp-m3ua.confmerge', '/tmp/testenv-stp-m3ua-20250516-1349-e4103924-bfvi_syt/stp']
  cp: cannot stat '': No such file or directory

Catch this early and print a more useful error:

  [testenv] /home/user/code/osmo-dev/src/osmo-ttcn3-hacks/stp/testenv.cfg: copy= in section [stp] has multiple spaces:
  [testenv]   "osmo-stp.cfg  osmo-stp-m3ua.confmerge"
  [testenv] Please separate elements with only one space.

Change-Id: Ie47cf5482ba479457a662759ce87611a7c41e29c

stp: Rename STP_Tests.ttcn -> STP_Tests_IPA_M3UA.ttcn

The previous name usually causes confusion since it seems to indicate
either:
* Some sort of common placeholder for STP_Tests_IPA and STP_Tests_M3UA
  (it's not the case, we already have STP_Tests_Common.ttcn for that)
* A placeholder for tests not IPA or M3UA related (it's not the case,
  since it only contains IPA<->M3UA tests).

Hence, rename it to denote better the aim of that file, ie. testing
forwarding between IPA and M3UA AS(P)s.

Change-Id: Id2963407adf11add01630c3899a062d764c8ad75

stp: STP_Tests_IPA: Support configuring less than 8 AS(P)s

This is a preparation patch towards splitting testsuite into smaller
configurations.

Change-Id: I820d295cd22fe824abf0f60bf6f1f0f3fd069d85

epdg: add sleep to f_TC_hss_initiated_deregister_permanent_termination

The test sends PERMANENT_TERMINATION twice to osmo-epdg. If we don't
sleep between them, osmo-epdg is not able to terminate related FSMs
quickly enough between the first and the second termination request when
running in QEMU, which results in osmo-epdg answering with
DIAMETER_SUCESS instead of DIAMETER_ERROR_USER_UNKNOWN for the second
f_DIA_SWx_RT.

Related: OS#6796
Change-Id: I5d7021b6a9800cf1d7588f4a0ef864f5c30cf475

epdg: TC_concurrent_ues_MTC: rx CMD_ATTACHED without from vc_conn_list[i]

This is needed to make the test pass in QEMU. I think this makes it
accept the COORD_CMD_ATTACHED in any order instead of the order the
COORD_CMD_START were sent beforehand.

Increasing the sleep between the COORD_CMD_START also makes the test
pass in QEMU, but that increases the overall test time significantly in
TC_concurrent_ues100.

Change-Id: I4c76d12273a14df562ea906e6c8ddb348d1b0eda

epdg: initial testenv.cfg

With this config, all tests are passing.

Depends: osmo-ci Ia60d5c1f5ade31e37293b40340e789f04ea86287
Change-Id: Ide2873be7830cc43e7fa09f26b2d504d0563a3c2

testenv: check eclipse-titan version

The osmocom:latest repository currently has eclipse-titan 9.0.0 and we
assume that the user has at least this version installed. Add a check to
avoid subtle unexpected errors caused by using older versions.

Related: I57eecd6e0ea9e488a2110b029ddc313bd05cd1fa
Change-Id: Icace325f492ce803d6f25a30b128ee0676e16727

stp: Initial split into several testenv config

As a first step, split the generic config into 3 configs, one per
module.

The idea is to have a different config for a given set of related tests
running on a specific network topology/setup.

This helps in simplifying the test conditions, which allows easily
adding new topologies to test, validate specific scenarios or debug
existing ones.

For instance, to test Combined linkset loadsharing, we'll need to set up
some sort of scenario where we have at least 2 AS with each at least 1
ASP.

Change-Id: I4ec8e1bbc8e71d8bd421dfbd5356bf1937ce2bb4

stp: Split M3UA TCP tests into its own testenv config

That group of tests explicitly tests operation of m3ua-tcp AS(P)s and
interaction with m3ua(-sctp) ones.
Hence, create a new config to test those, where we keep the TCP related
configuration in osmo-stp.

Change-Id: I8123887755aa3253830b43407b4cc6b21142233c

stp: m3ua: Specify ASP names to use per test

Since we recently introduced an "asp_name" into each m3ua_config,
use that to construct a list of m3ua_configs to set up for each test.

This makes each test only set up the relevant ASPs for the test easily,
plus the big win of port offsets becoming test-specific.

That means changing the order or clients or servers in the testsuite
config, or adding new ones won't break existing tests.

Also add a new "is_server" field which allows specifying clients and
servers in whichever order we like.

Change-Id: I63ed043014ee8a9a593ed17797b621f39c746bcd

stp: ipa: Specify ASP names to use per test

Similar to what was done for M3UA ASPs in previous commit.

Change-Id: Ifce2a3964d4caf0850691515e516cee93dbe8d44

library: NGAP encoding/decoding using libfftranscode

This allows us to encode/decode 3GPP NGAP messages, as used on the
N2/NG-C interface control plane between gNB and AMF.

asn files fetched from https://forge.etsi.org/rep/int/5g-core/ngap.git
directory ttcn/LibNGAP/lib/asn1, commit
fa43d01e202379a969e991a9454d9c6c6930b5b5.

Change-Id: Ia8e29c77e09a4388c774e3d7286f96052d67fe3f

library: Add NGAP_Templates.ttcn

files fetched from https://forge.etsi.org/rep/int/5g-core/ngap.git
directory ttcn/LibNGAP/lib/LibNGAP_*.ttcn, commit
fa43d01e202379a969e991a9454d9c6c6930b5b5.

Change-Id: I52aed2961329ee904de82b4fdb91e3eaca2059c9

ngap: NGAP_Pixits: fix modulepar without default value assigned to template

Otherwise titan errors during startup when trying to assign unbound
values to template parameters in NGAP_Templates.ttcn.

Change-Id: Ib2410457d2b25f09134509b618b079b010e6ace0

NGAP_Templates: Fix criticality of PLMNSupportList IE in NGSetupResponse

The criticality rejected is specified in 3GPP TS 38.413 version 18.5.0
Release 18, both in the ASN.1 definition of "NGSetupResponseIEs NGAP-PROTOCOL-IES",
as well as section 9.2.6.2.
open5gs-amfd is correctly sending reject there.

Change-Id: I0e73a97201e61a41ce5b056a149e185582ed187c

NGAP_Templates: Add missing rx template for NGSetupFailure with TimeToWait optional IE

Change-Id: I241b83119e1fcf849895393ac1a1231368a85cbb

library: Introduce NGAP Emulation

Only initial features are working, like sending NG Setup Request +
Response.

Change-Id: I5aea8be12c54cf907e71bffe6456efb5e60eb203

testenv: podman: Stick rebar3 downloaded version to 3.24.0

The previous URL now contains a newer 3.25.0 rebar3 release, which
requires minimum OTP 26, but debian12 launches with OTP 25.

"""
  This BEAM file was compiled for a later version of the runtime system than the current (Erlang/OTP 25).
  To fix this, please re-compile this module with an Erlang/OTP 25 compiler.
  (Use of opcode 182; this emulator supports only up to 180.)
"""

Change-Id: Idce3a0a9e61b1d897a6d26f6b6eb49d59b0883ad

5gc: Introduce testsuite

Change-Id: I867433c87c6da2f0d1f299245aedf4830acbf539

library: Rename NAS_Templates.ttcn -> NAS_EPS_Templates.ttcn

This new naming matches existing files like NAS_EPS_Types.ttcn.
This also allows differentiating it from 5G NAS.

Change-Id: Ief9835e7c70ed2885105117613ec653a6ed4dfea

testenv: add -j/--jobs parameter to run action

Allow building with less than all CPU cores. This may be desirable
because the NGAP asn1 files are huge and building with -j$(NPROC) eats
all the memory on some systems.

Suggested-by: Pau Espin Pedrol <pespin@sysmocom.de>
Change-Id: I191291cabd40e23983d29a350e587c1e11a52c0d

testenv: add TESTENV_INSTALL_DIR

This is useful for e.g. the new 5gc testsuite.

Suggested-by: Pau Espin Pedrol <pespin@sysmocom.de>
Change-Id: I0a45e67c40a2c1d2220ef301e3e51178939f60b6

testenv: README: document env vars set by testenv

Change-Id: I1a43d6b71c4dbc00abd8a4347fb2b35704491591

5gc: Initial ConnHdlr support

With this we can already send an InitialUEMessage(Registration Request)
to the 5GC and see if everything is configured properly there.

Change-Id: I094b6775198dfcbf4041c3af423baa6f5072b97d

stp: ipa: Introduce tests to validate incoming TCP conn with unkown AS (ipa_unit_id)

Change-Id: If6a9f54a19f6a4d833bbf66aad5dafd7e9917f82

testenv: deduplicate make_dir

Generate the osmo-dev make dir path in one location, in testenv.cmd
which gets imported by testenv.osmo_dev instead of doing it in both.
This makes it easier to bump make_dir_version when necessary.

Change-Id: Id3cb30e1ea126daf04dac227a2bf39b746549ec9

testenv: fix TESTENV_INSTALL_DIR

When osmo-dev is used (no --binary-repo arg is set), then set
TESTENV_INSTALL_DIR and --install-prefix for osmo-dev to:
  <cache dir>/osmo-ttcn3-testenv/{podman,host}/install
Old --install-prefix:
  <cache dir>/osmo-ttcn3-testenv/{podman,host}/usr
Old TESTENV_INSTALL_DIR:
  <cache dir>/osmo-ttcn3-testenv/{podman,host}

The old behavior was misleading, because:
* It resulted in configs getting installed into:
  <cache dir>/osmo-ttcn3-testenv/{podman,host}/usr/etc/...
* TESTENV_INSTALL_DIR looked like it would point at the install dir
  (because there is usr inside that directory), but it was actually
  pointing at the top dir of the install dir.

Fixes: 143b1000 ("testenv: add TESTENV_INSTALL_DIR")
Change-Id: Id94936338a6eb74dee0b3f4668cbaca309b269e4

5gc: testenv: use TESTENV_INSTALL_DIR

Change-Id: I412e53d132957a877a9a0478df3ac2fe31327a6c

log_merge.sh: Merge all logs if no test cases are found

This can happen for instance if titan exits with an error during startup
even before starting any test.
In that scenario, titan still writes stuff to a file (eg.
C5G_Tests--efc28eab6a6d-hc-1305.log).
Let's try to make everything logged available in that case, so user can
debug what went wrong.

Change-Id: Ifc68e42022e8b2990d3c5221b3901f255e4e759b

deps: Depend on osmocom fork of forge.etsi.org nas.git

This module provides types, templates and functions to operate NG NAS
(5G).

A fork is needed because:
* Upstream code doesn't compile against eclipse titan (A PR has been
  submitted upstream and we should eventually be able to compile ttcn3
  code just fine in that regard).
* Some system/external functions need to be implemented, such as
  fx_GetSystemTime(). We currently do that in our fork.

Related: SYS#7073
Change-Id: I004fc26e5d691ee7e3be984e28f5516e2b55258c

5gc: Initial support encoding NG NAS UL messages

Change-Id: Id59564114cf18ae745e3e385e2c91779a453e545

library/ngap: Fix wrong id set on PWSFailureIndication templates

Change-Id: Ied1c7a5914c6cbacf64ba857aa31c12ca6f001fb

library/ngap: Fix criticality of several NGAP messages

As defined in ASN.1 in 3GPP TS 38.413 section 9.4.3.

Change-Id: I2283a5b025f0ce7d7445fa0ce9ba8405156c4533

bts: f_init(): print testcasename() in the IUT's logs

It's useful to see testcase names in the IUT's logs in some
situations.  For instance, when some testcase crashes the IUT.

Change-Id: I16136f32d7143edfc1638e359ef5b1066c248732
Related: OS#6794

bsc: fix race condition in RSLEm

It may happen that the RSLEm component receives a DChan message
earlier than we suspend the DChan processing.  We saw this once:

  RSL for unknown Dchan
      BSC_Tests.ttcn:12769 BSC_Tests control part
      BSC_Tests.ttcn:5888 TC_ho_int_a5_4 testcase

Let's guard against this by calling f_rslem_suspend() earlier.

Change-Id: I012d4db05538d294a6b4aa85be4a40bb0bad28a3

testenv: run "make deps" every time

The previous logic of not always running "make deps" was useful when
"make deps" would take a long time to complete even if there were no
changes. But this has been fixed in c7e40d6a ("Makefile: avoid fetching
deps if not needed"). Run it every time now in order to fix that deps
are not updated after deps/Makefile gets changed.

Change-Id: I02668530ce36c51a1c641fb816464c9c8e6ded9e

5gc: Initial NAS receiving support

With this patch it is already possible to receive the NAS Auth Request
in the test ConnHdlr.

nas.git dep needs updating to include a new patch fixing decoding of
NG_AUTHENTICATION_REQUEST.

Change-Id: I6697f30f95777fc9aed16a529a669d10f42c57be

5gc: Initial NAS transmitting support

With this patch it is already possible to transmit the NAS Auth Response
in the test ConnHdlr.
We still lack generating a proper RES to have the response properly
accepted.

Change-Id: I951e98217b0150eed58fabb8e50a4782c1a3b510

testenv: podman: Install newer libcurl from bookworm-backports

It was already spotted a few days ago that libcurl4 7.88.1-10+deb12u12,
currently being shipped by debian12, contains some sort of bug where it
doesn't properly format/read HTTP2 requests when used in open5gs.
It was found out that installing a newer version of libcurl4 fixes the
problem.
This patch also fixes the problems spotted in the 5gc testsuite when
running within podman (they didn't show up outside podman because I'm
using Archlinux and hence using newer libcurl 8.13.0 too).

Change-Id: I799eeac73c49b9596502ad98acaa11dba3b88e97

5gc: Fix upfd failing to start outside podman

tuns need to be recreated beforehand with sudo, as already done in
ttcn3-ggsn-tests-ogs, otherwise upfd would need root access to create
them.

Change-Id: I5d3e0c3b7391d312304190acf07b347320481275

testenv: use eclipse-titan 11 in Dockerfile

Install eclipse-titan from osmocom:nightly instead of osmocom:latest,
which now has version 11. Once we ensured everything works as expected,
we will upgrade the version in osmocom:latest too.

Change-Id: I660dd6ca93a54087b1d41787c4ed2b64a3ad0437