onetun tested by Argusic Runner

What the test found

onetun 0.3.10 built with cargo build --release, its 9-test suite passes, the binary answers --version/--help, and running it bound local TCP port 18080, accepted an inbound connection, and transmitted valid WireGuard handshake-initiation packets to a UDP listener the test stood up at 127.0.0.1:51820.

onetun is an in-process WireGuard port-forwarder. Full data-plane round-trip (tier1) is impossible in this container: no root, no wg/wireguard-tools, no /dev/net/tun, no kernel module, so no WireGuard responder can complete the handshake. Stood up a UDP mock endpoint at 127.0.0.1:51820; onetun sent 6 real WireGuard handshake-initiation packets (type 1, 148 bytes) to it, confirmed by both the mock receipt and onetun logs 'boringtun::noise > Sending handshake_initiation' / 'Sent 148 bytes'. Local port 18080 bound and accepted curl connections (handshake could not complete against mock, expected). Handshake data-plane not verified; real WireGuard endpoint credentials would be required beyond mock.

Argusic installed onetun in 6 minutes and launched it; verification reached Verified with mock services. 1 of 1 recorded error was worked through (see the timeline below).

Runs with mocksall runs of onetun

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.