* Move Service-Selection template to the TS 29.272 since it belongs
there.
* Set some parameter types to "template (value)" which makes it easier
for users, since both a template and a value can then be passed.
Change-Id: Ic57b2c5ec0a953f9a1751d4ce4ad441daafd3c87
The ddf file is added at the end of the list since it depends on tons of
other RFC and 3GGP TS specs, see for instance TS 29.372 Table 8.2.3.0.
Change-Id: I17f7f025ff31d9ce619cd23bfa5f1af282969dbf
A ddf file for TS 29.273 will be added soon to the list, which depends
on several RFCs. Move RFCs earlier in the list since this is a more
generic file than a 3GPP one.
Change-Id: Idcbdfd97332195af05928c81068f6a4779ac306e
It seems I somehow ended up adding this link file in
bf03d77649 when submitting the patch.
Get rid of it since it is totally undesired.
Change-Id: Iec812841bc474ae423b447707adc520cf4039499
The fields were added to be used in EPDG_Tests, but they need to be
explicitly set to omit here.
Fixes: 65a7f762ef
Change-Id: I3ed3c185310082f36bbce22817b903232825567c
The Types are already split in the dependent modules in GTPC_Types and
GTPU_Types.
There's no point in keeping them together in the same file since those 2
protocols are mostly independent.
Furthermore, testsuites using GTPv2C + GTPv1U don't need GTPv1C.
Change-Id: Ic15c9a2e92828cbafb4dda7355ee534107051e2d
Use setverdict(fail, …) instead of shutting down the test. Otherwise we
don't close the PDP context. This fixes TC_pdp6_act_deact failing if it
runs after a failed TC_pdp4_act_update_teid.
Change-Id: Ib31481e79fc81983ae0c36f0512c6b7dba3f28a8
Other Emulations like GTPv2 and DIAMETER already support that number of
sessions. Increase it to the same number in GSUP_Emulation to allow
handling a high amount of concurrent sessions while testing ePDG.
Change-Id: I9ce650140fc372debc85b603a20bbe9ea165c972
I see packets of 1520 bytes in the generated pcap running under the
docker setup. This happens when a lot of IPA concurrent clients send
messages and end up in the same TCP packet due to naggle algorithm.
Change-Id: I362371508ba83acc48376b6ed012a97a59d4b31b
This test allows initial testing of a session creation through the S2b
interface (emulating an ePDG).
A follow-up test will be added to test the APCO IE (feature which
open5gs-smfd still doesn't support).
Change-Id: I38e469edf0e00feca5a648035b64645e2c905937
So far we were only testing s5/s8 interface, but we'll want to test s2b
soon.
This commit is a mixture of refactorings and code improvements as a step
towards testing S2b interface.
Change-Id: I22b3e18d02ca828e2ea43bde2e0a602db236cf50
Strongswan already has this information during first IKE_AUTH message,
see 3GPP TS 24.302 7.2.2.1.
Change-Id: I42e4dc4bbcef969aae5867dbb103f8a5db157c89
A recent commit added records to separate 2 binary octets into known
fields, but 2 fields filling 1 byte were actually written swapped. Fix
it now.
Fixes: 7b7a1e8ed1
Change-Id: I884bddb0e1e5f1cfc5615c11d6c7d602d0df9224
Should fix the following log message:
NS_Emulation.ttcnpp:784 Timeout operation on timer Tns_alive failed: The timer is not started.
Change-Id: If1fae965659f73fde2508b0e9158099025fa65f2
Should fix the following log message:
BSSGP_Emulation.ttcnpp:1118 Timeout operation on timer g_T1 failed: The timer is not started.
Change-Id: Id7d1b76a6bc1fc2f0f4896c59673c01293b526e9
Those interfaces reuse messages from other Diameter RFCs, but changing
the contents of the messages, eg some Mandatory fields like
Service-Context-Id which are mandatory in RFC5006, doesn't even appear
in Gx CCR in TS 29.212.
Keeping them well separated helps in avoiding confusion on users fo the
messages.
Change-Id: Ibe0d5f263813d5083e020c942283f214983162b4
The previous conditions "isvalue()" were wrong. Passing an array of
templates to isvalue() returns false, which is unexpected here.
Change-Id: Iaad47b1ec7e2a7477fa554df9caeb866ffa594eb