laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/27092 )

Change subject: ggsn: Expect no linklocal-addr forwarding when testing open5gs ......................................................................

ggsn: Expect no linklocal-addr forwarding when testing open5gs

It's not really clear whether GTP should really be forwarding packets with link-local address outside the tunnel. In theory the link-local address should be used to communicate with the GGSN in order to get the global link address, that's it. Running against open5gs it can be observed that they are not forwarded, while osmo-ggsn forwards them correctly. Since it seems more like an implementation dependent detail, let's accept any and adapt expectancies depending on what are we testing, this way it ends up documented the current situation in case it ever changes in the future.

Change-Id: Ieafd24c059b9341c702311c78caad3312db5f1f3 --- M ggsn_tests/GGSN_Tests.ttcn 1 file changed, 5 insertions(+), 1 deletion(-)

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved

diff --git a/ggsn_tests/GGSN_Tests.ttcn b/ggsn_tests/GGSN_Tests.ttcn index 0d134f6..3b34c7f 100644 --- a/ggsn_tests/GGSN_Tests.ttcn +++ b/ggsn_tests/GGSN_Tests.ttcn @@ -995,7 +995,11 @@ /* Check if we can use valid link-local src addr. */ var OCT16 saddr_ll := f_ipv6_link_local(ctx.eua.endUserAddress.endUserAddressIPv6.ipv6_address); f_send_gtpu(ctx, f_gen_icmpv6_echo(saddr_ll, dns1_addr)); - f_wait_icmp6_echo_reply(ctx); + if (m_ggsn_impl == GGSN_IMPL_OSMOCOM) { + f_wait_icmp6_echo_reply(ctx); + } else { + f_wait_gtpu_fail(ctx); + }

/* Check that attempting RA with another ll src addr won't work, packet dropped: */ var OCT16 saddr_ll_wrong := f_ipv6_mangle(saddr_ll, 8);