build01: building dsijd43fs20xi1fv8kc89qaml036c8kn-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/tmpx_oj4dxc/controller1. ░ Spawning container peer1 on /build/tmpx_oj4dxc/peer1. ░ Spawning container peer2 on /build/tmpx_oj4dxc/peer2. ░ Spawning container controller2 on /build/tmpx_oj4dxc/controller2. ░ Spawning container peer3 on /build/tmpx_oj4dxc/peer3. <<< NixOS Stage 2 >>> booting system configuration /nix/store/9dwqfgz3pzr5pyg9i1arag1278fbqn10-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.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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 5ebeb4c0-53b4-4b05-b08d-2e52a9b2902d' Running as unit: run-p315-i403275.service; invocation ID: 4fd0edcc76724852bbad1980e4638f3f To attach to container controller1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*5ebeb4c0-53b4-4b05-b08d-2e52a9b2902d') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 5ebeb4c0-53b4-4b05-b08d-2e52a9b2902d <<< NixOS Stage 2 >>> booting system configuration /nix/store/0jha0nsdk205przg21riys2zlrlvkg99-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.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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 661685dd-bc12-427e-92ca-091c24ce8e18' Running as unit: run-p315-i403278.service; invocation ID: 6c57a78ddbe74d68aff245de5eb38e01 To attach to container controller2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*661685dd-bc12-427e-92ca-091c24ce8e18') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 661685dd-bc12-427e-92ca-091c24ce8e18 <<< NixOS Stage 2 >>> booting system configuration /nix/store/ff357l91d4k4ciyazcda8nh5z16yjwzr-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.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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo e37c0717-8f7b-4b68-a406-6d3e51e99cd2' Running as unit: run-p313-i403388.service; invocation ID: 69e8467b1d4f40478b566cfadcdfa220 To attach to container peer1 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*e37c0717-8f7b-4b68-a406-6d3e51e99cd2') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py e37c0717-8f7b-4b68-a406-6d3e51e99cd2 <<< NixOS Stage 2 >>> booting system configuration /nix/store/cd2jf9d7axzb47y1xdccx958r95ndaii-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.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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 626f2a84-6a66-412e-a2bf-998c9ab3f522' Running as unit: run-p313-i403391.service; invocation ID: bebf4bdb93164098876c5c6773c3ecd8 To attach to container peer2 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*626f2a84-6a66-412e-a2bf-998c9ab3f522') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 626f2a84-6a66-412e-a2bf-998c9ab3f522 <<< NixOS Stage 2 >>> booting system configuration /nix/store/c5pk9cvf5blpanmb1jms8bfc23n7mhki-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.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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 68bfb2ce-b9cb-4678-bf8e-93b6f65a14d5' Running as unit: run-p313-i403395.service; invocation ID: 9898e2a3f6e341578666f846f8b89871 To attach to container peer3 run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*68bfb2ce-b9cb-4678-bf8e-93b6f65a14d5') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 68bfb2ce-b9cb-4678-bf8e-93b6f65a14d5 + 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=3802 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3802.400/3802.400/3802.400/0.000 ms (finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.82 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.558 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.558/0.558/0.558/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.195 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.195/0.195/0.195/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.603 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.603/0.603/0.603/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=3.32 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.320/3.320/3.320/0.000 ms (finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.02 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=4.16 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.157/4.157/4.157/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=2.57 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.573/2.573/2.573/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.267 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.267/0.267/0.267/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.435 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.435/0.435/0.435/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.499 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.499/0.499/0.499/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.195 ms --- controller1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.195/0.195/0.195/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=1.65 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.648/1.648/1.648/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.331 ms --- peer1.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.331/0.331/0.331/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.263 ms --- peer2.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 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=5.28 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 5.281/5.281/5.281/0.000 ms (finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 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=1.33 ms --- controller2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.325/1.325/1.325/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.266 ms --- peer1.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 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.229 ms --- peer2.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.229/0.229/0.229/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.214 ms --- peer3.wg-test-one ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.214/0.214/0.214/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.311 ms --- controller1.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 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.