container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #814
· raw
1build01: building vrmzmbqnyjahwf299jz38sg4rsa4chkw-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 peer310111213141516<<< NixOS Stage 2 >>>1718booting system configuration /nix/store/8q31lc6pv23yqrcyvmnbldsapgp8pgh3-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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 3f426885-fd99-4fb3-b053-8d42fef73a2f'38Running as unit: run-p315-i28351345.service; invocation ID: 5227b4b304c94fcbad88e76e1537189639To attach to container controller1 run on the same machine that runs the test:40 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*3f426885-fd99-4fb3-b053-8d42fef73a2f') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4142To inject external network and continue test, run:43sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 3f426885-fd99-4fb3-b053-8d42fef73a2f4445<<< NixOS Stage 2 >>>4647booting system configuration /nix/store/38m75pwxsq7ckiyfib4h69v2cv3dfflf-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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 49e08cf6-6856-4aa4-ad66-772af09afec8'67Running as unit: run-p315-i28351350.service; invocation ID: 3b02d4fcd7c143c5bed286d58db1947968To attach to container controller2 run on the same machine that runs the test:69 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*49e08cf6-6856-4aa4-ad66-772af09afec8') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 7071To inject external network and continue test, run:72sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 49e08cf6-6856-4aa4-ad66-772af09afec87374<<< NixOS Stage 2 >>>7576booting system configuration /nix/store/plxrmm2rnanmi1wrbxsmnxx5wbrhg8rp-nixos-system-peer1-test77running activation script...78setting up /etc...792: host0@if3: <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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 1a0acd76-bf27-4f41-8ca7-c7785946b3f6'96Running as unit: run-p313-i28351372.service; invocation ID: 134ef95dd26e4c78a5cccd753896492797To attach to container peer1 run on the same machine that runs the test:98 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*1a0acd76-bf27-4f41-8ca7-c7785946b3f6') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 99100To inject external network and continue test, run:101sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 1a0acd76-bf27-4f41-8ca7-c7785946b3f6102103<<< NixOS Stage 2 >>>104105booting system configuration /nix/store/9wvlqv00pand0njgcr83b35kyh7yc6wz-nixos-system-peer2-test106running activation script...107setting up /etc...1082: host0@if4: <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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 17ff89b1-886a-47a1-8bfb-480ab69f8d05'125Running as unit: run-p313-i28351377.service; invocation ID: bf8e0878baa34d25b6d67ff56ec423d8126To attach to container peer2 run on the same machine that runs the test:127 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*17ff89b1-886a-47a1-8bfb-480ab69f8d05') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 128129To inject external network and continue test, run:130sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 17ff89b1-886a-47a1-8bfb-480ab69f8d05131132<<< NixOS Stage 2 >>>133134booting system configuration /nix/store/6ysc4k5jfmpkghac21wh23q3g5mjmcsr-nixos-system-peer3-test135running activation script...136setting up /etc...1372: host0@if6: <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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo dfb88a19-950d-42ae-89eb-a1d19b214367'154Running as unit: run-p313-i28351381.service; invocation ID: e54e44d342244752a993b61ddd290c88155To attach to container peer3 run on the same machine that runs the test:156 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*dfb88a19-950d-42ae-89eb-a1d19b214367') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 157158To inject external network and continue test, run:159sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py dfb88a19-950d-42ae-89eb-a1d19b214367160+ 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 bytes19264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.562 ms193194--- peer2.wg-test-one ping statistics ---1951 packets transmitted, 1 received, 0% packet loss, time 0ms196rtt min/avg/max/mdev = 0.562/0.562/0.562/0.000 ms197(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.78 seconds)198199--- Pinging from peer1 to peer3.wg-test-one ---200peer1: waiting for success: ping -c1 peer3.wg-test-one >&2201+ ping -c1 peer3.wg-test-one202PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes20364 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.560 ms204205--- peer3.wg-test-one ping statistics ---2061 packets transmitted, 1 received, 0% packet loss, time 0ms207rtt min/avg/max/mdev = 0.560/0.560/0.560/0.000 ms208(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)209210--- Pinging from peer1 to controller1.wg-test-one ---211peer1: waiting for success: ping -c1 controller1.wg-test-one >&2212+ ping -c1 controller1.wg-test-one213PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes21464 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.251 ms215216--- controller1.wg-test-one ping statistics ---2171 packets transmitted, 1 received, 0% packet loss, time 0ms218rtt min/avg/max/mdev = 0.251/0.251/0.251/0.000 ms219(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)220221--- Pinging from peer1 to controller2.wg-test-one ---222peer1: waiting for success: ping -c1 controller2.wg-test-one >&2223+ ping -c1 controller2.wg-test-one224PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes22564 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.299 ms226227--- controller2.wg-test-one ping statistics ---2281 packets transmitted, 1 received, 0% packet loss, time 0ms229rtt min/avg/max/mdev = 0.299/0.299/0.299/0.000 ms230(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)231232--- Pinging from peer2 to peer1.wg-test-one ---233peer2: waiting for success: ping -c1 peer1.wg-test-one >&2234+ ping -c1 peer1.wg-test-one235PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes23664 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.493 ms237238--- peer1.wg-test-one ping statistics ---2391 packets transmitted, 1 received, 0% packet loss, time 0ms240rtt min/avg/max/mdev = 0.493/0.493/0.493/0.000 ms241(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)242243--- Pinging from peer2 to peer3.wg-test-one ---244peer2: waiting for success: ping -c1 peer3.wg-test-one >&2245+ ping -c1 peer3.wg-test-one246PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes24764 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.551 ms248249--- peer3.wg-test-one ping statistics ---2501 packets transmitted, 1 received, 0% packet loss, time 0ms251rtt min/avg/max/mdev = 0.551/0.551/0.551/0.000 ms252(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)253254--- Pinging from peer2 to controller1.wg-test-one ---255peer2: waiting for success: ping -c1 controller1.wg-test-one >&2256+ ping -c1 controller1.wg-test-one257PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes25864 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.227 ms259260--- controller1.wg-test-one ping statistics ---2611 packets transmitted, 1 received, 0% packet loss, time 0ms262rtt min/avg/max/mdev = 0.227/0.227/0.227/0.000 ms263(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)264265--- Pinging from peer2 to controller2.wg-test-one ---266peer2: waiting for success: ping -c1 controller2.wg-test-one >&2267+ ping -c1 controller2.wg-test-one268PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes26964 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.548 ms270271--- controller2.wg-test-one ping statistics ---2721 packets transmitted, 1 received, 0% packet loss, time 0ms273rtt min/avg/max/mdev = 0.548/0.548/0.548/0.000 ms274(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)275276--- Pinging from peer3 to peer1.wg-test-one ---277peer3: waiting for success: ping -c1 peer1.wg-test-one >&2278+ ping -c1 peer1.wg-test-one279PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes28064 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.415 ms281282--- peer1.wg-test-one ping statistics ---2831 packets transmitted, 1 received, 0% packet loss, time 0ms284rtt min/avg/max/mdev = 0.415/0.415/0.415/0.000 ms285(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)286287--- Pinging from peer3 to peer2.wg-test-one ---288peer3: waiting for success: ping -c1 peer2.wg-test-one >&2289+ ping -c1 peer2.wg-test-one290PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes29164 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.451 ms292293--- peer2.wg-test-one ping statistics ---2941 packets transmitted, 1 received, 0% packet loss, time 0ms295rtt min/avg/max/mdev = 0.451/0.451/0.451/0.000 ms296(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)297298--- Pinging from peer3 to controller1.wg-test-one ---299peer3: waiting for success: ping -c1 controller1.wg-test-one >&2300+ ping -c1 controller1.wg-test-one301PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes30264 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.215 ms303304--- controller1.wg-test-one ping statistics ---3051 packets transmitted, 1 received, 0% packet loss, time 0ms306rtt min/avg/max/mdev = 0.215/0.215/0.215/0.000 ms307(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)308309--- Pinging from peer3 to controller2.wg-test-one ---310peer3: waiting for success: ping -c1 controller2.wg-test-one >&2311+ ping -c1 controller2.wg-test-one312PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes31364 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.211 ms314315--- controller2.wg-test-one ping statistics ---3161 packets transmitted, 1 received, 0% packet loss, time 0ms317rtt min/avg/max/mdev = 0.211/0.211/0.211/0.000 ms318(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)319320--- Pinging from controller1 to peer1.wg-test-one ---321controller1: waiting for success: ping -c1 peer1.wg-test-one >&2322+ ping -c1 peer1.wg-test-one323PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes32464 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.260 ms325326--- peer1.wg-test-one ping statistics ---3271 packets transmitted, 1 received, 0% packet loss, time 0ms328rtt min/avg/max/mdev = 0.260/0.260/0.260/0.000 ms329(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)330331--- Pinging from controller1 to peer2.wg-test-one ---332controller1: waiting for success: ping -c1 peer2.wg-test-one >&2333+ ping -c1 peer2.wg-test-one334PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes33564 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.238 ms336337--- peer2.wg-test-one ping statistics ---3381 packets transmitted, 1 received, 0% packet loss, time 0ms339rtt min/avg/max/mdev = 0.238/0.238/0.238/0.000 ms340(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)341342--- Pinging from controller1 to peer3.wg-test-one ---343controller1: waiting for success: ping -c1 peer3.wg-test-one >&2344+ ping -c1 peer3.wg-test-one345PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes34664 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.180 ms347348--- peer3.wg-test-one ping statistics ---3491 packets transmitted, 1 received, 0% packet loss, time 0ms350rtt min/avg/max/mdev = 0.180/0.180/0.180/0.000 ms351(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)352353--- Pinging from controller1 to controller2.wg-test-one ---354controller1: waiting for success: ping -c1 controller2.wg-test-one >&2355+ ping -c1 controller2.wg-test-one356PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes35764 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.309 ms358359--- controller2.wg-test-one ping statistics ---3601 packets transmitted, 1 received, 0% packet loss, time 0ms361rtt min/avg/max/mdev = 0.309/0.309/0.309/0.000 ms362(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)363364--- Pinging from controller2 to peer1.wg-test-one ---365controller2: waiting for success: ping -c1 peer1.wg-test-one >&2366+ ping -c1 peer1.wg-test-one367PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes36864 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.235 ms369370--- peer1.wg-test-one ping statistics ---3711 packets transmitted, 1 received, 0% packet loss, time 0ms372rtt min/avg/max/mdev = 0.235/0.235/0.235/0.000 ms373(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)374375--- Pinging from controller2 to peer2.wg-test-one ---376controller2: waiting for success: ping -c1 peer2.wg-test-one >&2377+ ping -c1 peer2.wg-test-one378PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes37964 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.272 ms380381--- peer2.wg-test-one ping statistics ---3821 packets transmitted, 1 received, 0% packet loss, time 0ms383rtt min/avg/max/mdev = 0.272/0.272/0.272/0.000 ms384(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)385386--- Pinging from controller2 to peer3.wg-test-one ---387controller2: waiting for success: ping -c1 peer3.wg-test-one >&2388+ ping -c1 peer3.wg-test-one389PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes39064 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.230 ms391392--- peer3.wg-test-one ping statistics ---3931 packets transmitted, 1 received, 0% packet loss, time 0ms394rtt min/avg/max/mdev = 0.230/0.230/0.230/0.000 ms395(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)396397--- Pinging from controller2 to controller1.wg-test-one ---398controller2: waiting for success: ping -c1 controller1.wg-test-one >&2399+ ping -c1 controller1.wg-test-one400PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes40164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.295 ms402403--- controller1.wg-test-one ping statistics ---4041 packets transmitted, 1 received, 0% packet loss, time 0ms405rtt min/avg/max/mdev = 0.295/0.295/0.295/0.000 ms406(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)407408409410411