container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #595
· 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/7qxnyz6a6qa2jhgmzlfjwdy9cwdb2g7b-nixos-system-controller1-test18running activation script...19setting up /etc...202: host0@if6: <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/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 9de7622b-7540-41f0-961b-07b921f907f0'37Running as unit: run-p315-i2102860.service; invocation ID: ab5b99f7a46b47f3b1414a8ffeeabb0f38To attach to container controller1 run on the same machine that runs the test:39 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*9de7622b-7540-41f0-961b-07b921f907f0') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4041To inject external network and continue test, run:42sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 9de7622b-7540-41f0-961b-07b921f907f04344<<< NixOS Stage 2 >>>4546booting system configuration /nix/store/c1jx5qdfqgmhk81mgbwvxgqg78h340m3-nixos-system-controller2-test47running activation script...48setting up /etc...492: host0@if5: <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/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 690dff15-ba1d-41e2-a6e7-eab2e9c7240e'66Running as unit: run-p315-i2102872.service; invocation ID: 770c095e9a7948baa0d54b58e39a85e567To attach to container controller2 run on the same machine that runs the test:68 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*690dff15-ba1d-41e2-a6e7-eab2e9c7240e') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 6970To inject external network and continue test, run:71sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 690dff15-ba1d-41e2-a6e7-eab2e9c7240e7273<<< NixOS Stage 2 >>>7475booting system configuration /nix/store/1xcbm3j3hd9phg50xjm8bmzizl51avss-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/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo a3b6e55e-11f8-4393-aecf-7b80bf76f73e'95Running as unit: run-p314-i2102875.service; invocation ID: ce14c3f29123435f9d5013f1c3a6a33096To attach to container peer1 run on the same machine that runs the test:97 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a3b6e55e-11f8-4393-aecf-7b80bf76f73e') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 9899To inject external network and continue test, run:100sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py a3b6e55e-11f8-4393-aecf-7b80bf76f73e101102<<< NixOS Stage 2 >>>103104booting system configuration /nix/store/4v7mq5gx5ixajf8lv8cjz09x3684s2yq-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/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo adcdd3d6-9f7b-424e-8201-7fc45a673b9b'124Running as unit: run-p313-i2102937.service; invocation ID: f91f75d4ef5b4750aa2d4e8a3db626f1125To attach to container peer2 run on the same machine that runs the test:126 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*adcdd3d6-9f7b-424e-8201-7fc45a673b9b') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 127128To inject external network and continue test, run:129sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py adcdd3d6-9f7b-424e-8201-7fc45a673b9b130131<<< NixOS Stage 2 >>>132133booting system configuration /nix/store/w1v2bp46v678ja5yl7rqh05cs860ahvl-nixos-system-peer3-test134running activation script...135setting up /etc...1362: host0@if7: <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/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo bba07481-b30a-4e31-b492-058564c77e3c'153Running as unit: run-p313-i2102947.service; invocation ID: dccf532cff734c42a38d73e3878f301e154To attach to container peer3 run on the same machine that runs the test:155 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*bba07481-b30a-4e31-b492-058564c77e3c') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 156157To inject external network and continue test, run:158sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py bba07481-b30a-4e31-b492-058564c77e3c159+ 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 bytes19164 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.720 ms192193--- peer2.wg-test-one ping statistics ---1941 packets transmitted, 1 received, 0% packet loss, time 0ms195rtt min/avg/max/mdev = 0.720/0.720/0.720/0.000 ms196(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 4.47 seconds)197198--- Pinging from peer1 to peer3.wg-test-one ---199peer1: waiting for success: ping -c1 peer3.wg-test-one >&2200+ ping -c1 peer3.wg-test-one201PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes20264 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.463 ms203204--- peer3.wg-test-one ping statistics ---2051 packets transmitted, 1 received, 0% packet loss, time 0ms206rtt min/avg/max/mdev = 0.463/0.463/0.463/0.000 ms207(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)208209--- Pinging from peer1 to controller1.wg-test-one ---210peer1: waiting for success: ping -c1 controller1.wg-test-one >&2211+ ping -c1 controller1.wg-test-one212PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes21364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.215 ms214215--- controller1.wg-test-one ping statistics ---2161 packets transmitted, 1 received, 0% packet loss, time 0ms217rtt min/avg/max/mdev = 0.215/0.215/0.215/0.000 ms218(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)219220--- Pinging from peer1 to controller2.wg-test-one ---221peer1: waiting for success: ping -c1 controller2.wg-test-one >&2222+ ping -c1 controller2.wg-test-one223PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes22464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.225 ms225226--- controller2.wg-test-one ping statistics ---2271 packets transmitted, 1 received, 0% packet loss, time 0ms228rtt min/avg/max/mdev = 0.225/0.225/0.225/0.000 ms229(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)230231--- Pinging from peer2 to peer1.wg-test-one ---232peer2: waiting for success: ping -c1 peer1.wg-test-one >&2233+ ping -c1 peer1.wg-test-one234PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes23564 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.477 ms236237--- peer1.wg-test-one ping statistics ---2381 packets transmitted, 1 received, 0% packet loss, time 0ms239rtt min/avg/max/mdev = 0.477/0.477/0.477/0.000 ms240(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)241242--- Pinging from peer2 to peer3.wg-test-one ---243peer2: waiting for success: ping -c1 peer3.wg-test-one >&2244+ ping -c1 peer3.wg-test-one245PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes24664 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=5.32 ms247248--- peer3.wg-test-one ping statistics ---2491 packets transmitted, 1 received, 0% packet loss, time 0ms250rtt min/avg/max/mdev = 5.315/5.315/5.315/0.000 ms251(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds)252253--- Pinging from peer2 to controller1.wg-test-one ---254peer2: waiting for success: ping -c1 controller1.wg-test-one >&2255+ ping -c1 controller1.wg-test-one256PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes25764 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.397 ms258259--- controller1.wg-test-one ping statistics ---2601 packets transmitted, 1 received, 0% packet loss, time 0ms261rtt min/avg/max/mdev = 0.397/0.397/0.397/0.000 ms262(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.02 seconds)263264--- Pinging from peer2 to controller2.wg-test-one ---265peer2: waiting for success: ping -c1 controller2.wg-test-one >&2266+ ping -c1 controller2.wg-test-one267PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes26864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.275 ms269270--- controller2.wg-test-one ping statistics ---2711 packets transmitted, 1 received, 0% packet loss, time 0ms272rtt min/avg/max/mdev = 0.275/0.275/0.275/0.000 ms273(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)274275--- Pinging from peer3 to peer1.wg-test-one ---276peer3: waiting for success: ping -c1 peer1.wg-test-one >&2277+ ping -c1 peer1.wg-test-one278PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes27964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.396 ms280281--- peer1.wg-test-one ping statistics ---2821 packets transmitted, 1 received, 0% packet loss, time 0ms283rtt min/avg/max/mdev = 0.396/0.396/0.396/0.000 ms284(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)285286--- Pinging from peer3 to peer2.wg-test-one ---287peer3: waiting for success: ping -c1 peer2.wg-test-one >&2288+ ping -c1 peer2.wg-test-one289PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes29064 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.533 ms291292--- peer2.wg-test-one ping statistics ---2931 packets transmitted, 1 received, 0% packet loss, time 0ms294rtt min/avg/max/mdev = 0.533/0.533/0.533/0.000 ms295(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)296297--- Pinging from peer3 to controller1.wg-test-one ---298peer3: waiting for success: ping -c1 controller1.wg-test-one >&2299+ ping -c1 controller1.wg-test-one300PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes30164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.145 ms302303--- controller1.wg-test-one ping statistics ---3041 packets transmitted, 1 received, 0% packet loss, time 0ms305rtt min/avg/max/mdev = 0.145/0.145/0.145/0.000 ms306(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)307308--- Pinging from peer3 to controller2.wg-test-one ---309peer3: waiting for success: ping -c1 controller2.wg-test-one >&2310+ ping -c1 controller2.wg-test-one311PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes31264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.188 ms313314--- controller2.wg-test-one ping statistics ---3151 packets transmitted, 1 received, 0% packet loss, time 0ms316rtt min/avg/max/mdev = 0.188/0.188/0.188/0.000 ms317(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)318319--- Pinging from controller1 to peer1.wg-test-one ---320controller1: waiting for success: ping -c1 peer1.wg-test-one >&2321+ ping -c1 peer1.wg-test-one322PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes32364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.220 ms324325--- peer1.wg-test-one ping statistics ---3261 packets transmitted, 1 received, 0% packet loss, time 0ms327rtt min/avg/max/mdev = 0.220/0.220/0.220/0.000 ms328(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)329330--- Pinging from controller1 to peer2.wg-test-one ---331controller1: waiting for success: ping -c1 peer2.wg-test-one >&2332+ ping -c1 peer2.wg-test-one333PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes33464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.201 ms335336--- peer2.wg-test-one ping statistics ---3371 packets transmitted, 1 received, 0% packet loss, time 0ms338rtt min/avg/max/mdev = 0.201/0.201/0.201/0.000 ms339(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)340341--- Pinging from controller1 to peer3.wg-test-one ---342controller1: waiting for success: ping -c1 peer3.wg-test-one >&2343+ ping -c1 peer3.wg-test-one344PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes34564 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.179 ms346347--- peer3.wg-test-one ping statistics ---3481 packets transmitted, 1 received, 0% packet loss, time 0ms349rtt min/avg/max/mdev = 0.179/0.179/0.179/0.000 ms350(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)351352--- Pinging from controller1 to controller2.wg-test-one ---353controller1: waiting for success: ping -c1 controller2.wg-test-one >&2354+ ping -c1 controller2.wg-test-one355PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes35664 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.363 ms357358--- controller2.wg-test-one ping statistics ---3591 packets transmitted, 1 received, 0% packet loss, time 0ms360rtt min/avg/max/mdev = 0.363/0.363/0.363/0.000 ms361(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)362363--- Pinging from controller2 to peer1.wg-test-one ---364controller2: waiting for success: ping -c1 peer1.wg-test-one >&2365+ ping -c1 peer1.wg-test-one366PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes36764 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.261 ms368369--- peer1.wg-test-one ping statistics ---3701 packets transmitted, 1 received, 0% packet loss, time 0ms371rtt min/avg/max/mdev = 0.261/0.261/0.261/0.000 ms372(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)373374--- Pinging from controller2 to peer2.wg-test-one ---375controller2: waiting for success: ping -c1 peer2.wg-test-one >&2376+ ping -c1 peer2.wg-test-one377PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes37864 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.314 ms379380--- peer2.wg-test-one ping statistics ---3811 packets transmitted, 1 received, 0% packet loss, time 0ms382rtt min/avg/max/mdev = 0.314/0.314/0.314/0.000 ms383(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)384385--- Pinging from controller2 to peer3.wg-test-one ---386controller2: waiting for success: ping -c1 peer3.wg-test-one >&2387+ ping -c1 peer3.wg-test-one388PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes38964 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.267 ms390391--- peer3.wg-test-one ping statistics ---3921 packets transmitted, 1 received, 0% packet loss, time 0ms393rtt min/avg/max/mdev = 0.267/0.267/0.267/0.000 ms394(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)395396--- Pinging from controller2 to controller1.wg-test-one ---397controller2: waiting for success: ping -c1 controller1.wg-test-one >&2398+ ping -c1 controller1.wg-test-one399PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes40064 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.223 ms401402--- controller1.wg-test-one ping statistics ---4031 packets transmitted, 1 received, 0% packet loss, time 0ms404rtt min/avg/max/mdev = 0.223/0.223/0.223/0.000 ms405(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)406407408409410