build01: building rdx1bkcg8p11yyq3yd2zxavlz3pkp5pc-container-test-run-wireguard.drv 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/z51jxqddp4p3marni8czmbwxnr4mf7jc-nixos-system-controller1-test running activation script... setting up /etc... 2: host0@if4: 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.5 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/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 61b5a83b-0169-452d-8b3b-ccaee1cd717d' Running as unit: run-p315-i6263911.service; invocation ID: 3c5d43e18b664fcda48b57945493ed30 To attach to container controller1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*61b5a83b-0169-452d-8b3b-ccaee1cd717d') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/qq5ppp119nyp6wdn1gi4pr1xkmgs2ny1-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 61b5a83b-0169-452d-8b3b-ccaee1cd717d <<< NixOS Stage 2 >>> booting system configuration /nix/store/qkg20pjpf9mz3vk67xg6jkvgcazb33na-nixos-system-controller2-test running activation script... setting up /etc... 2: host0@if5: 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.5 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/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 45e6e5e2-f95d-47bb-9dff-480de0c9e5e7' Running as unit: run-p315-i6263914.service; invocation ID: 2981f9917f1d46aea07fe313ba591efe To attach to container controller2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*45e6e5e2-f95d-47bb-9dff-480de0c9e5e7') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/qq5ppp119nyp6wdn1gi4pr1xkmgs2ny1-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 45e6e5e2-f95d-47bb-9dff-480de0c9e5e7 <<< NixOS Stage 2 >>> booting system configuration /nix/store/sxi5dz41a7qzv9apgz696in2m6378wa8-nixos-system-peer1-test running activation script... setting up /etc... 2: host0@if7: 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.5 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/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo fd9454c3-b057-4c79-bc30-051ea6725f44' Running as unit: run-p313-i6263917.service; invocation ID: 12b67e53f1bb423db81a4ec90c08cf18 To attach to container peer1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*fd9454c3-b057-4c79-bc30-051ea6725f44') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/qq5ppp119nyp6wdn1gi4pr1xkmgs2ny1-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py fd9454c3-b057-4c79-bc30-051ea6725f44 <<< NixOS Stage 2 >>> booting system configuration /nix/store/9xg469zbbgcgk1kyy1p2gnchl2pl0bj0-nixos-system-peer2-test running activation script... setting up /etc... 2: host0@if6: 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.5 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/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 3fc6e329-bfbe-4841-8a61-61675ff5cdb7' Running as unit: run-p313-i6263922.service; invocation ID: f711ca5fe0d2425a887628bf505a0849 To attach to container peer2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*3fc6e329-bfbe-4841-8a61-61675ff5cdb7') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/qq5ppp119nyp6wdn1gi4pr1xkmgs2ny1-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 3fc6e329-bfbe-4841-8a61-61675ff5cdb7 <<< NixOS Stage 2 >>> booting system configuration /nix/store/i1qp3dk3hszrm2pflzv15y20pjihsifm-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.5 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/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 28287677-6ff4-4056-bbcf-c78257025fa5' Running as unit: run-p313-i6263926.service; invocation ID: e033105be9844568bd9ff314130d008d To attach to container peer3 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*28287677-6ff4-4056-bbcf-c78257025fa5') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/qq5ppp119nyp6wdn1gi4pr1xkmgs2ny1-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 28287677-6ff4-4056-bbcf-c78257025fa5 + 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=0.702 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.702/0.702/0.702/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 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=1.02 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.022/1.022/1.022/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.230 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.230/0.230/0.230/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.275 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.275/0.275/0.275/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.514 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.514/0.514/0.514/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.859 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.859/0.859/0.859/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.253 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.253/0.253/0.253/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.296 ms --- controller2.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 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=6.07 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 6.072/6.072/6.072/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.02 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=3230 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3230.244/3230.244/3230.244/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.24 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.356 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.356/0.356/0.356/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.301 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.301/0.301/0.301/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.327 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.327/0.327/0.327/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.468 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.468/0.468/0.468/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=3.50 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.501/3.501/3.501/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=2.50 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.502/2.502/2.502/0.000 ms (finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 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.327 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.327/0.327/0.327/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.314 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.314/0.314/0.314/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.311 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.311/0.311/0.311/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.261 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.261/0.261/0.261/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)