container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #578
· 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/wg6ry4md2rk03r39ls1r1199wxhadcbz-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 a81764cb-cc9d-48c5-9f1e-91b262424041'37Running as unit: run-p315-i119032347.service; invocation ID: e9ed29065f83466e8836bcc3704b2bd938To attach to container controller1 run on the same machine that runs the test:39 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a81764cb-cc9d-48c5-9f1e-91b262424041') --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 a81764cb-cc9d-48c5-9f1e-91b2624240414344<<< NixOS Stage 2 >>>4546booting system configuration /nix/store/4yc8k0hlk31x2qn9j20mgniwxwx7y6ik-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 9ecf5d9b-2874-459d-9f58-71f72643da61'66Running as unit: run-p315-i119032350.service; invocation ID: 1f20f0a626f94d9aa038d08846290d8167To attach to container controller2 run on the same machine that runs the test:68 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*9ecf5d9b-2874-459d-9f58-71f72643da61') --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/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 9ecf5d9b-2874-459d-9f58-71f72643da617273<<< NixOS Stage 2 >>>7475booting system configuration /nix/store/ypv25kf8n51lw7ayi6fv96gsb8lglxk8-nixos-system-peer1-test76running activation script...77setting up /etc...782: host0@if6: <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 ec9b2abc-6376-4854-bbd9-3a2e086ee286'95Running as unit: run-p313-i119032353.service; invocation ID: 74534789d8cc47dcbe978d1d3da302e896To attach to container peer1 run on the same machine that runs the test:97 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*ec9b2abc-6376-4854-bbd9-3a2e086ee286') --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/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py ec9b2abc-6376-4854-bbd9-3a2e086ee286101102<<< NixOS Stage 2 >>>103104booting system configuration /nix/store/igxg0i3bd4la2a36lxalr2h4mds69w0w-nixos-system-peer2-test105running activation script...106setting up /etc...1072: host0@if7: <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 53215f1f-c46a-4862-9f9d-72508bc65a9e'124Running as unit: run-p313-i119032358.service; invocation ID: 8a5e88b1b36b4c1b80d961d1add1d182125To attach to container peer2 run on the same machine that runs the test:126 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*53215f1f-c46a-4862-9f9d-72508bc65a9e') --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/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 53215f1f-c46a-4862-9f9d-72508bc65a9e130131<<< NixOS Stage 2 >>>132133booting system configuration /nix/store/clcqm4j3pzhbm1jrbybkm64gy00ppy56-nixos-system-peer3-test134running activation script...135setting up /etc...1362: host0@if5: <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 79f48354-87ef-446c-a3a4-c15803fd8a17'153Running as unit: run-p313-i119032362.service; invocation ID: c9d9ef64844847f78bc5446160318c49154To attach to container peer3 run on the same machine that runs the test:155 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*79f48354-87ef-446c-a3a4-c15803fd8a17') --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/f4nvkcws5x7zcpbn7zsscrdviq2jxrpi-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 79f48354-87ef-446c-a3a4-c15803fd8a17159+ 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 bytes184From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable185186--- peer2.wg-test-one ping statistics ---1871 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms188189+ ping -c1 peer2.wg-test-one190PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes191From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable192193--- peer2.wg-test-one ping statistics ---1941 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms195196+ ping -c1 peer2.wg-test-one197PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes198From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable199200--- peer2.wg-test-one ping statistics ---2011 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms202203+ ping -c1 peer2.wg-test-one204PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes205From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable206207--- peer2.wg-test-one ping statistics ---2081 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms209210+ ping -c1 peer2.wg-test-one211PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes21264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.601 ms213214--- peer2.wg-test-one ping statistics ---2151 packets transmitted, 1 received, 0% packet loss, time 0ms216rtt min/avg/max/mdev = 0.601/0.601/0.601/0.000 ms217(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 4.07 seconds)218219--- Pinging from peer1 to peer3.wg-test-one ---220peer1: waiting for success: ping -c1 peer3.wg-test-one >&2221+ ping -c1 peer3.wg-test-one222PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes22364 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.563 ms224225--- peer3.wg-test-one ping statistics ---2261 packets transmitted, 1 received, 0% packet loss, time 0ms227rtt min/avg/max/mdev = 0.563/0.563/0.563/0.000 ms228(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)229230--- Pinging from peer1 to controller1.wg-test-one ---231peer1: waiting for success: ping -c1 controller1.wg-test-one >&2232+ ping -c1 controller1.wg-test-one233PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes23464 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.249 ms235236--- controller1.wg-test-one ping statistics ---2371 packets transmitted, 1 received, 0% packet loss, time 0ms238rtt min/avg/max/mdev = 0.249/0.249/0.249/0.000 ms239(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)240241--- Pinging from peer1 to controller2.wg-test-one ---242peer1: waiting for success: ping -c1 controller2.wg-test-one >&2243+ ping -c1 controller2.wg-test-one244PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes24564 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.206 ms246247--- controller2.wg-test-one ping statistics ---2481 packets transmitted, 1 received, 0% packet loss, time 0ms249rtt min/avg/max/mdev = 0.206/0.206/0.206/0.000 ms250(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)251252--- Pinging from peer2 to peer1.wg-test-one ---253peer2: waiting for success: ping -c1 peer1.wg-test-one >&2254+ ping -c1 peer1.wg-test-one255PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes25664 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.483 ms257258--- peer1.wg-test-one ping statistics ---2591 packets transmitted, 1 received, 0% packet loss, time 0ms260rtt min/avg/max/mdev = 0.483/0.483/0.483/0.000 ms261(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)262263--- Pinging from peer2 to peer3.wg-test-one ---264peer2: waiting for success: ping -c1 peer3.wg-test-one >&2265+ ping -c1 peer3.wg-test-one266PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes26764 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.466 ms268269--- peer3.wg-test-one ping statistics ---2701 packets transmitted, 1 received, 0% packet loss, time 0ms271rtt min/avg/max/mdev = 0.466/0.466/0.466/0.000 ms272(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)273274--- Pinging from peer2 to controller1.wg-test-one ---275peer2: waiting for success: ping -c1 controller1.wg-test-one >&2276+ ping -c1 controller1.wg-test-one277PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes27864 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.228 ms279280--- controller1.wg-test-one ping statistics ---2811 packets transmitted, 1 received, 0% packet loss, time 0ms282rtt min/avg/max/mdev = 0.228/0.228/0.228/0.000 ms283(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)284285--- Pinging from peer2 to controller2.wg-test-one ---286peer2: waiting for success: ping -c1 controller2.wg-test-one >&2287+ ping -c1 controller2.wg-test-one288PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes28964 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.290 ms290291--- controller2.wg-test-one ping statistics ---2921 packets transmitted, 1 received, 0% packet loss, time 0ms293rtt min/avg/max/mdev = 0.290/0.290/0.290/0.000 ms294(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)295296--- Pinging from peer3 to peer1.wg-test-one ---297peer3: waiting for success: ping -c1 peer1.wg-test-one >&2298+ ping -c1 peer1.wg-test-one299PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes30064 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.551 ms301302--- peer1.wg-test-one ping statistics ---3031 packets transmitted, 1 received, 0% packet loss, time 0ms304rtt min/avg/max/mdev = 0.551/0.551/0.551/0.000 ms305(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)306307--- Pinging from peer3 to peer2.wg-test-one ---308peer3: waiting for success: ping -c1 peer2.wg-test-one >&2309+ ping -c1 peer2.wg-test-one310PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes31164 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.443 ms312313--- peer2.wg-test-one ping statistics ---3141 packets transmitted, 1 received, 0% packet loss, time 0ms315rtt min/avg/max/mdev = 0.443/0.443/0.443/0.000 ms316(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)317318--- Pinging from peer3 to controller1.wg-test-one ---319peer3: waiting for success: ping -c1 controller1.wg-test-one >&2320+ ping -c1 controller1.wg-test-one321PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes32264 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.243 ms323324--- controller1.wg-test-one ping statistics ---3251 packets transmitted, 1 received, 0% packet loss, time 0ms326rtt min/avg/max/mdev = 0.243/0.243/0.243/0.000 ms327(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)328329--- Pinging from peer3 to controller2.wg-test-one ---330peer3: waiting for success: ping -c1 controller2.wg-test-one >&2331+ ping -c1 controller2.wg-test-one332PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes33364 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.244 ms334335--- controller2.wg-test-one ping statistics ---3361 packets transmitted, 1 received, 0% packet loss, time 0ms337rtt min/avg/max/mdev = 0.244/0.244/0.244/0.000 ms338(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)339340--- Pinging from controller1 to peer1.wg-test-one ---341controller1: waiting for success: ping -c1 peer1.wg-test-one >&2342+ ping -c1 peer1.wg-test-one343PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes34464 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=2.74 ms345346--- peer1.wg-test-one ping statistics ---3471 packets transmitted, 1 received, 0% packet loss, time 0ms348rtt min/avg/max/mdev = 2.740/2.740/2.740/0.000 ms349(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)350351--- Pinging from controller1 to peer2.wg-test-one ---352controller1: waiting for success: ping -c1 peer2.wg-test-one >&2353+ ping -c1 peer2.wg-test-one354PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes35564 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.219 ms356357--- peer2.wg-test-one ping statistics ---3581 packets transmitted, 1 received, 0% packet loss, time 0ms359rtt min/avg/max/mdev = 0.219/0.219/0.219/0.000 ms360(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)361362--- Pinging from controller1 to peer3.wg-test-one ---363controller1: waiting for success: ping -c1 peer3.wg-test-one >&2364+ ping -c1 peer3.wg-test-one365PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes36664 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.217 ms367368--- peer3.wg-test-one ping statistics ---3691 packets transmitted, 1 received, 0% packet loss, time 0ms370rtt min/avg/max/mdev = 0.217/0.217/0.217/0.000 ms371(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)372373--- Pinging from controller1 to controller2.wg-test-one ---374controller1: waiting for success: ping -c1 controller2.wg-test-one >&2375+ ping -c1 controller2.wg-test-one376PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes37764 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.310 ms378379--- controller2.wg-test-one ping statistics ---3801 packets transmitted, 1 received, 0% packet loss, time 0ms381rtt min/avg/max/mdev = 0.310/0.310/0.310/0.000 ms382(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)383384--- Pinging from controller2 to peer1.wg-test-one ---385controller2: waiting for success: ping -c1 peer1.wg-test-one >&2386+ ping -c1 peer1.wg-test-one387PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes38864 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.222 ms389390--- peer1.wg-test-one ping statistics ---3911 packets transmitted, 1 received, 0% packet loss, time 0ms392rtt min/avg/max/mdev = 0.222/0.222/0.222/0.000 ms393(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)394395--- Pinging from controller2 to peer2.wg-test-one ---396controller2: waiting for success: ping -c1 peer2.wg-test-one >&2397+ ping -c1 peer2.wg-test-one398PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes39964 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.224 ms400401--- peer2.wg-test-one ping statistics ---4021 packets transmitted, 1 received, 0% packet loss, time 0ms403rtt min/avg/max/mdev = 0.224/0.224/0.224/0.000 ms404(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)405406--- Pinging from controller2 to peer3.wg-test-one ---407controller2: waiting for success: ping -c1 peer3.wg-test-one >&2408+ ping -c1 peer3.wg-test-one409PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes41064 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.343 ms411412--- peer3.wg-test-one ping statistics ---4131 packets transmitted, 1 received, 0% packet loss, time 0ms414rtt min/avg/max/mdev = 0.343/0.343/0.343/0.000 ms415(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)416417--- Pinging from controller2 to controller1.wg-test-one ---418controller2: waiting for success: ping -c1 controller1.wg-test-one >&2419+ ping -c1 controller1.wg-test-one420PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes42164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.277 ms422423--- controller1.wg-test-one ping statistics ---4241 packets transmitted, 1 received, 0% packet loss, time 0ms425rtt min/avg/max/mdev = 0.277/0.277/0.277/0.000 ms426(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)427428429430431