container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #1213
· raw
1build01: building zp9v48a971cbz17cak1rhlh05hgcbbj9-container-test-run-wireguard.drv2additionally exposed symbols:3 controller1, controller2, peer1, peer2, peer3,4 start_all, machines, driver, Machine, wait_for_signal5Starting controller16Starting controller27Starting peer18Starting peer29Starting peer310░ Spawning container controller1 on /build/tmpagvgch5_/controller1.11░ Spawning container controller2 on /build/tmpagvgch5_/controller2.12░ Spawning container peer1 on /build/tmpagvgch5_/peer1.13░ Spawning container peer2 on /build/tmpagvgch5_/peer2.14░ Spawning container peer3 on /build/tmpagvgch5_/peer3.1516<<< NixOS Stage 2 >>>1718booting system configuration /nix/store/54zmpfiwgc1hlh6g44kli6w22wk31636-nixos-system-controller1-test19running activation script...20setting up /etc...212: host0@if5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100022 link/ether ba:9c:76:d8:39:5a brd ff:ff:ff:ff:ff:ff link-netnsid 023setting up age secrets...24starting systemd...25systemd 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)26Detected virtualization systemd-nspawn.27Detected architecture arm64.28Detected first boot.29Initializing machine ID from container UUID.30Applying preset policy.31Populated /etc with preset unit settings.32Queued start job for default target Multi-User System.33343536<<< Welcome to NixOS test (aarch64) - console >>>37+ systemd-run /bin/sh -c '/nix/store/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 53d52ff0-466a-4beb-9da1-7f605733a3d1'38Running as unit: run-p315-i20897492.service; invocation ID: 0934dbf3173440ec8602bc7d97f41d1e39To attach to container controller1 run on the same machine that runs the test:40 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*53d52ff0-466a-4beb-9da1-7f605733a3d1') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4142To inject external network and continue test, run:43sudo /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 53d52ff0-466a-4beb-9da1-7f605733a3d14445<<< NixOS Stage 2 >>>4647booting system configuration /nix/store/r6grx2l91brpgwz42ri3bmklmdjy3kfl-nixos-system-controller2-test48running activation script...49setting up /etc...502: host0@if7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100051 link/ether e2:8c:47:a0:40:ce brd ff:ff:ff:ff:ff:ff link-netnsid 052setting up age secrets...53starting systemd...54systemd 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)55Detected virtualization systemd-nspawn.56Detected architecture arm64.57Detected first boot.58Initializing machine ID from container UUID.59Applying preset policy.60Populated /etc with preset unit settings.61Queued start job for default target Multi-User System.62636465<<< Welcome to NixOS test (aarch64) - console >>>66+ systemd-run /bin/sh -c '/nix/store/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 48aab333-789c-4d26-9046-1276ee3caa7f'67Running as unit: run-p315-i20897495.service; invocation ID: 378e43b540824276a8b4d347d57c8d8c68To attach to container controller2 run on the same machine that runs the test:69 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*48aab333-789c-4d26-9046-1276ee3caa7f') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 7071To inject external network and continue test, run:72sudo /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 48aab333-789c-4d26-9046-1276ee3caa7f7374<<< NixOS Stage 2 >>>7576booting system configuration /nix/store/nhyn4w1mv25cn7g4h2aqbcjwkrln4aji-nixos-system-peer1-test77running activation script...78setting up /etc...792: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100080 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 081setting up age secrets...82starting systemd...83systemd 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)84Detected virtualization systemd-nspawn.85Detected architecture arm64.86Detected first boot.87Initializing machine ID from container UUID.88Applying preset policy.89Populated /etc with preset unit settings.90Queued start job for default target Multi-User System.91929394<<< Welcome to NixOS test (aarch64) - console >>>95+ systemd-run /bin/sh -c '/nix/store/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 9913ed51-780a-447e-88e7-6d67befb671f'96Running as unit: run-p313-i20897498.service; invocation ID: a51e275c63194fab98888f283ab856df97To attach to container peer1 run on the same machine that runs the test:98 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*9913ed51-780a-447e-88e7-6d67befb671f') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 99100To inject external network and continue test, run:101sudo /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 9913ed51-780a-447e-88e7-6d67befb671f102103<<< NixOS Stage 2 >>>104105booting system configuration /nix/store/g3904ca25ihgazcl6d25agvmyswc01gn-nixos-system-peer2-test106running activation script...107setting up /etc...1082: host0@if6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000109 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0110setting up age secrets...111starting systemd...112systemd 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)113Detected virtualization systemd-nspawn.114Detected architecture arm64.115Detected first boot.116Initializing machine ID from container UUID.117Applying preset policy.118Populated /etc with preset unit settings.119Queued start job for default target Multi-User System.120121122123<<< Welcome to NixOS test (aarch64) - console >>>124+ systemd-run /bin/sh -c '/nix/store/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo f2ac70d3-1bac-4d57-82a8-3d3c8d0118a2'125Running as unit: run-p313-i20897503.service; invocation ID: ac223f57180647d88884e0f57ca1bf87126To attach to container peer2 run on the same machine that runs the test:127 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*f2ac70d3-1bac-4d57-82a8-3d3c8d0118a2') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 128129To inject external network and continue test, run:130sudo /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 f2ac70d3-1bac-4d57-82a8-3d3c8d0118a2131132<<< NixOS Stage 2 >>>133134booting system configuration /nix/store/g4rw30fkchsrcnhnixf91hmx2qy03sgb-nixos-system-peer3-test135running activation script...136setting up /etc...1372: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000138 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0139setting up age secrets...140starting systemd...141systemd 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)142Detected virtualization systemd-nspawn.143Detected architecture arm64.144Detected first boot.145Initializing machine ID from container UUID.146Applying preset policy.147Populated /etc with preset unit settings.148Queued start job for default target Multi-User System.149150151152<<< Welcome to NixOS test (aarch64) - console >>>153+ systemd-run /bin/sh -c '/nix/store/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo b0bfc501-cc6a-4827-83e0-c7375e54bfc8'154Running as unit: run-p313-i20897507.service; invocation ID: 84ba02bcdb5441048773fd3a98f52137155To attach to container peer3 run on the same machine that runs the test:156 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*b0bfc501-cc6a-4827-83e0-c7375e54bfc8') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 157158To inject external network and continue test, run:159sudo /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 b0bfc501-cc6a-4827-83e0-c7375e54bfc8160+ systemctl start network-online.target161+ systemctl start network-online.target162+ systemctl start network-online.target163+ systemctl start network-online.target164+ systemctl start network-online.target165+ systemctl --no-pager show network-online.target166+ systemctl --no-pager show systemd-networkd.service167+ systemctl --no-pager show network-online.target168+ systemctl --no-pager show systemd-networkd.service169+ systemctl --no-pager show network-online.target170+ systemctl --no-pager show systemd-networkd.service171+ systemctl --no-pager show network-online.target172+ systemctl --no-pager show systemd-networkd.service173+ systemctl --no-pager show network-online.target174+ systemctl --no-pager show systemd-networkd.service175176177============================================================178STARTING PING TESTS179============================================================180181--- Pinging from peer1 to peer2.wg-test-one ---182peer1: waiting for success: ping -c1 peer2.wg-test-one >&2183+ ping -c1 peer2.wg-test-one184PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes185From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable186187--- peer2.wg-test-one ping statistics ---1881 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms189190+ ping -c1 peer2.wg-test-one191PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes192From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable193194--- peer2.wg-test-one ping statistics ---1951 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms196197+ ping -c1 peer2.wg-test-one198PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes199From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable200201--- peer2.wg-test-one ping statistics ---2021 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms203204+ ping -c1 peer2.wg-test-one205PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes206From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable207208--- peer2.wg-test-one ping statistics ---2091 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms210211+ ping -c1 peer2.wg-test-one212PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes21364 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.626 ms214215--- peer2.wg-test-one ping statistics ---2161 packets transmitted, 1 received, 0% packet loss, time 0ms217rtt min/avg/max/mdev = 0.626/0.626/0.626/0.000 ms218(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 4.07 seconds)219220--- Pinging from peer1 to peer3.wg-test-one ---221peer1: waiting for success: ping -c1 peer3.wg-test-one >&2222+ ping -c1 peer3.wg-test-one223PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes22464 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.726 ms225226--- peer3.wg-test-one ping statistics ---2271 packets transmitted, 1 received, 0% packet loss, time 0ms228rtt min/avg/max/mdev = 0.726/0.726/0.726/0.000 ms229(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)230231--- Pinging from peer1 to controller1.wg-test-one ---232peer1: waiting for success: ping -c1 controller1.wg-test-one >&2233+ ping -c1 controller1.wg-test-one234PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes23564 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.303 ms236237--- controller1.wg-test-one ping statistics ---2381 packets transmitted, 1 received, 0% packet loss, time 0ms239rtt min/avg/max/mdev = 0.303/0.303/0.303/0.000 ms240(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)241242--- Pinging from peer1 to controller2.wg-test-one ---243peer1: waiting for success: ping -c1 controller2.wg-test-one >&2244+ ping -c1 controller2.wg-test-one245PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes24664 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.274 ms247248--- controller2.wg-test-one ping statistics ---2491 packets transmitted, 1 received, 0% packet loss, time 0ms250rtt min/avg/max/mdev = 0.274/0.274/0.274/0.000 ms251(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)252253--- Pinging from peer2 to peer1.wg-test-one ---254peer2: waiting for success: ping -c1 peer1.wg-test-one >&2255+ ping -c1 peer1.wg-test-one256PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes25764 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.600 ms258259--- peer1.wg-test-one ping statistics ---2601 packets transmitted, 1 received, 0% packet loss, time 0ms261rtt min/avg/max/mdev = 0.600/0.600/0.600/0.000 ms262(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)263264--- Pinging from peer2 to peer3.wg-test-one ---265peer2: waiting for success: ping -c1 peer3.wg-test-one >&2266+ ping -c1 peer3.wg-test-one267PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes26864 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.512 ms269270--- peer3.wg-test-one ping statistics ---2711 packets transmitted, 1 received, 0% packet loss, time 0ms272rtt min/avg/max/mdev = 0.512/0.512/0.512/0.000 ms273(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)274275--- Pinging from peer2 to controller1.wg-test-one ---276peer2: waiting for success: ping -c1 controller1.wg-test-one >&2277+ ping -c1 controller1.wg-test-one278PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes27964 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.270 ms280281--- controller1.wg-test-one ping statistics ---2821 packets transmitted, 1 received, 0% packet loss, time 0ms283rtt min/avg/max/mdev = 0.270/0.270/0.270/0.000 ms284(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)285286--- Pinging from peer2 to controller2.wg-test-one ---287peer2: waiting for success: ping -c1 controller2.wg-test-one >&2288+ ping -c1 controller2.wg-test-one289PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes29064 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.399 ms291292--- controller2.wg-test-one ping statistics ---2931 packets transmitted, 1 received, 0% packet loss, time 0ms294rtt min/avg/max/mdev = 0.399/0.399/0.399/0.000 ms295(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)296297--- Pinging from peer3 to peer1.wg-test-one ---298peer3: waiting for success: ping -c1 peer1.wg-test-one >&2299+ ping -c1 peer1.wg-test-one300PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes30164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.479 ms302303--- peer1.wg-test-one ping statistics ---3041 packets transmitted, 1 received, 0% packet loss, time 0ms305rtt min/avg/max/mdev = 0.479/0.479/0.479/0.000 ms306(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)307308--- Pinging from peer3 to peer2.wg-test-one ---309peer3: waiting for success: ping -c1 peer2.wg-test-one >&2310+ ping -c1 peer2.wg-test-one311PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes31264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.679 ms313314--- peer2.wg-test-one ping statistics ---3151 packets transmitted, 1 received, 0% packet loss, time 0ms316rtt min/avg/max/mdev = 0.679/0.679/0.679/0.000 ms317(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)318319--- Pinging from peer3 to controller1.wg-test-one ---320peer3: waiting for success: ping -c1 controller1.wg-test-one >&2321+ ping -c1 controller1.wg-test-one322PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes32364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=2.03 ms324325--- controller1.wg-test-one ping statistics ---3261 packets transmitted, 1 received, 0% packet loss, time 0ms327rtt min/avg/max/mdev = 2.026/2.026/2.026/0.000 ms328(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.02 seconds)329330--- Pinging from peer3 to controller2.wg-test-one ---331peer3: waiting for success: ping -c1 controller2.wg-test-one >&2332+ ping -c1 controller2.wg-test-one333PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes33464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.303 ms335336--- controller2.wg-test-one ping statistics ---3371 packets transmitted, 1 received, 0% packet loss, time 0ms338rtt min/avg/max/mdev = 0.303/0.303/0.303/0.000 ms339(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)340341--- Pinging from controller1 to peer1.wg-test-one ---342controller1: waiting for success: ping -c1 peer1.wg-test-one >&2343+ ping -c1 peer1.wg-test-one344PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes34564 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.278 ms346347--- peer1.wg-test-one ping statistics ---3481 packets transmitted, 1 received, 0% packet loss, time 0ms349rtt min/avg/max/mdev = 0.278/0.278/0.278/0.000 ms350(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)351352--- Pinging from controller1 to peer2.wg-test-one ---353controller1: waiting for success: ping -c1 peer2.wg-test-one >&2354+ ping -c1 peer2.wg-test-one355PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes35664 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.317 ms357358--- peer2.wg-test-one ping statistics ---3591 packets transmitted, 1 received, 0% packet loss, time 0ms360rtt min/avg/max/mdev = 0.317/0.317/0.317/0.000 ms361(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)362363--- Pinging from controller1 to peer3.wg-test-one ---364controller1: waiting for success: ping -c1 peer3.wg-test-one >&2365+ ping -c1 peer3.wg-test-one366PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes36764 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.356 ms368369--- peer3.wg-test-one ping statistics ---3701 packets transmitted, 1 received, 0% packet loss, time 0ms371rtt min/avg/max/mdev = 0.356/0.356/0.356/0.000 ms372(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)373374--- Pinging from controller1 to controller2.wg-test-one ---375controller1: waiting for success: ping -c1 controller2.wg-test-one >&2376+ ping -c1 controller2.wg-test-one377PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes37864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.394 ms379380--- controller2.wg-test-one ping statistics ---3811 packets transmitted, 1 received, 0% packet loss, time 0ms382rtt min/avg/max/mdev = 0.394/0.394/0.394/0.000 ms383(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)384385--- Pinging from controller2 to peer1.wg-test-one ---386controller2: waiting for success: ping -c1 peer1.wg-test-one >&2387+ ping -c1 peer1.wg-test-one388PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes38964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.334 ms390391--- peer1.wg-test-one ping statistics ---3921 packets transmitted, 1 received, 0% packet loss, time 0ms393rtt min/avg/max/mdev = 0.334/0.334/0.334/0.000 ms394(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)395396--- Pinging from controller2 to peer2.wg-test-one ---397controller2: waiting for success: ping -c1 peer2.wg-test-one >&2398+ ping -c1 peer2.wg-test-one399PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes40064 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.279 ms401402--- peer2.wg-test-one ping statistics ---4031 packets transmitted, 1 received, 0% packet loss, time 0ms404rtt min/avg/max/mdev = 0.279/0.279/0.279/0.000 ms405(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)406407--- Pinging from controller2 to peer3.wg-test-one ---408controller2: waiting for success: ping -c1 peer3.wg-test-one >&2409+ ping -c1 peer3.wg-test-one410PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes41164 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.355 ms412413--- peer3.wg-test-one ping statistics ---4141 packets transmitted, 1 received, 0% packet loss, time 0ms415rtt min/avg/max/mdev = 0.355/0.355/0.355/0.000 ms416(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)417418--- Pinging from controller2 to controller1.wg-test-one ---419controller2: waiting for success: ping -c1 controller1.wg-test-one >&2420+ ping -c1 controller1.wg-test-one421PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes42264 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.287 ms423424--- controller1.wg-test-one ping statistics ---4251 packets transmitted, 1 received, 0% packet loss, time 0ms426rtt min/avg/max/mdev = 0.287/0.287/0.287/0.000 ms427(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)428Container controller1 terminated by signal KILL.429Container controller2 terminated by signal KILL.430Container peer1 terminated by signal KILL.431Container peer2 terminated by signal KILL.432Container peer3 terminated by signal KILL.