container-test-run-wireguard
default.checks.aarch64-linux.wireguard
· build #391
· raw
1additionally exposed symbols:2 controller1, controller2, peer1, peer2, peer3,3 start_all, machines, driver, Machine, wait_for_signal4Starting controller15Starting controller26Starting peer17Starting peer28Starting peer39101112131415<<< NixOS Stage 2 >>>1617booting system configuration /nix/store/00l238lgfwdd6521i6ma2wz7r9zmrqhg-nixos-system-controller1-test18running activation script...19setting up /etc...202: host0@if7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100021 link/ether ba:9c:76:d8:39:5a brd ff:ff:ff:ff:ff:ff link-netnsid 022setting up age secrets...23starting systemd...24systemd 260.2 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)25Detected virtualization systemd-nspawn.26Detected architecture arm64.27Detected first boot.28Initializing machine ID from container UUID.29Applying preset policy.30Populated /etc with preset unit settings.31Queued start job for default target Multi-User System.32333435<<< Welcome to NixOS test (aarch64) - console >>>36+ systemd-run /bin/sh -c '/nix/store/vpnizxs18sv6agrsqplsvaml9y3bfx0k-coreutils-9.11/bin/sleep 999999999 && echo 524837e1-5653-48bd-bb68-19979146f211'37Running as unit: run-p315-i93753526.service; invocation ID: 7e28feae68d744dba4bb80e576ecc24b38To attach to container controller1 run on the same machine that runs the test:39 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*524837e1-5653-48bd-bb68-19979146f211') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4041To inject external network and continue test, run:42sudo /nix/store/1bhl5b9821ifsz1dbfm4wxbjbfywmsaq-python3-3.13.14/bin/python3.13 /nix/store/lf6lngb6dzima2m8nqbna4lc6bm1qw85-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 524837e1-5653-48bd-bb68-19979146f2114344<<< NixOS Stage 2 >>>4546booting system configuration /nix/store/6kb2q0b22b4iypsvpx62160vip59fnjf-nixos-system-controller2-test47running activation script...48setting up /etc...492: host0@if6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100050 link/ether e2:8c:47:a0:40:ce brd ff:ff:ff:ff:ff:ff link-netnsid 051setting up age secrets...52starting systemd...53systemd 260.2 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)54Detected virtualization systemd-nspawn.55Detected architecture arm64.56Detected first boot.57Initializing machine ID from container UUID.58Applying preset policy.59Populated /etc with preset unit settings.60Queued start job for default target Multi-User System.61626364<<< Welcome to NixOS test (aarch64) - console >>>65+ systemd-run /bin/sh -c '/nix/store/vpnizxs18sv6agrsqplsvaml9y3bfx0k-coreutils-9.11/bin/sleep 999999999 && echo bdc77fa4-11d0-4fea-a831-0915a4b6fdfb'66Running as unit: run-p315-i93753547.service; invocation ID: 7abe6ff313254cab84997ac83836170967To attach to container controller2 run on the same machine that runs the test:68 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*bdc77fa4-11d0-4fea-a831-0915a4b6fdfb') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 6970To inject external network and continue test, run:71sudo /nix/store/1bhl5b9821ifsz1dbfm4wxbjbfywmsaq-python3-3.13.14/bin/python3.13 /nix/store/lf6lngb6dzima2m8nqbna4lc6bm1qw85-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py bdc77fa4-11d0-4fea-a831-0915a4b6fdfb7273<<< NixOS Stage 2 >>>7475booting system configuration /nix/store/z95300g1m3zhqf8vjh5d980zk7p92py7-nixos-system-peer1-test76running activation script...77setting up /etc...782: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100079 link/ether 5a:72:92:04:a1:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 080setting up age secrets...81starting systemd...82systemd 260.2 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)83Detected virtualization systemd-nspawn.84Detected architecture arm64.85Detected first boot.86Initializing machine ID from container UUID.87Applying preset policy.88Populated /etc with preset unit settings.89Queued start job for default target Multi-User System.90919293<<< Welcome to NixOS test (aarch64) - console >>>94+ systemd-run /bin/sh -c '/nix/store/vpnizxs18sv6agrsqplsvaml9y3bfx0k-coreutils-9.11/bin/sleep 999999999 && echo abb48b61-91f3-4080-85b9-f55b177fd2ab'95Running as unit: run-p313-i93753593.service; invocation ID: c32520d821794705825af36b2a1ddf9696To attach to container peer1 run on the same machine that runs the test:97 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*abb48b61-91f3-4080-85b9-f55b177fd2ab') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 9899To inject external network and continue test, run:100sudo /nix/store/1bhl5b9821ifsz1dbfm4wxbjbfywmsaq-python3-3.13.14/bin/python3.13 /nix/store/lf6lngb6dzima2m8nqbna4lc6bm1qw85-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py abb48b61-91f3-4080-85b9-f55b177fd2ab101102<<< NixOS Stage 2 >>>103104booting system configuration /nix/store/4c2mndh97dbr2gxdv4f1dib5iv3kcx67-nixos-system-peer2-test105running activation script...106setting up /etc...1072: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000108 link/ether 12:c0:58:37:f8:51 brd ff:ff:ff:ff:ff:ff link-netnsid 0109setting up age secrets...110starting systemd...111systemd 260.2 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)112Detected virtualization systemd-nspawn.113Detected architecture arm64.114Detected first boot.115Initializing machine ID from container UUID.116Applying preset policy.117Populated /etc with preset unit settings.118Queued start job for default target Multi-User System.119120121122<<< Welcome to NixOS test (aarch64) - console >>>123+ systemd-run /bin/sh -c '/nix/store/vpnizxs18sv6agrsqplsvaml9y3bfx0k-coreutils-9.11/bin/sleep 999999999 && echo 56844b41-c5f2-46b5-90ac-7695a8faf180'124Running as unit: run-p313-i93753621.service; invocation ID: 9ac0fd6fe3d147fd93017576c038104b125To attach to container peer2 run on the same machine that runs the test:126 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*56844b41-c5f2-46b5-90ac-7695a8faf180') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 127128To inject external network and continue test, run:129sudo /nix/store/1bhl5b9821ifsz1dbfm4wxbjbfywmsaq-python3-3.13.14/bin/python3.13 /nix/store/lf6lngb6dzima2m8nqbna4lc6bm1qw85-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 56844b41-c5f2-46b5-90ac-7695a8faf180130131<<< NixOS Stage 2 >>>132133booting system configuration /nix/store/8dq1smsxfcpqk3qfjcf8jynzlr6k5bvy-nixos-system-peer3-test134running activation script...135setting up /etc...1362: host0@if5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000137 link/ether a6:44:e4:32:05:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0138setting up age secrets...139starting systemd...140systemd 260.2 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)141Detected virtualization systemd-nspawn.142Detected architecture arm64.143Detected first boot.144Initializing machine ID from container UUID.145Applying preset policy.146Populated /etc with preset unit settings.147Queued start job for default target Multi-User System.148149150151<<< Welcome to NixOS test (aarch64) - console >>>152+ systemd-run /bin/sh -c '/nix/store/vpnizxs18sv6agrsqplsvaml9y3bfx0k-coreutils-9.11/bin/sleep 999999999 && echo 60a2fac9-62eb-4ef1-bfc6-257b03e592c9'153Running as unit: run-p313-i93753649.service; invocation ID: ecfef3cf24d84c93810aecdc73a51a45154To attach to container peer3 run on the same machine that runs the test:155 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*60a2fac9-62eb-4ef1-bfc6-257b03e592c9') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 156157To inject external network and continue test, run:158sudo /nix/store/1bhl5b9821ifsz1dbfm4wxbjbfywmsaq-python3-3.13.14/bin/python3.13 /nix/store/lf6lngb6dzima2m8nqbna4lc6bm1qw85-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 60a2fac9-62eb-4ef1-bfc6-257b03e592c9159+ systemctl start network-online.target160+ systemctl start network-online.target161+ systemctl start network-online.target162+ systemctl start network-online.target163+ systemctl start network-online.target164+ systemctl --no-pager show network-online.target165+ systemctl --no-pager show systemd-networkd.service166+ systemctl --no-pager show network-online.target167+ systemctl --no-pager show systemd-networkd.service168+ systemctl --no-pager show network-online.target169+ systemctl --no-pager show systemd-networkd.service170+ systemctl --no-pager show network-online.target171+ systemctl --no-pager show systemd-networkd.service172+ systemctl --no-pager show network-online.target173+ systemctl --no-pager show systemd-networkd.service174175176============================================================177STARTING PING TESTS178============================================================179180--- Pinging from peer1 to peer2.wg-test-one ---181peer1: waiting for success: ping -c1 peer2.wg-test-one >&2182+ ping -c1 peer2.wg-test-one183PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes184From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable185186--- peer2.wg-test-one ping statistics ---1871 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms188189+ ping -c1 peer2.wg-test-one190PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes191From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable192193--- peer2.wg-test-one ping statistics ---1941 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms195196+ ping -c1 peer2.wg-test-one197PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes198From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable199200--- peer2.wg-test-one ping statistics ---2011 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms202203+ ping -c1 peer2.wg-test-one204PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes20564 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.630 ms206207--- peer2.wg-test-one ping statistics ---2081 packets transmitted, 1 received, 0% packet loss, time 0ms209rtt min/avg/max/mdev = 0.630/0.630/0.630/0.000 ms210(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.05 seconds)211212--- Pinging from peer1 to peer3.wg-test-one ---213peer1: waiting for success: ping -c1 peer3.wg-test-one >&2214+ ping -c1 peer3.wg-test-one215PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes21664 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.576 ms217218--- peer3.wg-test-one ping statistics ---2191 packets transmitted, 1 received, 0% packet loss, time 0ms220rtt min/avg/max/mdev = 0.576/0.576/0.576/0.000 ms221(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)222223--- Pinging from peer1 to controller1.wg-test-one ---224peer1: waiting for success: ping -c1 controller1.wg-test-one >&2225+ ping -c1 controller1.wg-test-one226PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes22764 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.377 ms228229--- controller1.wg-test-one ping statistics ---2301 packets transmitted, 1 received, 0% packet loss, time 0ms231rtt min/avg/max/mdev = 0.377/0.377/0.377/0.000 ms232(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)233234--- Pinging from peer1 to controller2.wg-test-one ---235peer1: waiting for success: ping -c1 controller2.wg-test-one >&2236+ ping -c1 controller2.wg-test-one237PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes23864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.260 ms239240--- controller2.wg-test-one ping statistics ---2411 packets transmitted, 1 received, 0% packet loss, time 0ms242rtt min/avg/max/mdev = 0.260/0.260/0.260/0.000 ms243(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)244245--- Pinging from peer2 to peer1.wg-test-one ---246peer2: waiting for success: ping -c1 peer1.wg-test-one >&2247+ ping -c1 peer1.wg-test-one248PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes24964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.457 ms250251--- peer1.wg-test-one ping statistics ---2521 packets transmitted, 1 received, 0% packet loss, time 0ms253rtt min/avg/max/mdev = 0.457/0.457/0.457/0.000 ms254(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)255256--- Pinging from peer2 to peer3.wg-test-one ---257peer2: waiting for success: ping -c1 peer3.wg-test-one >&2258+ ping -c1 peer3.wg-test-one259PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes26064 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.419 ms261262--- peer3.wg-test-one ping statistics ---2631 packets transmitted, 1 received, 0% packet loss, time 0ms264rtt min/avg/max/mdev = 0.419/0.419/0.419/0.000 ms265(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)266267--- Pinging from peer2 to controller1.wg-test-one ---268peer2: waiting for success: ping -c1 controller1.wg-test-one >&2269+ ping -c1 controller1.wg-test-one270PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes27164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.182 ms272273--- controller1.wg-test-one ping statistics ---2741 packets transmitted, 1 received, 0% packet loss, time 0ms275rtt min/avg/max/mdev = 0.182/0.182/0.182/0.000 ms276(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)277278--- Pinging from peer2 to controller2.wg-test-one ---279peer2: waiting for success: ping -c1 controller2.wg-test-one >&2280+ ping -c1 controller2.wg-test-one281PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes28264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.294 ms283284--- controller2.wg-test-one ping statistics ---2851 packets transmitted, 1 received, 0% packet loss, time 0ms286rtt min/avg/max/mdev = 0.294/0.294/0.294/0.000 ms287(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)288289--- Pinging from peer3 to peer1.wg-test-one ---290peer3: waiting for success: ping -c1 peer1.wg-test-one >&2291+ ping -c1 peer1.wg-test-one292PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes29364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.796 ms294295--- peer1.wg-test-one ping statistics ---2961 packets transmitted, 1 received, 0% packet loss, time 0ms297rtt min/avg/max/mdev = 0.796/0.796/0.796/0.000 ms298(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)299300--- Pinging from peer3 to peer2.wg-test-one ---301peer3: waiting for success: ping -c1 peer2.wg-test-one >&2302+ ping -c1 peer2.wg-test-one303PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes30464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.522 ms305306--- peer2.wg-test-one ping statistics ---3071 packets transmitted, 1 received, 0% packet loss, time 0ms308rtt min/avg/max/mdev = 0.522/0.522/0.522/0.000 ms309(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)310311--- Pinging from peer3 to controller1.wg-test-one ---312peer3: waiting for success: ping -c1 controller1.wg-test-one >&2313+ ping -c1 controller1.wg-test-one314PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes31564 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.226 ms316317--- controller1.wg-test-one ping statistics ---3181 packets transmitted, 1 received, 0% packet loss, time 0ms319rtt min/avg/max/mdev = 0.226/0.226/0.226/0.000 ms320(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)321322--- Pinging from peer3 to controller2.wg-test-one ---323peer3: waiting for success: ping -c1 controller2.wg-test-one >&2324+ ping -c1 controller2.wg-test-one325PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes32664 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.254 ms327328--- controller2.wg-test-one ping statistics ---3291 packets transmitted, 1 received, 0% packet loss, time 0ms330rtt min/avg/max/mdev = 0.254/0.254/0.254/0.000 ms331(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)332333--- Pinging from controller1 to peer1.wg-test-one ---334controller1: waiting for success: ping -c1 peer1.wg-test-one >&2335+ ping -c1 peer1.wg-test-one336PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes33764 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.223 ms338339--- peer1.wg-test-one ping statistics ---3401 packets transmitted, 1 received, 0% packet loss, time 0ms341rtt min/avg/max/mdev = 0.223/0.223/0.223/0.000 ms342(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)343344--- Pinging from controller1 to peer2.wg-test-one ---345controller1: waiting for success: ping -c1 peer2.wg-test-one >&2346+ ping -c1 peer2.wg-test-one347PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes34864 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=2.49 ms349350--- peer2.wg-test-one ping statistics ---3511 packets transmitted, 1 received, 0% packet loss, time 0ms352rtt min/avg/max/mdev = 2.491/2.491/2.491/0.000 ms353(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)354355--- Pinging from controller1 to peer3.wg-test-one ---356controller1: waiting for success: ping -c1 peer3.wg-test-one >&2357+ ping -c1 peer3.wg-test-one358PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes35964 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.235 ms360361--- peer3.wg-test-one ping statistics ---3621 packets transmitted, 1 received, 0% packet loss, time 0ms363rtt min/avg/max/mdev = 0.235/0.235/0.235/0.000 ms364(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)365366--- Pinging from controller1 to controller2.wg-test-one ---367controller1: waiting for success: ping -c1 controller2.wg-test-one >&2368+ ping -c1 controller2.wg-test-one369PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes37064 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.295 ms371372--- controller2.wg-test-one ping statistics ---3731 packets transmitted, 1 received, 0% packet loss, time 0ms374rtt min/avg/max/mdev = 0.295/0.295/0.295/0.000 ms375(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)376377--- Pinging from controller2 to peer1.wg-test-one ---378controller2: waiting for success: ping -c1 peer1.wg-test-one >&2379+ ping -c1 peer1.wg-test-one380PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes38164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.256 ms382383--- peer1.wg-test-one ping statistics ---3841 packets transmitted, 1 received, 0% packet loss, time 0ms385rtt min/avg/max/mdev = 0.256/0.256/0.256/0.000 ms386(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)387388--- Pinging from controller2 to peer2.wg-test-one ---389controller2: waiting for success: ping -c1 peer2.wg-test-one >&2390+ ping -c1 peer2.wg-test-one391PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes39264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.241 ms393394--- peer2.wg-test-one ping statistics ---3951 packets transmitted, 1 received, 0% packet loss, time 0ms396rtt min/avg/max/mdev = 0.241/0.241/0.241/0.000 ms397(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)398399--- Pinging from controller2 to peer3.wg-test-one ---400controller2: waiting for success: ping -c1 peer3.wg-test-one >&2401+ ping -c1 peer3.wg-test-one402PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes40364 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.232 ms404405--- peer3.wg-test-one ping statistics ---4061 packets transmitted, 1 received, 0% packet loss, time 0ms407rtt min/avg/max/mdev = 0.232/0.232/0.232/0.000 ms408(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)409410--- Pinging from controller2 to controller1.wg-test-one ---411controller2: waiting for success: ping -c1 controller1.wg-test-one >&2412+ ping -c1 controller1.wg-test-one413PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes41464 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.217 ms415416--- controller1.wg-test-one ping statistics ---4171 packets transmitted, 1 received, 0% packet loss, time 0ms418rtt min/avg/max/mdev = 0.217/0.217/0.217/0.000 ms419(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)420421422423424