nixbot

builds

succeeded container-test-run-wireguard default.checks.aarch64-linux.wireguard · build #337 · raw

1additionally exposed symbols:2 controller1, controller2, peer1, peer2, peer3,3 start_all, machines, driver, Machine, wait_for_signal4Starting controller15Starting controller26Starting peer17Starting peer289Starting peer31011121314151617181920<<< NixOS Stage 2 >>>2122booting system configuration /nix/store/0n6phhqwhcpp3v13nc959xhxwjmfkndi-nixos-system-controller1-test23running activation script...24setting up /etc...252: host0@if6: <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/dqxknsb71lsgzfzcdmn6x7fzssqbdyyx-coreutils-9.11/bin/sleep 999999999 && echo a6358183-193b-4ac9-b728-1c4f4d27a699'42Running as unit: run-p316-i86861980.service; invocation ID: c112ef3815dc4a4ab58610d81ae1ede443To attach to container controller1 run on the same machine that runs the test:44 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a6358183-193b-4ac9-b728-1c4f4d27a699') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 4546To inject external network and continue test, run:47sudo /nix/store/3inr3nxzqarhb9rh1z7s2s20j8c0395h-python3-3.14.7/bin/python3.14 /nix/store/yrfr6y1wjgrgr3g63rypc096h0dyh5rx-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py a6358183-193b-4ac9-b728-1c4f4d27a6994849<<< NixOS Stage 2 >>>5051booting system configuration /nix/store/fa8sba8pbk7y3pkyvm1vv930jk0m08jy-nixos-system-controller2-test52running activation script...53setting up /etc...542: host0@if4: <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/dqxknsb71lsgzfzcdmn6x7fzssqbdyyx-coreutils-9.11/bin/sleep 999999999 && echo 84f94103-30e5-47d1-b961-8ff3ae3ea173'71Running as unit: run-p316-i86861983.service; invocation ID: e2684faac61b4bb6acef0fed20c19fc672To attach to container controller2 run on the same machine that runs the test:73 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*84f94103-30e5-47d1-b961-8ff3ae3ea173') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 7475To inject external network and continue test, run:76sudo /nix/store/3inr3nxzqarhb9rh1z7s2s20j8c0395h-python3-3.14.7/bin/python3.14 /nix/store/yrfr6y1wjgrgr3g63rypc096h0dyh5rx-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 84f94103-30e5-47d1-b961-8ff3ae3ea1737778<<< NixOS Stage 2 >>>7980booting system configuration /nix/store/8yjmhvi75jjxl3ksghjvviakbsk87mll-nixos-system-peer1-test81running activation script...82setting up /etc...832: host0@if3: <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/dqxknsb71lsgzfzcdmn6x7fzssqbdyyx-coreutils-9.11/bin/sleep 999999999 && echo 525a67f5-acbf-417a-938b-f402e5be0925'100Running as unit: run-p314-i86862006.service; invocation ID: de9bb8e2cdd34fd6a59468ee49901cc6101To attach to container peer1 run on the same machine that runs the test:102 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*525a67f5-acbf-417a-938b-f402e5be0925') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 103104To inject external network and continue test, run:105sudo /nix/store/3inr3nxzqarhb9rh1z7s2s20j8c0395h-python3-3.14.7/bin/python3.14 /nix/store/yrfr6y1wjgrgr3g63rypc096h0dyh5rx-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 525a67f5-acbf-417a-938b-f402e5be0925106107<<< NixOS Stage 2 >>>108109booting system configuration /nix/store/1gmf45f06m9hk9x4dvl0r0f0jinl34fj-nixos-system-peer2-test110running activation script...111setting up /etc...1122: host0@if7: <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/dqxknsb71lsgzfzcdmn6x7fzssqbdyyx-coreutils-9.11/bin/sleep 999999999 && echo 5bc92b88-5ac9-4e4f-adb4-68ad7a5852e2'129Running as unit: run-p314-i86862010.service; invocation ID: 35d015e104e94fa38a26614ce96f8b6a130To attach to container peer2 run on the same machine that runs the test:131 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*5bc92b88-5ac9-4e4f-adb4-68ad7a5852e2') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 132133To inject external network and continue test, run:134sudo /nix/store/3inr3nxzqarhb9rh1z7s2s20j8c0395h-python3-3.14.7/bin/python3.14 /nix/store/yrfr6y1wjgrgr3g63rypc096h0dyh5rx-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 5bc92b88-5ac9-4e4f-adb4-68ad7a5852e2135136<<< NixOS Stage 2 >>>137138booting system configuration /nix/store/zi5753mbk28a6894vrgvsmbbzhmlgk2w-nixos-system-peer3-test139running activation script...140setting up /etc...1412: host0@if5: <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/dqxknsb71lsgzfzcdmn6x7fzssqbdyyx-coreutils-9.11/bin/sleep 999999999 && echo e8e2ef2f-230f-4bbf-aa99-003579c41957'158Running as unit: run-p314-i86862015.service; invocation ID: eb89412197924fa5bf83f321fd6f8403159To attach to container peer3 run on the same machine that runs the test:160 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*e8e2ef2f-230f-4bbf-aa99-003579c41957') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 161162To inject external network and continue test, run:163sudo /nix/store/3inr3nxzqarhb9rh1z7s2s20j8c0395h-python3-3.14.7/bin/python3.14 /nix/store/yrfr6y1wjgrgr3g63rypc096h0dyh5rx-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py e8e2ef2f-230f-4bbf-aa99-003579c41957164+ 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 bytes189From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable190191--- peer2.wg-test-one ping statistics ---1921 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms193194+ ping -c1 peer2.wg-test-one195PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes196From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable197198--- peer2.wg-test-one ping statistics ---1991 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms200201+ ping -c1 peer2.wg-test-one202PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes203From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable204205--- peer2.wg-test-one ping statistics ---2061 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms207208+ ping -c1 peer2.wg-test-one209PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes210From controller2.wg-test-one (fd51:19c1:c1:aa00::1) icmp_seq=1 Destination unreachable: Address unreachable211212--- peer2.wg-test-one ping statistics ---2131 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms214215+ ping -c1 peer2.wg-test-one216PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes21764 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.537 ms218219--- peer2.wg-test-one ping statistics ---2201 packets transmitted, 1 received, 0% packet loss, time 0ms221rtt min/avg/max/mdev = 0.537/0.537/0.537/0.000 ms222(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 4.06 seconds)223224--- Pinging from peer1 to peer3.wg-test-one ---225peer1: waiting for success: ping -c1 peer3.wg-test-one >&2226+ ping -c1 peer3.wg-test-one227PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes22864 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=4.81 ms229230--- peer3.wg-test-one ping statistics ---2311 packets transmitted, 1 received, 0% packet loss, time 0ms232rtt min/avg/max/mdev = 4.808/4.808/4.808/0.000 ms233(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds)234235--- Pinging from peer1 to controller1.wg-test-one ---236peer1: waiting for success: ping -c1 controller1.wg-test-one >&2237+ ping -c1 controller1.wg-test-one238PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes23964 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.204 ms240241--- controller1.wg-test-one ping statistics ---2421 packets transmitted, 1 received, 0% packet loss, time 0ms243rtt min/avg/max/mdev = 0.204/0.204/0.204/0.000 ms244(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)245246--- Pinging from peer1 to controller2.wg-test-one ---247peer1: waiting for success: ping -c1 controller2.wg-test-one >&2248+ ping -c1 controller2.wg-test-one249PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes25064 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=1.83 ms251252--- controller2.wg-test-one ping statistics ---2531 packets transmitted, 1 received, 0% packet loss, time 0ms254rtt min/avg/max/mdev = 1.825/1.825/1.825/0.000 ms255(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)256257--- Pinging from peer2 to peer1.wg-test-one ---258peer2: waiting for success: ping -c1 peer1.wg-test-one >&2259+ ping -c1 peer1.wg-test-one260PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes26164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.458 ms262263--- peer1.wg-test-one ping statistics ---2641 packets transmitted, 1 received, 0% packet loss, time 0ms265rtt min/avg/max/mdev = 0.458/0.458/0.458/0.000 ms266(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)267268--- Pinging from peer2 to peer3.wg-test-one ---269peer2: waiting for success: ping -c1 peer3.wg-test-one >&2270+ ping -c1 peer3.wg-test-one271PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes27264 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.421 ms273274--- peer3.wg-test-one ping statistics ---2751 packets transmitted, 1 received, 0% packet loss, time 0ms276rtt min/avg/max/mdev = 0.421/0.421/0.421/0.000 ms277(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)278279--- Pinging from peer2 to controller1.wg-test-one ---280peer2: waiting for success: ping -c1 controller1.wg-test-one >&2281+ ping -c1 controller1.wg-test-one282PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes28364 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.273 ms284285--- controller1.wg-test-one ping statistics ---2861 packets transmitted, 1 received, 0% packet loss, time 0ms287rtt min/avg/max/mdev = 0.273/0.273/0.273/0.000 ms288(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)289290--- Pinging from peer2 to controller2.wg-test-one ---291peer2: waiting for success: ping -c1 controller2.wg-test-one >&2292+ ping -c1 controller2.wg-test-one293PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes29464 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.248 ms295296--- controller2.wg-test-one ping statistics ---2971 packets transmitted, 1 received, 0% packet loss, time 0ms298rtt min/avg/max/mdev = 0.248/0.248/0.248/0.000 ms299(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)300301--- Pinging from peer3 to peer1.wg-test-one ---302peer3: waiting for success: ping -c1 peer1.wg-test-one >&2303+ ping -c1 peer1.wg-test-one304PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes30564 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.591 ms306307--- peer1.wg-test-one ping statistics ---3081 packets transmitted, 1 received, 0% packet loss, time 0ms309rtt min/avg/max/mdev = 0.591/0.591/0.591/0.000 ms310(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)311312--- Pinging from peer3 to peer2.wg-test-one ---313peer3: waiting for success: ping -c1 peer2.wg-test-one >&2314+ ping -c1 peer2.wg-test-one315PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes31664 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.435 ms317318--- peer2.wg-test-one ping statistics ---3191 packets transmitted, 1 received, 0% packet loss, time 0ms320rtt min/avg/max/mdev = 0.435/0.435/0.435/0.000 ms321(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)322323--- Pinging from peer3 to controller1.wg-test-one ---324peer3: waiting for success: ping -c1 controller1.wg-test-one >&2325+ ping -c1 controller1.wg-test-one326PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes32764 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.175 ms328329--- controller1.wg-test-one ping statistics ---3301 packets transmitted, 1 received, 0% packet loss, time 0ms331rtt min/avg/max/mdev = 0.175/0.175/0.175/0.000 ms332(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)333334--- Pinging from peer3 to controller2.wg-test-one ---335peer3: waiting for success: ping -c1 controller2.wg-test-one >&2336+ ping -c1 controller2.wg-test-one337PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes33864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.230 ms339340--- controller2.wg-test-one ping statistics ---3411 packets transmitted, 1 received, 0% packet loss, time 0ms342rtt min/avg/max/mdev = 0.230/0.230/0.230/0.000 ms343(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)344345--- Pinging from controller1 to peer1.wg-test-one ---346controller1: waiting for success: ping -c1 peer1.wg-test-one >&2347+ ping -c1 peer1.wg-test-one348PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes34964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.233 ms350351--- peer1.wg-test-one ping statistics ---3521 packets transmitted, 1 received, 0% packet loss, time 0ms353rtt min/avg/max/mdev = 0.233/0.233/0.233/0.000 ms354(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)355356--- Pinging from controller1 to peer2.wg-test-one ---357controller1: waiting for success: ping -c1 peer2.wg-test-one >&2358+ ping -c1 peer2.wg-test-one359PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes36064 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.248 ms361362--- peer2.wg-test-one ping statistics ---3631 packets transmitted, 1 received, 0% packet loss, time 0ms364rtt min/avg/max/mdev = 0.248/0.248/0.248/0.000 ms365(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)366367--- Pinging from controller1 to peer3.wg-test-one ---368controller1: waiting for success: ping -c1 peer3.wg-test-one >&2369+ ping -c1 peer3.wg-test-one370PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes37164 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.221 ms372373--- peer3.wg-test-one ping statistics ---3741 packets transmitted, 1 received, 0% packet loss, time 0ms375rtt min/avg/max/mdev = 0.221/0.221/0.221/0.000 ms376(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)377378--- Pinging from controller1 to controller2.wg-test-one ---379controller1: waiting for success: ping -c1 controller2.wg-test-one >&2380+ ping -c1 controller2.wg-test-one381PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes38264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=4721 ms383384--- controller2.wg-test-one ping statistics ---3851 packets transmitted, 1 received, 0% packet loss, time 0ms386rtt min/avg/max/mdev = 4720.697/4720.697/4720.697/0.000 ms387(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 4.73 seconds)388389--- Pinging from controller2 to peer1.wg-test-one ---390controller2: waiting for success: ping -c1 peer1.wg-test-one >&2391+ ping -c1 peer1.wg-test-one392PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes39364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.302 ms394395--- peer1.wg-test-one ping statistics ---3961 packets transmitted, 1 received, 0% packet loss, time 0ms397rtt min/avg/max/mdev = 0.302/0.302/0.302/0.000 ms398(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)399400--- Pinging from controller2 to peer2.wg-test-one ---401controller2: waiting for success: ping -c1 peer2.wg-test-one >&2402+ ping -c1 peer2.wg-test-one403PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes40464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.249 ms405406--- peer2.wg-test-one ping statistics ---4071 packets transmitted, 1 received, 0% packet loss, time 0ms408rtt min/avg/max/mdev = 0.249/0.249/0.249/0.000 ms409(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)410411--- Pinging from controller2 to peer3.wg-test-one ---412controller2: waiting for success: ping -c1 peer3.wg-test-one >&2413+ ping -c1 peer3.wg-test-one414PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes41564 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=1.13 ms416417--- peer3.wg-test-one ping statistics ---4181 packets transmitted, 1 received, 0% packet loss, time 0ms419rtt min/avg/max/mdev = 1.128/1.128/1.128/0.000 ms420(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)421422--- Pinging from controller2 to controller1.wg-test-one ---423controller2: waiting for success: ping -c1 controller1.wg-test-one >&2424+ ping -c1 controller1.wg-test-one425PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes42664 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.202 ms427428--- controller1.wg-test-one ping statistics ---4291 packets transmitted, 1 received, 0% packet loss, time 0ms430rtt min/avg/max/mdev = 0.202/0.202/0.202/0.000 ms431(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)432433434435436