OPNsensePIAWireguard
This script automates the process of getting Wireguard setup on OPNsense to connect to PIA's NextGen Wireguard servers. It will create Wireguard Instance(Local) and Peer(Endpoint) on your OPNsense setup.
Runssource: GitHubPythonBSD-3-Clausecommit a0b3dad1e459
Python, BSD-3-Clause licensed. The project labels itself: firewall, opnsense, privateinternetaccess and wireguard.
OPNsensePIAWireguard runs. An Argusic agent installed it in 4 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The PIAWireguard.py script completes its full workflow against mocked OPNsense and PIA APIs: creates WireGuard instance and peer, registers with PIA server, sets up port forwarding alias, and logs 'Finished' with exit 0.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Script called real PIA endpoints instead of mocks due to DNS: override_dns() uses private IPs (10.1.0.x) that are unrouteable in this container, and plain requests.get() had no proxy10 minutes
- Missing Python dependency 'requests'2 minutes
- Missing 'netstat' binary (OPNsense/FreeBSD host tool)1 minute
- Missing '/usr/local/sbin/configctl' binary (OPNsense-specific)1 minute
- Unwritable '/usr/local/www/' (OPNsense web root)1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- PYTHON script PIAWireguard.py runs, tested: --listregions (listed UK London, exit 0), --debug (monitor mode, exit 0), --debug --changeserver london (full end-to-end: OPNsense WG create, PIA token, addKey, setServer/setClient, reconfigure, gateway file, port-forward getSignature/bindPort, alias addItem/reconfigure, all HTTP 200, exit 0)
- Model tokens used
- 3,581,300
- Exact commit tested
- a0b3dad1e459
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: EXIT=0 2026-10-27 10:43:28 INFO:UK London | ID: uk | Port forwarding: True | Geo-located: False 2026-10-27 10:43:28 INFO:* Geo-located means these servers is not physically located in the region … All three entry points work: `--listregions`, `--changeserver`, and plain monitoring run. Let me cl… 2026-10-27T10:43:38.952387Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… exec /bin/sh -lc 'echo "final state: repo is untouched, tests ran successfully clean"' in /work/repo succeeded in 0ms: final state: repo is untouched, tests ran successfully clean tokens used 3,581,300
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 4 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 4 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/opnsensepiawireguard)Questions
- Does OPNsensePIAWireguard run?
- Yes. OPNsensePIAWireguard runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test OPNsensePIAWireguard?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a0b3dad1e459. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OPNsensePIAWireguard?
- The run that produced this verdict cost $0.73: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OPNsensePIAWireguard take to install?
- 4 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OPNsensePIAWireguard need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OPNsensePIAWireguard?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OPNsensePIAWireguard?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.