Editorial desk
OPNsense Router Editorial
The editorial desk that publishes OPNsense Router. It is a byline for the site's editorial process, not a person, and this page carries no author biography because there is no individual author to describe.
How this desk works
- Articles are researched from primary sources: vendor and project documentation, published standards and specifications, release notes, advisories, and measurements published by the people who took them.
- Drafts are produced with AI assistance and then edited against those same sources before publication.
- Nothing published here claims hands-on lab testing, benchmarking, or first-hand measurement. Where a figure comes from a datasheet or someone else's test, the article names the source.
- Corrections go to hello@opnsenserouter.com and are made on the affected page. Funding is set out on the disclosure page.
Posts (5)
- Configuration
OPNsense Traffic Shaping and QoS Explained: FQ-CoDel
How OPNsense shapes traffic with pipes, queues and rules on dummynet, why FQ-CoDel fixes bufferbloat, and what weights and masks really do.
- Networking
OPNsense WireGuard Site to Site Tunnel: Routing Setup
Connect two OPNsense networks with WireGuard, preserve IoT isolation, configure Allowed IPs and firewall rules, and troubleshoot CGNAT
- Hardware
OPNsense Hardware Requirements: CPU, RAM & Storage
See the official OPNsense CPU, RAM and storage tiers, then size for gigabit routing, Suricata, VPNs, state tables and compatible NICs.
- VPN
WireGuard vs OpenVPN vs IPsec on OPNsense
Compare WireGuard, OpenVPN and IPsec on OPNsense by cryptography, roaming, CPU cost and interoperability, and see which tunnel fits each job.
- Troubleshooting
OPNsense WireGuard Setup Problems: Handshake, NAT, MTU
Fix an OPNsense WireGuard tunnel that won't connect: read the handshake, then check the WAN rule, keys, allowed addresses, outbound NAT, DNS and MTU.