container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #518
· raw
1additionally exposed symbols:2 controller1, controller2, peer1, peer2, peer3,3 start_all, machines, driver, Machine, wait_for_signal4Starting controller15Starting controller26Starting peer17Starting peer28Starting peer39101112131415<<< NixOS Stage 2 >>>1617booting system configuration /nix/store/msh1p1k1mx42r7smi7zjrvsqna0gxj74-nixos-system-controller1-test18running activation script...19setting up /etc...202: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100021 link/ether ba:9c:76:d8:39:5a brd ff:ff:ff:ff:ff:ff link-netnsid 022setting up age secrets...23starting systemd...24systemd 260.2 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE)25Detected virtualization systemd-nspawn.26Detected architecture arm64.27Detected first boot.28Initializing machine ID from container UUID.29Applying preset policy.30Populated /etc with preset unit settings.31Queued start job for default target Multi-User System.32333435<<< Welcome to NixOS test (aarch64) - console >>>36+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo 1f99eaba-7ff3-45c5-a177-a1afd777a1c9'37Running as unit: run-p315-i110603828.service; invocation ID: dbadc9b345744982aabc69632c8f791f38To attach to container controller1 run on the same machine that runs the test:39 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*1f99eaba-7ff3-45c5-a177-a1afd777a1c9') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4041To inject external network and continue test, run:42sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/2y51rn5wgsfsam71nsisca336nva2cm8-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 1f99eaba-7ff3-45c5-a177-a1afd777a1c94344<<< NixOS Stage 2 >>>4546booting system configuration /nix/store/nhbxwyryh5lp80a17zd2vyr4n3c6igzy-nixos-system-controller2-test47running activation script...48setting up /etc...492: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100050 link/ether e2:8c:47:a0:40:ce brd ff:ff:ff:ff:ff:ff link-netnsid 051setting up age secrets...52starting systemd...53systemd 260.2 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE)54Detected virtualization systemd-nspawn.55Detected architecture arm64.56Detected first boot.57Initializing machine ID from container UUID.58Applying preset policy.59Populated /etc with preset unit settings.60Queued start job for default target Multi-User System.61626364<<< Welcome to NixOS test (aarch64) - console >>>65+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo a1009181-147e-472e-b467-c83b7d88a002'66Running as unit: run-p315-i110603879.service; invocation ID: fcf237f3c174466497d7d71b450de06d67To attach to container controller2 run on the same machine that runs the test:68 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a1009181-147e-472e-b467-c83b7d88a002') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 6970To inject external network and continue test, run:71sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/2y51rn5wgsfsam71nsisca336nva2cm8-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py a1009181-147e-472e-b467-c83b7d88a0027273<<< NixOS Stage 2 >>>7475booting system configuration /nix/store/81k9f1lc17sfhm484zw2yql4l6nxm0zz-nixos-system-peer1-test76running activation script...77setting up /etc...782: host0@if7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100079 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 080setting up age secrets...81starting systemd...82systemd 260.2 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE)83Detected virtualization systemd-nspawn.84Detected architecture arm64.85Detected first boot.86Initializing machine ID from container UUID.87Applying preset policy.88Populated /etc with preset unit settings.89Queued start job for default target Multi-User System.90919293<<< Welcome to NixOS test (aarch64) - console >>>94+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo 21cbce65-c0ed-446d-8165-54631a26df1d'95Running as unit: run-p313-i110603902.service; invocation ID: 52b0eac234bd404e980d6d7ff6eed44596To attach to container peer1 run on the same machine that runs the test:97 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*21cbce65-c0ed-446d-8165-54631a26df1d') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 9899To inject external network and continue test, run:100sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/2y51rn5wgsfsam71nsisca336nva2cm8-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 21cbce65-c0ed-446d-8165-54631a26df1d101102<<< NixOS Stage 2 >>>103104booting system configuration /nix/store/yyy22245w595hwhvy5fcp7fjvc4kq3b6-nixos-system-peer2-test105running activation script...106setting up /etc...1072: host0@if5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000108 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0109setting up age secrets...110starting systemd...111systemd 260.2 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE)112Detected virtualization systemd-nspawn.113Detected architecture arm64.114Detected first boot.115Initializing machine ID from container UUID.116Applying preset policy.117Populated /etc with preset unit settings.118Queued start job for default target Multi-User System.119120121122<<< Welcome to NixOS test (aarch64) - console >>>123+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo 109f84a4-b1e6-4296-acbb-4816cc0dc308'124Running as unit: run-p313-i110603927.service; invocation ID: 11744d9fa9a946df8504197b0d90f443125To attach to container peer2 run on the same machine that runs the test:126 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*109f84a4-b1e6-4296-acbb-4816cc0dc308') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 127128To inject external network and continue test, run:129sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/2y51rn5wgsfsam71nsisca336nva2cm8-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 109f84a4-b1e6-4296-acbb-4816cc0dc308130131<<< NixOS Stage 2 >>>132133booting system configuration /nix/store/zf93443k4yzr57q3bjv1cjkcxmqsb4lx-nixos-system-peer3-test134running activation script...135setting up /etc...1362: host0@if6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000137 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0138setting up age secrets...139starting systemd...140systemd 260.2 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE)141Detected virtualization systemd-nspawn.142Detected architecture arm64.143Detected first boot.144Initializing machine ID from container UUID.145Applying preset policy.146Populated /etc with preset unit settings.147Queued start job for default target Multi-User System.148149150151<<< Welcome to NixOS test (aarch64) - console >>>152+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo b6a6331b-3b02-40a4-a647-88fe6673c3ac'153Running as unit: run-p309-i110603946.service; invocation ID: e57dd57473364ab3888d43c36553f450154To attach to container peer3 run on the same machine that runs the test:155 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*b6a6331b-3b02-40a4-a647-88fe6673c3ac') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 156157To inject external network and continue test, run:158sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/2y51rn5wgsfsam71nsisca336nva2cm8-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py b6a6331b-3b02-40a4-a647-88fe6673c3ac159+ systemctl start network-online.target160+ systemctl start network-online.target161+ systemctl start network-online.target162+ systemctl start network-online.target163+ systemctl start network-online.target164+ systemctl --no-pager show network-online.target165+ systemctl --no-pager show systemd-networkd.service166+ systemctl --no-pager show network-online.target167+ systemctl --no-pager show systemd-networkd.service168+ systemctl --no-pager show network-online.target169+ systemctl --no-pager show systemd-networkd.service170+ systemctl --no-pager show network-online.target171+ systemctl --no-pager show systemd-networkd.service172+ systemctl --no-pager show network-online.target173+ systemctl --no-pager show systemd-networkd.service174175176============================================================177STARTING PING TESTS178============================================================179180--- Pinging from peer1 to peer2.wg-test-one ---181peer1: waiting for success: ping -c1 peer2.wg-test-one >&2182+ ping -c1 peer2.wg-test-one183PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes18464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.576 ms185186--- peer2.wg-test-one ping statistics ---1871 packets transmitted, 1 received, 0% packet loss, time 0ms188rtt min/avg/max/mdev = 0.576/0.576/0.576/0.000 ms189(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)190191--- Pinging from peer1 to peer3.wg-test-one ---192peer1: waiting for success: ping -c1 peer3.wg-test-one >&2193+ ping -c1 peer3.wg-test-one194PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes19564 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=3135 ms196197--- peer3.wg-test-one ping statistics ---1981 packets transmitted, 1 received, 0% packet loss, time 0ms199rtt min/avg/max/mdev = 3135.488/3135.488/3135.488/0.000 ms200(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 3.15 seconds)201202--- Pinging from peer1 to controller1.wg-test-one ---203peer1: waiting for success: ping -c1 controller1.wg-test-one >&2204+ ping -c1 controller1.wg-test-one205PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes20664 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.204 ms207208--- controller1.wg-test-one ping statistics ---2091 packets transmitted, 1 received, 0% packet loss, time 0ms210rtt min/avg/max/mdev = 0.204/0.204/0.204/0.000 ms211(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)212213--- Pinging from peer1 to controller2.wg-test-one ---214peer1: waiting for success: ping -c1 controller2.wg-test-one >&2215+ ping -c1 controller2.wg-test-one216PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes21764 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.324 ms218219--- controller2.wg-test-one ping statistics ---2201 packets transmitted, 1 received, 0% packet loss, time 0ms221rtt min/avg/max/mdev = 0.324/0.324/0.324/0.000 ms222(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)223224--- Pinging from peer2 to peer1.wg-test-one ---225peer2: waiting for success: ping -c1 peer1.wg-test-one >&2226+ ping -c1 peer1.wg-test-one227PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes22864 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.430 ms229230--- peer1.wg-test-one ping statistics ---2311 packets transmitted, 1 received, 0% packet loss, time 0ms232rtt min/avg/max/mdev = 0.430/0.430/0.430/0.000 ms233(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)234235--- Pinging from peer2 to peer3.wg-test-one ---236peer2: waiting for success: ping -c1 peer3.wg-test-one >&2237+ ping -c1 peer3.wg-test-one238PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes23964 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.414 ms240241--- peer3.wg-test-one ping statistics ---2421 packets transmitted, 1 received, 0% packet loss, time 0ms243rtt min/avg/max/mdev = 0.414/0.414/0.414/0.000 ms244(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)245246--- Pinging from peer2 to controller1.wg-test-one ---247peer2: waiting for success: ping -c1 controller1.wg-test-one >&2248+ ping -c1 controller1.wg-test-one249PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes25064 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.176 ms251252--- controller1.wg-test-one ping statistics ---2531 packets transmitted, 1 received, 0% packet loss, time 0ms254rtt min/avg/max/mdev = 0.176/0.176/0.176/0.000 ms255(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)256257--- Pinging from peer2 to controller2.wg-test-one ---258peer2: waiting for success: ping -c1 controller2.wg-test-one >&2259+ ping -c1 controller2.wg-test-one260PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes26164 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.230 ms262263--- controller2.wg-test-one ping statistics ---2641 packets transmitted, 1 received, 0% packet loss, time 0ms265rtt min/avg/max/mdev = 0.230/0.230/0.230/0.000 ms266(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)267268--- Pinging from peer3 to peer1.wg-test-one ---269peer3: waiting for success: ping -c1 peer1.wg-test-one >&2270+ ping -c1 peer1.wg-test-one271PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes27264 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.372 ms273274--- peer1.wg-test-one ping statistics ---2751 packets transmitted, 1 received, 0% packet loss, time 0ms276rtt min/avg/max/mdev = 0.372/0.372/0.372/0.000 ms277(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)278279--- Pinging from peer3 to peer2.wg-test-one ---280peer3: waiting for success: ping -c1 peer2.wg-test-one >&2281+ ping -c1 peer2.wg-test-one282PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes28364 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=3.77 ms284285--- peer2.wg-test-one ping statistics ---2861 packets transmitted, 1 received, 0% packet loss, time 0ms287rtt min/avg/max/mdev = 3.768/3.768/3.768/0.000 ms288(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)289290--- Pinging from peer3 to controller1.wg-test-one ---291peer3: waiting for success: ping -c1 controller1.wg-test-one >&2292+ ping -c1 controller1.wg-test-one293PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes29464 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.204 ms295296--- controller1.wg-test-one ping statistics ---2971 packets transmitted, 1 received, 0% packet loss, time 0ms298rtt min/avg/max/mdev = 0.204/0.204/0.204/0.000 ms299(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)300301--- Pinging from peer3 to controller2.wg-test-one ---302peer3: waiting for success: ping -c1 controller2.wg-test-one >&2303+ ping -c1 controller2.wg-test-one304PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes30564 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.193 ms306307--- controller2.wg-test-one ping statistics ---3081 packets transmitted, 1 received, 0% packet loss, time 0ms309rtt min/avg/max/mdev = 0.193/0.193/0.193/0.000 ms310(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)311312--- Pinging from controller1 to peer1.wg-test-one ---313controller1: waiting for success: ping -c1 peer1.wg-test-one >&2314+ ping -c1 peer1.wg-test-one315PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes31664 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.201 ms317318--- peer1.wg-test-one ping statistics ---3191 packets transmitted, 1 received, 0% packet loss, time 0ms320rtt min/avg/max/mdev = 0.201/0.201/0.201/0.000 ms321(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)322323--- Pinging from controller1 to peer2.wg-test-one ---324controller1: waiting for success: ping -c1 peer2.wg-test-one >&2325+ ping -c1 peer2.wg-test-one326PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes32764 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.212 ms328329--- peer2.wg-test-one ping statistics ---3301 packets transmitted, 1 received, 0% packet loss, time 0ms331rtt min/avg/max/mdev = 0.212/0.212/0.212/0.000 ms332(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)333334--- Pinging from controller1 to peer3.wg-test-one ---335controller1: waiting for success: ping -c1 peer3.wg-test-one >&2336+ ping -c1 peer3.wg-test-one337PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes33864 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.228 ms339340--- peer3.wg-test-one ping statistics ---3411 packets transmitted, 1 received, 0% packet loss, time 0ms342rtt min/avg/max/mdev = 0.228/0.228/0.228/0.000 ms343(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)344345--- Pinging from controller1 to controller2.wg-test-one ---346controller1: waiting for success: ping -c1 controller2.wg-test-one >&2347+ ping -c1 controller2.wg-test-one348PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes34964 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=4961 ms350351--- controller2.wg-test-one ping statistics ---3521 packets transmitted, 1 received, 0% packet loss, time 0ms353rtt min/avg/max/mdev = 4961.174/4961.174/4961.174/0.000 ms354(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 4.97 seconds)355356--- Pinging from controller2 to peer1.wg-test-one ---357controller2: waiting for success: ping -c1 peer1.wg-test-one >&2358+ ping -c1 peer1.wg-test-one359PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes36064 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.317 ms361362--- peer1.wg-test-one ping statistics ---3631 packets transmitted, 1 received, 0% packet loss, time 0ms364rtt min/avg/max/mdev = 0.317/0.317/0.317/0.000 ms365(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)366367--- Pinging from controller2 to peer2.wg-test-one ---368controller2: waiting for success: ping -c1 peer2.wg-test-one >&2369+ ping -c1 peer2.wg-test-one370PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes37164 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.251 ms372373--- peer2.wg-test-one ping statistics ---3741 packets transmitted, 1 received, 0% packet loss, time 0ms375rtt min/avg/max/mdev = 0.251/0.251/0.251/0.000 ms376(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)377378--- Pinging from controller2 to peer3.wg-test-one ---379controller2: waiting for success: ping -c1 peer3.wg-test-one >&2380+ ping -c1 peer3.wg-test-one381PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes38264 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.257 ms383384--- peer3.wg-test-one ping statistics ---3851 packets transmitted, 1 received, 0% packet loss, time 0ms386rtt min/avg/max/mdev = 0.257/0.257/0.257/0.000 ms387(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)388389--- Pinging from controller2 to controller1.wg-test-one ---390controller2: waiting for success: ping -c1 controller1.wg-test-one >&2391+ ping -c1 controller1.wg-test-one392PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes39364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.229 ms394395--- controller1.wg-test-one ping statistics ---3961 packets transmitted, 1 received, 0% packet loss, time 0ms397rtt min/avg/max/mdev = 0.229/0.229/0.229/0.000 ms398(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)399400401402403