Which network gateway do you actually need?
Most PC builders treat the gateway as an afterthought, then wonder why a gigabit plan feels sluggish once a few people are gaming, streaming and running a VPN at the same time. The gateway is the box that does NAT, firewalling, routing and often VPN termination, so it decides how well your whole network holds together. The tiers differ in what they do under load, not in their headline port speeds.
Entry-level gateways, like the TP-Link Omada ER605 class, run a modest SoC with hardware NAT offload. They route plain traffic at near wire speed on gigabit, but the moment you enable deep packet inspection, heavy VPN tunnels or IDS/IPS, throughput drops sharply because those tasks fall back to a slow general-purpose core. That is fine for a flat home network with a few dozen devices.
The sweet spot is either a stronger dedicated gateway with a multi-core SoC and SFP or 2.5G ports, or a small x86 box running OPNsense or pfSense. Here you get real CPU headroom, AES-NI for VPN crypto, and proper VLAN support. Enthusiast gear brings 10G ports, bigger connection tables and rack-style hardware. Diminishing returns hit fast: unless you have a multi-gig fibre plan, a 10G gateway just sits there idling and draws more power.
Upgrading and technical nuances
The biggest architectural split is hardware offload versus software forwarding. Offload engines in budget SoCs move packets quickly but only for simple flows. Features like traffic shaping, IDS/IPS or per-VLAN firewall rules can bypass the offload path, so the real figure is the throughput with your features turned on, not the box-art number. Check vendor documentation for the "with features enabled" figures.
For DIY builds, an Intel N100 or N305 mini PC with four 2.5GbE ports is a popular sweet spot. Look at the NIC more than the CPU. Intel i226-V controllers are well supported in FreeBSD and Linux, while some Realtek 2.5G parts can be fussy with drivers, offloading and stability under sustained load. If you want something more flexible, a spare AM5 or LGA1851 machine works, though it is overkill and idles at higher wattage than a purpose-built appliance. If you go this route, browse CPUs & Processors and Motherboards for low-power parts, and add an Intel-based PCIe NIC from Networking.
Firewall workloads are not RAM hungry, but Suricata rulesets and larger connection tables like headroom. 8GB is comfortable, 16GB if you run IDS/IPS plus DNS filtering. Check Desktop Memory only if you are building a full-size system, since most mini PCs use SO-DIMMs. For storage, a quality SATA or NVMe drive from Solid State Drives (SSD) matters because logging hammers cheap flash. Look for drives with decent endurance ratings, such as Samsung 990 or WD_BLACK families, rather than bargain-bin QLC.
Compatibility traps are common. Some NBN connections need PPPoE or VLAN tagging on the WAN, and a few software stacks handle PPPoE on a single core, which can cap a gigabit or multi-gig link. Also confirm your ISP's modem or NTD setup before assuming 2.5G WAN will deliver anything above gigabit.
For ecosystem simplicity, TP-Link Omada pairs a gateway with switches and access points under one controller, while Ubiquiti UniFi and MikroTik offer different balances of polish versus flexibility. Pick one ecosystem and stick with it, because mixing management platforms is a headache.
Practical things to check
Start with ports. Count how many WAN and LAN ports you need, and whether any are SFP. If you plan a second WAN for failover, confirm the gateway supports load balancing or failover natively. Some budget units limit which ports can be WAN.
Next, check power and thermals. Fanless appliances are silent but rely on a chunky aluminium chassis for passive cooling, so do not stuff them into a sealed cupboard with no airflow. A gateway runs 24/7, so sustained thermals matter more than peak. If you build your own, a small case from Computer Cases with a quiet fan from Fans, Heatsinks & Cooling keeps a hotter CPU stable. Avoid noisy 40mm fans with sleeve bearings, as they tend to develop rattles over months of continuous use.
For DIY builds, a decent PSU from Power Supplies or an ATX Power Supply is worth it, since a dodgy supply kills uptime. Pair the gateway with a small UPS if your area suffers brownouts, because a hard power cut can corrupt the filesystem on a software firewall.
Cabling is the other gotcha. Use proper Cat6 or better for 2.5G and 10G runs, and quality patch leads from Cables & Connectors. A cheap, kinked patch lead can negotiate down to 100Mbps and make you blame the gateway. If you use SFP+, match the module type and check vendor compatibility lists, since some gear locks to specific optics or DAC cables.
Lastly, confirm the management model. Cloud-only controllers can be convenient but may limit local control. If you value privacy, choose a model with a local controller or standard web interface.
Brands and local warranty
For off-the-shelf gateways, reputable names include TP-Link (Omada), Ubiquiti, MikroTik, Netgate and Protectli. For DIY mini PCs, buy from brands with documented BIOS support and genuine Intel NICs, and avoid no-name boxes with unlabelled chipsets that may ship with questionable firmware.
Genuine Australian warranty matters more for gateways than most hardware because the device is always on and everything depends on it. If it fails, you lose internet for the whole house or office. Local warranty means you deal with an Australian reseller under Australian Consumer Law rather than posting a unit overseas and waiting weeks. It also ensures the unit is built for local power and certified for use here. Grey imports can void support, so check the seller before buying.
Frequently asked questions
Do I need a separate network gateway if my ISP modem already routes?
Not always, but a dedicated gateway gives you better firewall control, VLANs, VPN and monitoring. Most ISP modems have limited features and weak Wi-Fi, so many people put the modem into bridge mode and let their own gateway handle routing. Check that your ISP supports it first.
Is a 2.5G WAN port worth it?
Only if your plan or internal network can use it. Many gigabit plans cap below 2.5G, so the port is future-proofing. If you are upgrading to a faster plan soon, it is worthwhile. Otherwise gigabit is perfectly fine.
Can I use an old PC as a gateway?
Yes, and it works well with OPNsense or pfSense. Just add a good dual-port Intel NIC. The catch is power draw and noise, so a small low-power box is usually better for something running 24/7.
How much CPU power does a gateway need?
For basic routing, very little. VPN, IDS/IPS and traffic shaping are what demand cores, and single-thread speed matters for PPPoE. A modern low-power quad-core is plenty for gigabit.
Will a new gateway fix my Wi-Fi?
No. The gateway handles routing, not wireless coverage. For Wi-Fi, you want dedicated access points. A better gateway can still help with congestion and QoS, but it will not extend range.
