build01: building igqmhwfyfarkjk68qmn9vfhajij03jlx-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 ░ Spawning container controller1 on /build/tmpleyag3ku/controller1. ░ Spawning container controller2 on /build/tmpleyag3ku/controller2. ░ Spawning container peer1 on /build/tmpleyag3ku/peer1. ░ Spawning container peer2 on /build/tmpleyag3ku/peer2. ░ Spawning container peer3 on /build/tmpleyag3ku/peer3. <<< NixOS Stage 2 >>> booting system configuration /nix/store/g9wxhm2nwgsr0xsmm4dhww57b77pxnqw-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.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 6482c468-60b1-47d8-84ba-eff0b6af5c04' Running as unit: run-p315-i20871823.service; invocation ID: d2b5045849fb440393d0d47d9e067944 To attach to container controller1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*6482c468-60b1-47d8-84ba-eff0b6af5c04') --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/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 6482c468-60b1-47d8-84ba-eff0b6af5c04 <<< NixOS Stage 2 >>> booting system configuration /nix/store/aggmbqzakcafjm0dynd4d3b5r80dx0n7-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.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 8d84e506-aec6-4548-9238-0298caf2cc3f' Running as unit: run-p315-i20871826.service; invocation ID: 67c829d372c24ba791523a2bfda33e73 To attach to container controller2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*8d84e506-aec6-4548-9238-0298caf2cc3f') --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/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 8d84e506-aec6-4548-9238-0298caf2cc3f <<< NixOS Stage 2 >>> booting system configuration /nix/store/rr88ygaas305map1y9k2bd3lrwh4v1s1-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.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 f555181e-2770-4b1e-bef0-ea4e589f25e0' Running as unit: run-p313-i20871829.service; invocation ID: cd601cb3bdd84069957fd4fd747bf4d1 To attach to container peer1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*f555181e-2770-4b1e-bef0-ea4e589f25e0') --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/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py f555181e-2770-4b1e-bef0-ea4e589f25e0 <<< NixOS Stage 2 >>> booting system configuration /nix/store/bybailnl6ffg85inr4j3lz1ggccfkxnj-nixos-system-peer2-test running activation script... setting up /etc... 2: host0@if3: 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 d617ac30-6a05-4f9b-81cb-16f0f2668717' Running as unit: run-p313-i20871834.service; invocation ID: 8181f9b4c12b42fe96fd964b9df23d72 To attach to container peer2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*d617ac30-6a05-4f9b-81cb-16f0f2668717') --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/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py d617ac30-6a05-4f9b-81cb-16f0f2668717 <<< NixOS Stage 2 >>> booting system configuration /nix/store/lc7wd6bciwsi6w3r2rr8vg1ay55z633b-nixos-system-peer3-test running activation script... setting up /etc... 2: host0@if4: 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 0a6f212d-5b32-464c-89ec-d54a6ca2b096' Running as unit: run-p313-i20871838.service; invocation ID: a14fc505272f489c838c0758e87b3b90 To attach to container peer3 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*0a6f212d-5b32-464c-89ec-d54a6ca2b096') --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/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 0a6f212d-5b32-464c-89ec-d54a6ca2b096 + 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 From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms + 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.700 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.700/0.700/0.700/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 4.61 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.67 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.665/3.665/3.665/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.231 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.231/0.231/0.231/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.283 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.283/0.283/0.283/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.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 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.825 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.825/0.825/0.825/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.266 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.266/0.266/0.266/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.298 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.298/0.298/0.298/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.521 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.521/0.521/0.521/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.543 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.543/0.543/0.543/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.243 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.243/0.243/0.243/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.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 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.285 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.285/0.285/0.285/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.268 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.268/0.268/0.268/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.204 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.204/0.204/0.204/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=0.440 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.440/0.440/0.440/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.284 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/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.250 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.250/0.250/0.250/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.775 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.775/0.775/0.775/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.336 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.336/0.336/0.336/0.000 ms (finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds) Container controller1 terminated by signal KILL. Container controller2 terminated by signal KILL. Container peer1 terminated by signal KILL. Container peer2 terminated by signal KILL. Container peer3 terminated by signal KILL.