container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #555
· 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/bkcf6n1aiqvbnlfwpm1h2fipqrd7s309-nixos-system-controller1-test18running activation script...19setting up /etc...202: host0@if5: <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 40cae779-d75e-4513-bdf5-d6df847701ac'37Running as unit: run-p315-i116222625.service; invocation ID: 9adb2d3bc30443ed899573962a0d078738To attach to container controller1 run on the same machine that runs the test:39 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*40cae779-d75e-4513-bdf5-d6df847701ac') --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/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 40cae779-d75e-4513-bdf5-d6df847701ac4344<<< NixOS Stage 2 >>>4546booting system configuration /nix/store/6bdlvll9q0g4n436pp7kq24184nksnjz-nixos-system-controller2-test47running activation script...48setting up /etc...492: host0@if7: <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.61systemd-tmpfiles-setup-dev-early.service: Failed to spawn executor: No such file or directory62systemd-tmpfiles-setup-dev-early.service: Failed to spawn 'start' task: No such file or directory63systemd-tmpfiles-setup-dev-early.service: Failed with result 'resources'.64656667<<< Welcome to NixOS test (aarch64) - console >>>68+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo a10b76d3-5c05-4a23-a101-a487baac557a'69Running as unit: run-p313-i116222653.service; invocation ID: fe965b45f94d49b288d6450c0a685c8d70To attach to container controller2 run on the same machine that runs the test:71 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a10b76d3-5c05-4a23-a101-a487baac557a') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 7273To inject external network and continue test, run:74sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py a10b76d3-5c05-4a23-a101-a487baac557a7576<<< NixOS Stage 2 >>>7778booting system configuration /nix/store/rbx6c1wdwvmianjrqcyqprvf53wwliga-nixos-system-peer1-test79running activation script...80setting up /etc...812: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100082 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 083setting up age secrets...84starting systemd...85systemd 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)86Detected virtualization systemd-nspawn.87Detected architecture arm64.88Detected first boot.89Initializing machine ID from container UUID.90Applying preset policy.91Populated /etc with preset unit settings.92Queued start job for default target Multi-User System.93949596<<< Welcome to NixOS test (aarch64) - console >>>97+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo 96746698-98a8-4c0d-9fc0-13773da41d4e'98Running as unit: run-p311-i116222733.service; invocation ID: 1e0f9e3c3834479ba324599c3be2719b99To attach to container peer1 run on the same machine that runs the test:100 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*96746698-98a8-4c0d-9fc0-13773da41d4e') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 101102To inject external network and continue test, run:103sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 96746698-98a8-4c0d-9fc0-13773da41d4e104105<<< NixOS Stage 2 >>>106107booting system configuration /nix/store/008ygvgsi0napg2lq04m3ai33fqmrg37-nixos-system-peer2-test108running activation script...109setting up /etc...1102: host0@if6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000111 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0112setting up age secrets...113starting systemd...114systemd 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)115Detected virtualization systemd-nspawn.116Detected architecture arm64.117Detected first boot.118Initializing machine ID from container UUID.119Applying preset policy.120Populated /etc with preset unit settings.121Queued start job for default target Multi-User System.122123124125<<< Welcome to NixOS test (aarch64) - console >>>126+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo 9eb0ed51-83de-4229-b02e-3ce81b246061'127Running as unit: run-p314-i116222744.service; invocation ID: a529a42196f84cf59fe6d0bea4cf5d64128To attach to container peer2 run on the same machine that runs the test:129 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*9eb0ed51-83de-4229-b02e-3ce81b246061') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 130131To inject external network and continue test, run:132sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 9eb0ed51-83de-4229-b02e-3ce81b246061133134<<< NixOS Stage 2 >>>135136booting system configuration /nix/store/c6n4945iggvyad52iicm5wik8ia2ian1-nixos-system-peer3-test137running activation script...138setting up /etc...1392: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000140 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0141setting up age secrets...142starting systemd...143systemd 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)144Detected virtualization systemd-nspawn.145Detected architecture arm64.146Detected first boot.147Initializing machine ID from container UUID.148Applying preset policy.149Populated /etc with preset unit settings.150Queued start job for default target Multi-User System.151systemd-tmpfiles-setup-dev-early.service: Failed to spawn executor: No such file or directory152systemd-tmpfiles-setup-dev-early.service: Failed to spawn 'start' task: No such file or directory153systemd-tmpfiles-setup-dev-early.service: Failed with result 'resources'.154155156157<<< Welcome to NixOS test (aarch64) - console >>>158+ systemd-run /bin/sh -c '/nix/store/hlc4nqfx0l06f6p7z7lmd77qcwszi7wc-coreutils-9.11/bin/sleep 999999999 && echo dcdc8721-a35e-4c73-a81c-5d10c9cdb596'159Running as unit: run-p311-i116222787.service; invocation ID: ea44006541a344bbaebc4608e65e38a8160To attach to container peer3 run on the same machine that runs the test:161 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*dcdc8721-a35e-4c73-a81c-5d10c9cdb596') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 162163To inject external network and continue test, run:164sudo /nix/store/d6kq2phq0zy5invmkfgg8h35zxaf13s9-python3-3.13.15/bin/python3.13 /nix/store/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py dcdc8721-a35e-4c73-a81c-5d10c9cdb596165+ systemctl start network-online.target166+ systemctl start network-online.target167+ systemctl start network-online.target168+ systemctl start network-online.target169+ systemctl start network-online.target170+ 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.service174+ systemctl --no-pager show network-online.target175+ systemctl --no-pager show systemd-networkd.service176+ systemctl --no-pager show network-online.target177+ systemctl --no-pager show systemd-networkd.service178+ systemctl --no-pager show network-online.target179+ systemctl --no-pager show systemd-networkd.service180181182============================================================183STARTING PING TESTS184============================================================185186--- Pinging from peer1 to peer2.wg-test-one ---187peer1: waiting for success: ping -c1 peer2.wg-test-one >&2188+ ping -c1 peer2.wg-test-one189PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes190From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable191192--- peer2.wg-test-one ping statistics ---1931 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms194195+ ping -c1 peer2.wg-test-one196PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes197From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable198199--- peer2.wg-test-one ping statistics ---2001 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms201202+ ping -c1 peer2.wg-test-one203PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes204From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable205206--- peer2.wg-test-one ping statistics ---2071 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms208209+ ping -c1 peer2.wg-test-one210PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes21164 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.497 ms212213--- peer2.wg-test-one ping statistics ---2141 packets transmitted, 1 received, 0% packet loss, time 0ms215rtt min/avg/max/mdev = 0.497/0.497/0.497/0.000 ms216(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.04 seconds)217218--- Pinging from peer1 to peer3.wg-test-one ---219peer1: waiting for success: ping -c1 peer3.wg-test-one >&2220+ ping -c1 peer3.wg-test-one221PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes22264 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=2.02 ms223224--- peer3.wg-test-one ping statistics ---2251 packets transmitted, 1 received, 0% packet loss, time 0ms226rtt min/avg/max/mdev = 2.021/2.021/2.021/0.000 ms227(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)228229--- Pinging from peer1 to controller1.wg-test-one ---230peer1: waiting for success: ping -c1 controller1.wg-test-one >&2231+ ping -c1 controller1.wg-test-one232PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes23364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.254 ms234235--- controller1.wg-test-one ping statistics ---2361 packets transmitted, 1 received, 0% packet loss, time 0ms237rtt min/avg/max/mdev = 0.254/0.254/0.254/0.000 ms238(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)239240--- Pinging from peer1 to controller2.wg-test-one ---241peer1: waiting for success: ping -c1 controller2.wg-test-one >&2242+ ping -c1 controller2.wg-test-one243PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes24464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=3.19 ms245246--- controller2.wg-test-one ping statistics ---2471 packets transmitted, 1 received, 0% packet loss, time 0ms248rtt min/avg/max/mdev = 3.186/3.186/3.186/0.000 ms249(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)250251--- Pinging from peer2 to peer1.wg-test-one ---252peer2: waiting for success: ping -c1 peer1.wg-test-one >&2253+ ping -c1 peer1.wg-test-one254PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes255256--- peer1.wg-test-one ping statistics ---2571 packets transmitted, 0 received, 100% packet loss, time 0ms258259+ ping -c1 peer1.wg-test-one260PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes26164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.601 ms262263--- peer1.wg-test-one ping statistics ---2641 packets transmitted, 1 received, 0% packet loss, time 0ms265rtt min/avg/max/mdev = 0.601/0.601/0.601/0.000 ms266(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 11.02 seconds)267268--- Pinging from peer2 to peer3.wg-test-one ---269peer2: waiting for success: ping -c1 peer3.wg-test-one >&2270+ ping -c1 peer3.wg-test-one271PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes27264 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.644 ms273274--- peer3.wg-test-one ping statistics ---2751 packets transmitted, 1 received, 0% packet loss, time 0ms276rtt min/avg/max/mdev = 0.644/0.644/0.644/0.000 ms277(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)278279--- Pinging from peer2 to controller1.wg-test-one ---280peer2: waiting for success: ping -c1 controller1.wg-test-one >&2281+ ping -c1 controller1.wg-test-one282PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes28364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.216 ms284285--- controller1.wg-test-one ping statistics ---2861 packets transmitted, 1 received, 0% packet loss, time 0ms287rtt min/avg/max/mdev = 0.216/0.216/0.216/0.000 ms288(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)289290--- Pinging from peer2 to controller2.wg-test-one ---291peer2: waiting for success: ping -c1 controller2.wg-test-one >&2292+ ping -c1 controller2.wg-test-one293PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes29464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.279 ms295296--- controller2.wg-test-one ping statistics ---2971 packets transmitted, 1 received, 0% packet loss, time 0ms298rtt min/avg/max/mdev = 0.279/0.279/0.279/0.000 ms299(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)300301--- Pinging from peer3 to peer1.wg-test-one ---302peer3: waiting for success: ping -c1 peer1.wg-test-one >&2303+ ping -c1 peer1.wg-test-one304PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes30564 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.479 ms306307--- peer1.wg-test-one ping statistics ---3081 packets transmitted, 1 received, 0% packet loss, time 0ms309rtt min/avg/max/mdev = 0.479/0.479/0.479/0.000 ms310(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)311312--- Pinging from peer3 to peer2.wg-test-one ---313peer3: waiting for success: ping -c1 peer2.wg-test-one >&2314+ ping -c1 peer2.wg-test-one315PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes31664 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.572 ms317318--- peer2.wg-test-one ping statistics ---3191 packets transmitted, 1 received, 0% packet loss, time 0ms320rtt min/avg/max/mdev = 0.572/0.572/0.572/0.000 ms321(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)322323--- Pinging from peer3 to controller1.wg-test-one ---324peer3: waiting for success: ping -c1 controller1.wg-test-one >&2325+ ping -c1 controller1.wg-test-one326PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes32764 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.269 ms328329--- controller1.wg-test-one ping statistics ---3301 packets transmitted, 1 received, 0% packet loss, time 0ms331rtt min/avg/max/mdev = 0.269/0.269/0.269/0.000 ms332(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)333334--- Pinging from peer3 to controller2.wg-test-one ---335peer3: waiting for success: ping -c1 controller2.wg-test-one >&2336+ ping -c1 controller2.wg-test-one337PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes33864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.254 ms339340--- controller2.wg-test-one ping statistics ---3411 packets transmitted, 1 received, 0% packet loss, time 0ms342rtt min/avg/max/mdev = 0.254/0.254/0.254/0.000 ms343(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)344345--- Pinging from controller1 to peer1.wg-test-one ---346controller1: waiting for success: ping -c1 peer1.wg-test-one >&2347+ ping -c1 peer1.wg-test-one348PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes34964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.533 ms350351--- peer1.wg-test-one ping statistics ---3521 packets transmitted, 1 received, 0% packet loss, time 0ms353rtt min/avg/max/mdev = 0.533/0.533/0.533/0.000 ms354(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)355356--- Pinging from controller1 to peer2.wg-test-one ---357controller1: waiting for success: ping -c1 peer2.wg-test-one >&2358+ ping -c1 peer2.wg-test-one359PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes36064 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.255 ms361362--- peer2.wg-test-one ping statistics ---3631 packets transmitted, 1 received, 0% packet loss, time 0ms364rtt min/avg/max/mdev = 0.255/0.255/0.255/0.000 ms365(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)366367--- Pinging from controller1 to peer3.wg-test-one ---368controller1: waiting for success: ping -c1 peer3.wg-test-one >&2369+ ping -c1 peer3.wg-test-one370PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes37164 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.243 ms372373--- peer3.wg-test-one ping statistics ---3741 packets transmitted, 1 received, 0% packet loss, time 0ms375rtt min/avg/max/mdev = 0.243/0.243/0.243/0.000 ms376(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)377378--- Pinging from controller1 to controller2.wg-test-one ---379controller1: waiting for success: ping -c1 controller2.wg-test-one >&2380+ ping -c1 controller2.wg-test-one381PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes38264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.318 ms383384--- controller2.wg-test-one ping statistics ---3851 packets transmitted, 1 received, 0% packet loss, time 0ms386rtt min/avg/max/mdev = 0.318/0.318/0.318/0.000 ms387(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)388389--- Pinging from controller2 to peer1.wg-test-one ---390controller2: waiting for success: ping -c1 peer1.wg-test-one >&2391+ ping -c1 peer1.wg-test-one392PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes39364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.299 ms394395--- peer1.wg-test-one ping statistics ---3961 packets transmitted, 1 received, 0% packet loss, time 0ms397rtt min/avg/max/mdev = 0.299/0.299/0.299/0.000 ms398(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)399400--- Pinging from controller2 to peer2.wg-test-one ---401controller2: waiting for success: ping -c1 peer2.wg-test-one >&2402+ ping -c1 peer2.wg-test-one403PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes40464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.250 ms405406--- peer2.wg-test-one ping statistics ---4071 packets transmitted, 1 received, 0% packet loss, time 0ms408rtt min/avg/max/mdev = 0.250/0.250/0.250/0.000 ms409(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)410411--- Pinging from controller2 to peer3.wg-test-one ---412controller2: waiting for success: ping -c1 peer3.wg-test-one >&2413+ ping -c1 peer3.wg-test-one414PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes41564 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.289 ms416417--- peer3.wg-test-one ping statistics ---4181 packets transmitted, 1 received, 0% packet loss, time 0ms419rtt min/avg/max/mdev = 0.289/0.289/0.289/0.000 ms420(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)421422--- Pinging from controller2 to controller1.wg-test-one ---423controller2: waiting for success: ping -c1 controller1.wg-test-one >&2424+ ping -c1 controller1.wg-test-one425PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes42664 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.261 ms427428--- controller1.wg-test-one ping statistics ---4291 packets transmitted, 1 received, 0% packet loss, time 0ms430rtt min/avg/max/mdev = 0.261/0.261/0.261/0.000 ms431(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)432433434435436