container-test-run-wireguard
default.checks.aarch64-linux.wireguard
· build #311
· raw
1additionally exposed symbols:2 controller1, controller2, peer1, peer2, peer3,3 start_all, machines, driver, Machine, wait_for_signal4Starting controller15Starting controller26Starting peer17Starting peer28Starting peer391011121314151617181920<<< NixOS Stage 2 >>>2122booting system configuration /nix/store/n9pdmi0wbxzppabdfdcjnjjp3xkn35mz-nixos-system-controller1-test23running activation script...24setting up /etc...252: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100026 link/ether ba:9c:76:d8:39:5a brd ff:ff:ff:ff:ff:ff link-netnsid 027setting up age secrets...28starting systemd...29systemd 261.1 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)30Detected virtualization systemd-nspawn.31Detected architecture arm64.32Detected first boot.33Initializing machine ID from container UUID.34Applying preset policy.35Populated /etc with preset unit settings.36Queued start job for default target Multi-User System.37383940<<< Welcome to NixOS test (aarch64) - console >>>41+ systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo ecc93873-453d-4374-8a20-32a176b25165'42Running as unit: run-p316-i84323000.service; invocation ID: 56b9958abdd44f7dac1de70601ab7eef43To attach to container controller1 run on the same machine that runs the test:44 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*ecc93873-453d-4374-8a20-32a176b25165') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4546To inject external network and continue test, run:47sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py ecc93873-453d-4374-8a20-32a176b251654849<<< NixOS Stage 2 >>>5051booting system configuration /nix/store/li2j3mhpvdy38pcc5i076wgr2hlys2ay-nixos-system-controller2-test52running activation script...53setting up /etc...542: host0@if5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100055 link/ether e2:8c:47:a0:40:ce brd ff:ff:ff:ff:ff:ff link-netnsid 056setting up age secrets...57starting systemd...58systemd 261.1 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)59Detected virtualization systemd-nspawn.60Detected architecture arm64.61Detected first boot.62Initializing machine ID from container UUID.63Applying preset policy.64Populated /etc with preset unit settings.65Queued start job for default target Multi-User System.66676869<<< Welcome to NixOS test (aarch64) - console >>>70+ systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo 4bc607e7-e340-4e14-adc9-f718037dd1e3'71Running as unit: run-p316-i84323003.service; invocation ID: 6d78479268ce4b70854257b292c55e7f72To attach to container controller2 run on the same machine that runs the test:73 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*4bc607e7-e340-4e14-adc9-f718037dd1e3') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 7475To inject external network and continue test, run:76sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 4bc607e7-e340-4e14-adc9-f718037dd1e37778<<< NixOS Stage 2 >>>7980booting system configuration /nix/store/f28drxwfbmkzncv4j8k9j9w20a5cvm4m-nixos-system-peer1-test81running activation script...82setting up /etc...832: host0@if7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100084 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 085setting up age secrets...86starting systemd...87systemd 261.1 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)88Detected virtualization systemd-nspawn.89Detected architecture arm64.90Detected first boot.91Initializing machine ID from container UUID.92Applying preset policy.93Populated /etc with preset unit settings.94Queued start job for default target Multi-User System.95969798<<< Welcome to NixOS test (aarch64) - console >>>99+ systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo 09ebe3d1-d7e9-461a-b380-b418816ad742'100Running as unit: run-p314-i84323006.service; invocation ID: e054bdb6b27645ca982c4106ab6905cd101To attach to container peer1 run on the same machine that runs the test:102 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*09ebe3d1-d7e9-461a-b380-b418816ad742') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 103104To inject external network and continue test, run:105sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 09ebe3d1-d7e9-461a-b380-b418816ad742106107<<< NixOS Stage 2 >>>108109booting system configuration /nix/store/wvzgqnarx026kplr0h1pd9h88agxv9i9-nixos-system-peer2-test110running activation script...111setting up /etc...1122: host0@if6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000113 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0114setting up age secrets...115starting systemd...116systemd 261.1 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)117Detected virtualization systemd-nspawn.118Detected architecture arm64.119Detected first boot.120Initializing machine ID from container UUID.121Applying preset policy.122Populated /etc with preset unit settings.123Queued start job for default target Multi-User System.124125126127<<< Welcome to NixOS test (aarch64) - console >>>128+ systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo 60fbcba7-0b4a-48d9-9674-863f0f7685bf'129Running as unit: run-p314-i84323011.service; invocation ID: c916688eead2477e93dc0cc6886b598b130To attach to container peer2 run on the same machine that runs the test:131 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*60fbcba7-0b4a-48d9-9674-863f0f7685bf') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 132133To inject external network and continue test, run:134sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 60fbcba7-0b4a-48d9-9674-863f0f7685bf135136<<< NixOS Stage 2 >>>137138booting system configuration /nix/store/zrw5wppjxq9cq1fd78wx0iigx2b4plp8-nixos-system-peer3-test139running activation script...140setting up /etc...1412: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000142 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0143setting up age secrets...144starting systemd...145systemd 261.1 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)146Detected virtualization systemd-nspawn.147Detected architecture arm64.148Detected first boot.149Initializing machine ID from container UUID.150Applying preset policy.151Populated /etc with preset unit settings.152Queued start job for default target Multi-User System.153154155156<<< Welcome to NixOS test (aarch64) - console >>>157+ systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo c3e04f64-7a9b-4d8a-9864-2479c3057388'158Running as unit: run-p314-i84323015.service; invocation ID: 62fe58eefb864830a8796a413134d04d159To attach to container peer3 run on the same machine that runs the test:160 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*c3e04f64-7a9b-4d8a-9864-2479c3057388') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 161162To inject external network and continue test, run:163sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py c3e04f64-7a9b-4d8a-9864-2479c3057388164+ systemctl start network-online.target165+ systemctl start network-online.target166+ systemctl start network-online.target167+ systemctl start network-online.target168+ systemctl start network-online.target169+ 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.service175+ systemctl --no-pager show network-online.target176+ systemctl --no-pager show systemd-networkd.service177+ systemctl --no-pager show network-online.target178+ systemctl --no-pager show systemd-networkd.service179180181============================================================182STARTING PING TESTS183============================================================184185--- Pinging from peer1 to peer2.wg-test-one ---186peer1: waiting for success: ping -c1 peer2.wg-test-one >&2187+ ping -c1 peer2.wg-test-one188PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes18964 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=3438 ms190191--- peer2.wg-test-one ping statistics ---1921 packets transmitted, 1 received, 0% packet loss, time 0ms193rtt min/avg/max/mdev = 3438.381/3438.381/3438.381/0.000 ms194(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.45 seconds)195196--- Pinging from peer1 to peer3.wg-test-one ---197peer1: waiting for success: ping -c1 peer3.wg-test-one >&2198+ ping -c1 peer3.wg-test-one199PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes20064 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.608 ms201202--- peer3.wg-test-one ping statistics ---2031 packets transmitted, 1 received, 0% packet loss, time 0ms204rtt min/avg/max/mdev = 0.608/0.608/0.608/0.000 ms205(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)206207--- Pinging from peer1 to controller1.wg-test-one ---208peer1: waiting for success: ping -c1 controller1.wg-test-one >&2209+ ping -c1 controller1.wg-test-one210PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes21164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.437 ms212213--- controller1.wg-test-one ping statistics ---2141 packets transmitted, 1 received, 0% packet loss, time 0ms215rtt min/avg/max/mdev = 0.437/0.437/0.437/0.000 ms216(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)217218--- Pinging from peer1 to controller2.wg-test-one ---219peer1: waiting for success: ping -c1 controller2.wg-test-one >&2220+ ping -c1 controller2.wg-test-one221PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes22264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.293 ms223224--- controller2.wg-test-one ping statistics ---2251 packets transmitted, 1 received, 0% packet loss, time 0ms226rtt min/avg/max/mdev = 0.293/0.293/0.293/0.000 ms227(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)228229--- Pinging from peer2 to peer1.wg-test-one ---230peer2: waiting for success: ping -c1 peer1.wg-test-one >&2231+ ping -c1 peer1.wg-test-one232PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes23364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.753 ms234235--- peer1.wg-test-one ping statistics ---2361 packets transmitted, 1 received, 0% packet loss, time 0ms237rtt min/avg/max/mdev = 0.753/0.753/0.753/0.000 ms238(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)239240--- Pinging from peer2 to peer3.wg-test-one ---241peer2: waiting for success: ping -c1 peer3.wg-test-one >&2242+ ping -c1 peer3.wg-test-one243PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes24464 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.586 ms245246--- peer3.wg-test-one ping statistics ---2471 packets transmitted, 1 received, 0% packet loss, time 0ms248rtt min/avg/max/mdev = 0.586/0.586/0.586/0.000 ms249(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)250251--- Pinging from peer2 to controller1.wg-test-one ---252peer2: waiting for success: ping -c1 controller1.wg-test-one >&2253+ ping -c1 controller1.wg-test-one254PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes25564 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.267 ms256257--- controller1.wg-test-one ping statistics ---2581 packets transmitted, 1 received, 0% packet loss, time 0ms259rtt min/avg/max/mdev = 0.267/0.267/0.267/0.000 ms260(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)261262--- Pinging from peer2 to controller2.wg-test-one ---263peer2: waiting for success: ping -c1 controller2.wg-test-one >&2264+ ping -c1 controller2.wg-test-one265PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes26664 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.274 ms267268--- controller2.wg-test-one ping statistics ---2691 packets transmitted, 1 received, 0% packet loss, time 0ms270rtt min/avg/max/mdev = 0.274/0.274/0.274/0.000 ms271(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)272273--- Pinging from peer3 to peer1.wg-test-one ---274peer3: waiting for success: ping -c1 peer1.wg-test-one >&2275+ ping -c1 peer1.wg-test-one276PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes27764 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.493 ms278279--- peer1.wg-test-one ping statistics ---2801 packets transmitted, 1 received, 0% packet loss, time 0ms281rtt min/avg/max/mdev = 0.493/0.493/0.493/0.000 ms282(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)283284--- Pinging from peer3 to peer2.wg-test-one ---285peer3: waiting for success: ping -c1 peer2.wg-test-one >&2286+ ping -c1 peer2.wg-test-one287PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes28864 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.585 ms289290--- peer2.wg-test-one ping statistics ---2911 packets transmitted, 1 received, 0% packet loss, time 0ms292rtt min/avg/max/mdev = 0.585/0.585/0.585/0.000 ms293(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)294295--- Pinging from peer3 to controller1.wg-test-one ---296peer3: waiting for success: ping -c1 controller1.wg-test-one >&2297+ ping -c1 controller1.wg-test-one298PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes29964 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.332 ms300301--- controller1.wg-test-one ping statistics ---3021 packets transmitted, 1 received, 0% packet loss, time 0ms303rtt min/avg/max/mdev = 0.332/0.332/0.332/0.000 ms304(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)305306--- Pinging from peer3 to controller2.wg-test-one ---307peer3: waiting for success: ping -c1 controller2.wg-test-one >&2308+ ping -c1 controller2.wg-test-one309PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes31064 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.345 ms311312--- controller2.wg-test-one ping statistics ---3131 packets transmitted, 1 received, 0% packet loss, time 0ms314rtt min/avg/max/mdev = 0.345/0.345/0.345/0.000 ms315(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)316317--- Pinging from controller1 to peer1.wg-test-one ---318controller1: waiting for success: ping -c1 peer1.wg-test-one >&2319+ ping -c1 peer1.wg-test-one320PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes32164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.245 ms322323--- peer1.wg-test-one ping statistics ---3241 packets transmitted, 1 received, 0% packet loss, time 0ms325rtt min/avg/max/mdev = 0.245/0.245/0.245/0.000 ms326(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)327328--- Pinging from controller1 to peer2.wg-test-one ---329controller1: waiting for success: ping -c1 peer2.wg-test-one >&2330+ ping -c1 peer2.wg-test-one331PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes33264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.297 ms333334--- peer2.wg-test-one ping statistics ---3351 packets transmitted, 1 received, 0% packet loss, time 0ms336rtt min/avg/max/mdev = 0.297/0.297/0.297/0.000 ms337(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)338339--- Pinging from controller1 to peer3.wg-test-one ---340controller1: waiting for success: ping -c1 peer3.wg-test-one >&2341+ ping -c1 peer3.wg-test-one342PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes34364 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.315 ms344345--- peer3.wg-test-one ping statistics ---3461 packets transmitted, 1 received, 0% packet loss, time 0ms347rtt min/avg/max/mdev = 0.315/0.315/0.315/0.000 ms348(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)349350--- Pinging from controller1 to controller2.wg-test-one ---351controller1: waiting for success: ping -c1 controller2.wg-test-one >&2352+ ping -c1 controller2.wg-test-one353PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes35464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=1.73 ms355356--- controller2.wg-test-one ping statistics ---3571 packets transmitted, 1 received, 0% packet loss, time 0ms358rtt min/avg/max/mdev = 1.728/1.728/1.728/0.000 ms359(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)360361--- Pinging from controller2 to peer1.wg-test-one ---362controller2: waiting for success: ping -c1 peer1.wg-test-one >&2363+ ping -c1 peer1.wg-test-one364PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes36564 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.390 ms366367--- peer1.wg-test-one ping statistics ---3681 packets transmitted, 1 received, 0% packet loss, time 0ms369rtt min/avg/max/mdev = 0.390/0.390/0.390/0.000 ms370(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)371372--- Pinging from controller2 to peer2.wg-test-one ---373controller2: waiting for success: ping -c1 peer2.wg-test-one >&2374+ ping -c1 peer2.wg-test-one375PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes37664 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.239 ms377378--- peer2.wg-test-one ping statistics ---3791 packets transmitted, 1 received, 0% packet loss, time 0ms380rtt min/avg/max/mdev = 0.239/0.239/0.239/0.000 ms381(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)382383--- Pinging from controller2 to peer3.wg-test-one ---384controller2: waiting for success: ping -c1 peer3.wg-test-one >&2385+ ping -c1 peer3.wg-test-one386PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes38764 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.430 ms388389--- peer3.wg-test-one ping statistics ---3901 packets transmitted, 1 received, 0% packet loss, time 0ms391rtt min/avg/max/mdev = 0.430/0.430/0.430/0.000 ms392(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)393394--- Pinging from controller2 to controller1.wg-test-one ---395controller2: waiting for success: ping -c1 controller1.wg-test-one >&2396+ ping -c1 controller1.wg-test-one397PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes39864 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.339 ms399400--- controller1.wg-test-one ping statistics ---4011 packets transmitted, 1 received, 0% packet loss, time 0ms402rtt min/avg/max/mdev = 0.339/0.339/0.339/0.000 ms403(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)404405406407408