github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 10:18:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

test: handle IPv6-only roaming (#10703)

Browse Source 
It is possible that our "roaming" integration test only ever connects
Client and Gateway over IPv6. In that case, the number of unique source
tuples after roaming is only 2 and not 3. To handle this case, we count
the number of IPv4 tuples and change the assertion accordingly.

In the current state, this causes test failures on `main`.
This commit is contained in:
Thomas Eizinger
2025-10-24 16:06:42 +11:00
committed by GitHub
parent 1bec325a64
commit f4ce6f12a0
1 changed files with 22 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
scripts/tests/download-roaming-network.sh
View File

@@ -50,14 +50,33 @@ readarray -t flows < <(get_flow_logs "tcp")
assert_gteq "${#flows[@]}" 2
declare -A unique_src_tuples
declare -i num_ipv4_tuples
for flow in "${flows[@]}"; do
# All flows should have same inner_dst_ip
assert_eq "$(get_flow_field "$flow" "inner_dst_ip")" "172.21.0.101"
# Collect all unique source tuples
outer_dst_ip=$(get_flow_field "$flow" "outer_dst_ip")
src_tuple="$(get_flow_field "${flow}" "outer_src_ip") $(get_flow_field "${flow}" "outer_src_port")"
unique_src_tuples["$src_tuple"]=1
case $outer_dst_ip in
"172.31.0.100")
unique_src_tuples["$src_tuple"]=1
num_ipv4_tuples+=1
;;
"172:31::100")
unique_src_tuples["$src_tuple"]=1
;;
*)
echo "Unexpected 'outer_src_ip': ${outer_dst_ip}"
exit 1
;;
esac
done
assert_gteq "${#unique_src_tuples[@]}" 3 # We should have at least 3; > 2 is important because ICE might hop between IPv4 and IPv6 during connection setup.
# If we only ever connected via IPv6, two unique source tuples are enough, otherwise we want three.
if [[ $num_ipv4_tuples == 0 ]]; then
assert_gteq "${#unique_src_tuples[@]}" 2
else
assert_gteq "${#unique_src_tuples[@]}" 3
fi