container-test-run-wireguard
checks.aarch64-linux.wireguard
· build #855
· raw
1build01: building phblmb7r295wcz4497nzv513x49jz1fb-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/94gsnvn2k80bzla0gsxyj9ifg9mwc2ng-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 b49a2e3a-d702-4812-9453-2a9dd9caf49e'38Running as unit: run-p315-i32372804.service; invocation ID: 66b3eee5cdda4750b3e20de7994c52b739To attach to container controller1 run on the same machine that runs the test:40 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*b49a2e3a-d702-4812-9453-2a9dd9caf49e') --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 b49a2e3a-d702-4812-9453-2a9dd9caf49e4445<<< NixOS Stage 2 >>>4647booting system configuration /nix/store/2f4cy7xgwjaqhadbmh3wad7kvqr3grqh-nixos-system-controller2-test48running activation script...49setting up /etc...502: host0@if3: <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 ec0c0a44-c5b9-4602-970b-7e86bf24f641'67Running as unit: run-p315-i32372807.service; invocation ID: 97e7141d455e4a0798fdb012781ad47868To attach to container controller2 run on the same machine that runs the test:69 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*ec0c0a44-c5b9-4602-970b-7e86bf24f641') --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 ec0c0a44-c5b9-4602-970b-7e86bf24f6417374<<< NixOS Stage 2 >>>7576booting system configuration /nix/store/rbqi58cpsp0qxd8dxgq41z7kg0g8xmrh-nixos-system-peer1-test77running activation script...78setting up /etc...792: host0@if7: <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 0bbc992c-64db-4174-bec1-8406b3ad45dc'96Running as unit: run-p313-i32372894.service; invocation ID: 5bc59d94f7434ebab9349ba5da2b1f7c97To attach to container peer1 run on the same machine that runs the test:98 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*0bbc992c-64db-4174-bec1-8406b3ad45dc') --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 0bbc992c-64db-4174-bec1-8406b3ad45dc102103<<< NixOS Stage 2 >>>104105booting system configuration /nix/store/6gwf5fvx21z9rv2w42q5j5qnsg7jid3l-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 c3194c71-4fc6-485f-ab7d-415ddc50ec64'125Running as unit: run-p313-i32372912.service; invocation ID: 46209085b0874d179f0261f9695bfc0a126To attach to container peer2 run on the same machine that runs the test:127 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*c3194c71-4fc6-485f-ab7d-415ddc50ec64') --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 c3194c71-4fc6-485f-ab7d-415ddc50ec64131132<<< NixOS Stage 2 >>>133134booting system configuration /nix/store/f9ahr4kxc6iadc27c92yn5m8zhin4r2c-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 4c9c0aad-66cf-4f79-9b45-55d47e489236'154Running as unit: run-p313-i32372916.service; invocation ID: 4c5fe37098f04e27879a87aaf7c335f7155To attach to container peer3 run on the same machine that runs the test:156 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*4c9c0aad-66cf-4f79-9b45-55d47e489236') --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 4c9c0aad-66cf-4f79-9b45-55d47e489236160+ 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 bytes18564 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=3807 ms186187--- peer2.wg-test-one ping statistics ---1881 packets transmitted, 1 received, 0% packet loss, time 0ms189rtt min/avg/max/mdev = 3807.057/3807.057/3807.057/0.000 ms190(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 3.82 seconds)191192--- Pinging from peer1 to peer3.wg-test-one ---193peer1: waiting for success: ping -c1 peer3.wg-test-one >&2194+ ping -c1 peer3.wg-test-one195PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes19664 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=0.642 ms197198--- peer3.wg-test-one ping statistics ---1991 packets transmitted, 1 received, 0% packet loss, time 0ms200rtt min/avg/max/mdev = 0.642/0.642/0.642/0.000 ms201(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds)202203--- Pinging from peer1 to controller1.wg-test-one ---204peer1: waiting for success: ping -c1 controller1.wg-test-one >&2205+ ping -c1 controller1.wg-test-one206PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes20764 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.238 ms208209--- controller1.wg-test-one ping statistics ---2101 packets transmitted, 1 received, 0% packet loss, time 0ms211rtt min/avg/max/mdev = 0.238/0.238/0.238/0.000 ms212(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.02 seconds)213214--- Pinging from peer1 to controller2.wg-test-one ---215peer1: waiting for success: ping -c1 controller2.wg-test-one >&2216+ ping -c1 controller2.wg-test-one217PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes21864 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.421 ms219220--- controller2.wg-test-one ping statistics ---2211 packets transmitted, 1 received, 0% packet loss, time 0ms222rtt min/avg/max/mdev = 0.421/0.421/0.421/0.000 ms223(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)224225--- Pinging from peer2 to peer1.wg-test-one ---226peer2: waiting for success: ping -c1 peer1.wg-test-one >&2227+ ping -c1 peer1.wg-test-one228PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes22964 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.572 ms230231--- peer1.wg-test-one ping statistics ---2321 packets transmitted, 1 received, 0% packet loss, time 0ms233rtt min/avg/max/mdev = 0.572/0.572/0.572/0.000 ms234(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)235236--- Pinging from peer2 to peer3.wg-test-one ---237peer2: waiting for success: ping -c1 peer3.wg-test-one >&2238+ ping -c1 peer3.wg-test-one239PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes24064 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=63 time=4.14 ms241242--- peer3.wg-test-one ping statistics ---2431 packets transmitted, 1 received, 0% packet loss, time 0ms244rtt min/avg/max/mdev = 4.142/4.142/4.142/0.000 ms245(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.02 seconds)246247--- Pinging from peer2 to controller1.wg-test-one ---248peer2: waiting for success: ping -c1 controller1.wg-test-one >&2249+ ping -c1 controller1.wg-test-one250PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes25164 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.210 ms252253--- controller1.wg-test-one ping statistics ---2541 packets transmitted, 1 received, 0% packet loss, time 0ms255rtt min/avg/max/mdev = 0.210/0.210/0.210/0.000 ms256(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)257258--- Pinging from peer2 to controller2.wg-test-one ---259peer2: waiting for success: ping -c1 controller2.wg-test-one >&2260+ ping -c1 controller2.wg-test-one261PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes26264 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.280 ms263264--- controller2.wg-test-one ping statistics ---2651 packets transmitted, 1 received, 0% packet loss, time 0ms266rtt min/avg/max/mdev = 0.280/0.280/0.280/0.000 ms267(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)268269--- Pinging from peer3 to peer1.wg-test-one ---270peer3: waiting for success: ping -c1 peer1.wg-test-one >&2271+ ping -c1 peer1.wg-test-one272PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes27364 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=63 time=0.424 ms274275--- peer1.wg-test-one ping statistics ---2761 packets transmitted, 1 received, 0% packet loss, time 0ms277rtt min/avg/max/mdev = 0.424/0.424/0.424/0.000 ms278(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)279280--- Pinging from peer3 to peer2.wg-test-one ---281peer3: waiting for success: ping -c1 peer2.wg-test-one >&2282+ ping -c1 peer2.wg-test-one283PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes28464 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=63 time=0.475 ms285286--- peer2.wg-test-one ping statistics ---2871 packets transmitted, 1 received, 0% packet loss, time 0ms288rtt min/avg/max/mdev = 0.475/0.475/0.475/0.000 ms289(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)290291--- Pinging from peer3 to controller1.wg-test-one ---292peer3: waiting for success: ping -c1 controller1.wg-test-one >&2293+ ping -c1 controller1.wg-test-one294PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes29564 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=12.3 ms296297--- controller1.wg-test-one ping statistics ---2981 packets transmitted, 1 received, 0% packet loss, time 0ms299rtt min/avg/max/mdev = 12.337/12.337/12.337/0.000 ms300(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.03 seconds)301302--- Pinging from peer3 to controller2.wg-test-one ---303peer3: waiting for success: ping -c1 controller2.wg-test-one >&2304+ ping -c1 controller2.wg-test-one305PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes30664 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=0.227 ms307308--- controller2.wg-test-one ping statistics ---3091 packets transmitted, 1 received, 0% packet loss, time 0ms310rtt min/avg/max/mdev = 0.227/0.227/0.227/0.000 ms311(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 0.01 seconds)312313--- Pinging from controller1 to peer1.wg-test-one ---314controller1: waiting for success: ping -c1 peer1.wg-test-one >&2315+ ping -c1 peer1.wg-test-one316PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes31764 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.215 ms318319--- peer1.wg-test-one ping statistics ---3201 packets transmitted, 1 received, 0% packet loss, time 0ms321rtt min/avg/max/mdev = 0.215/0.215/0.215/0.000 ms322(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.01 seconds)323324--- Pinging from controller1 to peer2.wg-test-one ---325controller1: waiting for success: ping -c1 peer2.wg-test-one >&2326+ ping -c1 peer2.wg-test-one327PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes32864 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=4.22 ms329330--- peer2.wg-test-one ping statistics ---3311 packets transmitted, 1 received, 0% packet loss, time 0ms332rtt min/avg/max/mdev = 4.224/4.224/4.224/0.000 ms333(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.02 seconds)334335--- Pinging from controller1 to peer3.wg-test-one ---336controller1: waiting for success: ping -c1 peer3.wg-test-one >&2337+ ping -c1 peer3.wg-test-one338PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes33964 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.237 ms340341--- peer3.wg-test-one ping statistics ---3421 packets transmitted, 1 received, 0% packet loss, time 0ms343rtt min/avg/max/mdev = 0.237/0.237/0.237/0.000 ms344(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)345346--- Pinging from controller1 to controller2.wg-test-one ---347controller1: waiting for success: ping -c1 controller2.wg-test-one >&2348+ ping -c1 controller2.wg-test-one349PING controller2.wg-test-one (fd51:19c1:c1:aa00::1) 56 data bytes35064 bytes from controller2.wg-test-one (fd51:19c1:c1:aa00::1): icmp_seq=1 ttl=64 time=4889 ms351352--- controller2.wg-test-one ping statistics ---3531 packets transmitted, 1 received, 0% packet loss, time 0ms354rtt min/avg/max/mdev = 4889.412/4889.412/4889.412/0.000 ms355(finished: waiting for success: ping -c1 controller2.wg-test-one >&2, in 4.90 seconds)356357--- Pinging from controller2 to peer1.wg-test-one ---358controller2: waiting for success: ping -c1 peer1.wg-test-one >&2359+ ping -c1 peer1.wg-test-one360PING peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337) 56 data bytes36164 bytes from peer1.wg-test-one (fd51:19c1:3b:f700:6987:50a0:9b93:4337): icmp_seq=1 ttl=64 time=0.348 ms362363--- peer1.wg-test-one ping statistics ---3641 packets transmitted, 1 received, 0% packet loss, time 0ms365rtt min/avg/max/mdev = 0.348/0.348/0.348/0.000 ms366(finished: waiting for success: ping -c1 peer1.wg-test-one >&2, in 0.02 seconds)367368--- Pinging from controller2 to peer2.wg-test-one ---369controller2: waiting for success: ping -c1 peer2.wg-test-one >&2370+ ping -c1 peer2.wg-test-one371PING peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3) 56 data bytes37264 bytes from peer2.wg-test-one (fd51:19c1:c1:aa00:3b21:3ced:3e:89b3): icmp_seq=1 ttl=64 time=0.352 ms373374--- peer2.wg-test-one ping statistics ---3751 packets transmitted, 1 received, 0% packet loss, time 0ms376rtt min/avg/max/mdev = 0.352/0.352/0.352/0.000 ms377(finished: waiting for success: ping -c1 peer2.wg-test-one >&2, in 0.01 seconds)378379--- Pinging from controller2 to peer3.wg-test-one ---380controller2: waiting for success: ping -c1 peer3.wg-test-one >&2381+ ping -c1 peer3.wg-test-one382PING peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1) 56 data bytes38364 bytes from peer3.wg-test-one (fd51:19c1:3b:f700:e42b:bf85:33f4:f0b1): icmp_seq=1 ttl=64 time=0.360 ms384385--- peer3.wg-test-one ping statistics ---3861 packets transmitted, 1 received, 0% packet loss, time 0ms387rtt min/avg/max/mdev = 0.360/0.360/0.360/0.000 ms388(finished: waiting for success: ping -c1 peer3.wg-test-one >&2, in 0.01 seconds)389390--- Pinging from controller2 to controller1.wg-test-one ---391controller2: waiting for success: ping -c1 controller1.wg-test-one >&2392+ ping -c1 controller1.wg-test-one393PING controller1.wg-test-one (fd51:19c1:3b:f700::1) 56 data bytes39464 bytes from controller1.wg-test-one (fd51:19c1:3b:f700::1): icmp_seq=1 ttl=64 time=0.285 ms395396--- controller1.wg-test-one ping statistics ---3971 packets transmitted, 1 received, 0% packet loss, time 0ms398rtt min/avg/max/mdev = 0.285/0.285/0.285/0.000 ms399(finished: waiting for success: ping -c1 controller1.wg-test-one >&2, in 0.01 seconds)400401402403404