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/lp3pa92y6ccw4yv9dkdswa6v7q69yz4p-nixos-system-controller1-test running activation script... setting up /etc... 2: host0@if3: 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 c9e929d0-c03d-4231-8733-46f7714a7ddf' Running as unit: run-p315-i3612369.service; invocation ID: efd32c2f6568441eba11f697301936b9 To attach to container controller1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*c9e929d0-c03d-4231-8733-46f7714a7ddf') --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 c9e929d0-c03d-4231-8733-46f7714a7ddf <<< NixOS Stage 2 >>> booting system configuration /nix/store/xcfn1q3wv2d6f6iqqil5igsflm1082p8-nixos-system-controller2-test running activation script... setting up /etc... 2: host0@if4: 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 4a5793c5-1e09-484a-b858-108e6beb5ff1' Running as unit: run-p315-i3612390.service; invocation ID: 57032cc4de7248a69f5685af353e545c To attach to container controller2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*4a5793c5-1e09-484a-b858-108e6beb5ff1') --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 4a5793c5-1e09-484a-b858-108e6beb5ff1 <<< NixOS Stage 2 >>> booting system configuration /nix/store/3w2dc04a4cwpg79j8l79ycmm1snx0iv5-nixos-system-peer1-test running activation script... setting up /etc... 2: host0@if6: 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 b57dfe68-d412-421e-b43f-7f47e227cdc5' Running as unit: run-p313-i3612395.service; invocation ID: 3131aa52e3f7426cb572a259d0035e91 To attach to container peer1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*b57dfe68-d412-421e-b43f-7f47e227cdc5') --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 b57dfe68-d412-421e-b43f-7f47e227cdc5 <<< NixOS Stage 2 >>> booting system configuration /nix/store/g3sdhd020sapgily6s53291drrd620j3-nixos-system-peer2-test running activation script... setting up /etc... 2: host0@if5: 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 b75a1ca1-acbc-4ed0-a22e-c0814ec3289d' Running as unit: run-p313-i3612399.service; invocation ID: 9672ffbfb35e47f88db6ca7dab1a5f53 To attach to container peer2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*b75a1ca1-acbc-4ed0-a22e-c0814ec3289d') --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 b75a1ca1-acbc-4ed0-a22e-c0814ec3289d <<< NixOS Stage 2 >>> booting system configuration /nix/store/czj2hl6cy9q6085vidyida2f0zwwd3gx-nixos-system-peer3-test running activation script... setting up /etc... 2: host0@if7: 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 08119066-daba-4fdf-8ea7-e13c375d3067' Running as unit: run-p313-i3612404.service; invocation ID: feda05bb5a3840d383e415961d449ef3 To attach to container peer3 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*08119066-daba-4fdf-8ea7-e13c375d3067') --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 08119066-daba-4fdf-8ea7-e13c375d3067 + 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=1305 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1304.690/1304.690/1304.690/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 1.31 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=0.477 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.477/0.477/0.477/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 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.302 ms --- controller1.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 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.211 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.211/0.211/0.211/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.480 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.480/0.480/0.480/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.380 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.380/0.380/0.380/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.211 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.211/0.211/0.211/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.244 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.244/0.244/0.244/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=0.546 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.546/0.546/0.546/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=0.438 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.438/0.438/0.438/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 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.219 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.219/0.219/0.219/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.197 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.197/0.197/0.197/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.205 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.205/0.205/0.205/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.206 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.206/0.206/0.206/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.263 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.263/0.263/0.263/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=4943 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4942.658/4942.658/4942.658/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 4.95 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.338 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.338/0.338/0.338/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.277 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.277/0.277/0.277/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 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=0.288 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.288/0.288/0.288/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 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=0.227 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.227/0.227/0.227/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)