OPNsense
-
Multi WAN Inbound Load Balance: DNS, BGP or a Proxy
Your router can't steer inbound connections. How to balance them across two WANs on OPNsense with health-checked DNS, a proxy front end, or BGP.
-
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.
-
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
-
OPNsense Requirements: Minimum and Recommended Hardware
OPNsense needs a 64-bit x86 CPU and 3 GB RAM at minimum, 8 GB and a 120 GB SSD recommended. See how states, Suricata, ZFS ARC and NICs change the sizing.
-
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.
-
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.