additionally exposed symbols: controller1, controller2, peer1, peer2, peer3, start_all, machines, driver, Machine, wait_for_signal Starting controller1 Starting controller2 Starting peer1 Starting peer2 Starting peer3 <<< NixOS Stage 2 >>> booting system configuration /nix/store/wjr9kqxn9pdvmlcmsn8zzzx20l0nviik-nixos-system-controller1-test running activation script... setting up /etc... 2: host0@if7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether ba:9c:76:d8:39:5a brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 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) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 328c3940-9e1e-49c6-b0bf-f60e654e0bd7' Running as unit: run-p315-i6973751.service; invocation ID: c0ea8dc8509c42dea83476df3023d74f To attach to container controller1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*328c3940-9e1e-49c6-b0bf-f60e654e0bd7') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 328c3940-9e1e-49c6-b0bf-f60e654e0bd7 <<< NixOS Stage 2 >>> booting system configuration /nix/store/ad3dy4q1802hyyha1sgfx4x4cb5n02yg-nixos-system-controller2-test running activation script... setting up /etc... 2: host0@if6: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether e2:8c:47:a0:40:ce brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 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) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 791a5862-f011-4938-aee2-c5a5924949a4' Running as unit: run-p315-i6973762.service; invocation ID: 9ecdeb1299f74565a87084a99a9ed712 To attach to container controller2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*791a5862-f011-4938-aee2-c5a5924949a4') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 791a5862-f011-4938-aee2-c5a5924949a4 <<< NixOS Stage 2 >>> booting system configuration /nix/store/kdykzcl87x3l951jcmbgcp71sq47iwg2-nixos-system-peer1-test running activation script... setting up /etc... 2: host0@if5: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 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) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 83e1b6f0-5658-4c7f-a755-5033a7aa0fa5' Running as unit: run-p313-i6973787.service; invocation ID: 31b703da99d74728b05d716e194a5296 To attach to container peer1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*83e1b6f0-5658-4c7f-a755-5033a7aa0fa5') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 83e1b6f0-5658-4c7f-a755-5033a7aa0fa5 <<< NixOS Stage 2 >>> booting system configuration /nix/store/qr2j7ckw0iqlkb5g4f5a9gr6q8nrsdm5-nixos-system-peer2-test running activation script... setting up /etc... 2: host0@if4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 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) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 48915ec7-8c7d-4b02-b13b-ffbdb7895ff6' Running as unit: run-p313-i6973790.service; invocation ID: b93e836fc9cc4f61a3cc6d9a2219cbc8 To attach to container peer2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*48915ec7-8c7d-4b02-b13b-ffbdb7895ff6') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 48915ec7-8c7d-4b02-b13b-ffbdb7895ff6 <<< NixOS Stage 2 >>> booting system configuration /nix/store/fcvfgq7ic8wgnfsdzq22rvcqgc80wk21-nixos-system-peer3-test running activation script... setting up /etc... 2: host0@if3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 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) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 3d64eccc-32ce-4e6f-aada-18ba155f6cff' Running as unit: run-p313-i6973793.service; invocation ID: a341157c16674c44a1c9550a30065c89 To attach to container peer3 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*3d64eccc-32ce-4e6f-aada-18ba155f6cff') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 3d64eccc-32ce-4e6f-aada-18ba155f6cff + systemctl start network-online.target + systemctl start network-online.target + systemctl start network-online.target + systemctl start network-online.target + systemctl start network-online.target + systemctl --no-pager show network-online.target + systemctl --no-pager show systemd-networkd.service + systemctl --no-pager show network-online.target + systemctl --no-pager show systemd-networkd.service + systemctl --no-pager show network-online.target + systemctl --no-pager show systemd-networkd.service + systemctl --no-pager show network-online.target + systemctl --no-pager show systemd-networkd.service + systemctl --no-pager show network-online.target + systemctl --no-pager show systemd-networkd.service ============================================================ STARTING PING TESTS ============================================================ --- Pinging from peer1 to peer2.wg-test-one --- peer1: waiting for success: ping -c1 peer2.wg-test-one >&2 + ping -c1 peer2.wg-test-one PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes 64 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=3636 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3635.900/3635.900/3635.900/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.65 seconds) --- Pinging from peer1 to peer3.wg-test-one --- peer1: waiting for success: ping -c1 peer3.wg-test-one >&2 + ping -c1 peer3.wg-test-one PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes 64 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=3.75 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.748/3.748/3.748/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds) --- Pinging from peer1 to controller1.wg-test-one --- peer1: waiting for success: ping -c1 controller1.wg-test-one >&2 + ping -c1 controller1.wg-test-one PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes 64 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.207 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.207/0.207/0.207/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer1 to controller2.wg-test-one --- peer1: waiting for success: ping -c1 controller2.wg-test-one >&2 + ping -c1 controller2.wg-test-one PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes 64 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.256 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.256/0.256/0.256/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer2 to peer1.wg-test-one --- peer2: waiting for success: ping -c1 peer1.wg-test-one >&2 + ping -c1 peer1.wg-test-one PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes 64 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.494 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.494/0.494/0.494/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer2 to peer3.wg-test-one --- peer2: waiting for success: ping -c1 peer3.wg-test-one >&2 + ping -c1 peer3.wg-test-one PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes 64 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.756 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.756/0.756/0.756/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer2 to controller1.wg-test-one --- peer2: waiting for success: ping -c1 controller1.wg-test-one >&2 + ping -c1 controller1.wg-test-one PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes 64 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.382 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.382/0.382/0.382/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer2 to controller2.wg-test-one --- peer2: waiting for success: ping -c1 controller2.wg-test-one >&2 + ping -c1 controller2.wg-test-one PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes 64 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.274 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.274/0.274/0.274/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer3 to peer1.wg-test-one --- peer3: waiting for success: ping -c1 peer1.wg-test-one >&2 + ping -c1 peer1.wg-test-one PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes 64 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=1.22 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.215/1.215/1.215/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer3 to peer2.wg-test-one --- peer3: waiting for success: ping -c1 peer2.wg-test-one >&2 + ping -c1 peer2.wg-test-one PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes 64 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=1.67 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.674/1.674/1.674/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.02 seconds) --- Pinging from peer3 to controller1.wg-test-one --- peer3: waiting for success: ping -c1 controller1.wg-test-one >&2 + ping -c1 controller1.wg-test-one PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes 64 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.228 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.228/0.228/0.228/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds) --- Pinging from peer3 to controller2.wg-test-one --- peer3: waiting for success: ping -c1 controller2.wg-test-one >&2 + ping -c1 controller2.wg-test-one PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes 64 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.223 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.223/0.223/0.223/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds) --- Pinging from controller1 to peer1.wg-test-one --- controller1: waiting for success: ping -c1 peer1.wg-test-one >&2 + ping -c1 peer1.wg-test-one PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes 64 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.194 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.194/0.194/0.194/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds) --- Pinging from controller1 to peer2.wg-test-one --- controller1: waiting for success: ping -c1 peer2.wg-test-one >&2 + ping -c1 peer2.wg-test-one PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes 64 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.202 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.202/0.202/0.202/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds) --- Pinging from controller1 to peer3.wg-test-one --- controller1: waiting for success: ping -c1 peer3.wg-test-one >&2 + ping -c1 peer3.wg-test-one PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes 64 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.254 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.254/0.254/0.254/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds) --- Pinging from controller1 to controller2.wg-test-one --- controller1: waiting for success: ping -c1 controller2.wg-test-one >&2 + ping -c1 controller2.wg-test-one PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes 64 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=4674 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4674.363/4674.363/4674.363/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 4.69 seconds) --- Pinging from controller2 to peer1.wg-test-one --- controller2: waiting for success: ping -c1 peer1.wg-test-one >&2 + ping -c1 peer1.wg-test-one PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes 64 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.296 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.296/0.296/0.296/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds) --- Pinging from controller2 to peer2.wg-test-one --- controller2: waiting for success: ping -c1 peer2.wg-test-one >&2 + ping -c1 peer2.wg-test-one PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes 64 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.302 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.302/0.302/0.302/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.02 seconds) --- Pinging from controller2 to peer3.wg-test-one --- controller2: waiting for success: ping -c1 peer3.wg-test-one >&2 + ping -c1 peer3.wg-test-one PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes 64 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=2.55 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.553/2.553/2.553/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds) --- Pinging from controller2 to controller1.wg-test-one --- controller2: waiting for success: ping -c1 controller1.wg-test-one >&2 + ping -c1 controller1.wg-test-one PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes 64 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=6.96 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 6.964/6.964/6.964/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.02 seconds)