Most people let their ISP give them a router – or maybe they go out and buy a decent consumer-grade model and call it a day. I went in a different direction.
I built my router from scratch using a Dell OptiPlex 3040 SFF, installed MikroTik RouterOS, and turned it into what I call my “turbo router.” And for my homelab needs? It’s perfect.
Why Not a Consumer Router?
Consumer routers are designed to be plug-and-play, and that’s fine for basic setups. But they fall short when you need:
- Granular DHCP control (like setting static leases or PXE boot options)
- Full visibility into routing behavior
- A proper CLI and firewall you can actually reason about
- Advanced network tools that don’t get dumbed down behind a web UI
- VPN connectivity that isn’t OpenVPN (poor quality) or IPsec (difficult to set up)
I wanted real control without the cost or complexity of rackmount gear. So I built it.
Turbo Router Specs
- Chassis: Dell OptiPlex 3040 SFF (repurposed from a retired desktop)
- CPU/RAM: Intel Core i5-6500 CPU, 8GB RAM
- Storage: 128GB Sandisk SATA SSD
- NICs: Two Intel Gigabit CT cards (one for WAN, one for LAN)
- OS: RouterOS 7 (installed bare-metal)
This system runs 24/7, silently tucked in the corner, and it doesn’t even flinch under full load from my gigabit fiber connection.
RouterOS: Why I Chose It
MikroTik’s RouterOS is a lightweight, high-performance routing operating system that turns just about any x86 system into a feature-packed network appliance. It’s the same software that runs on MikroTik’s routers, but on x86, you get full hardware performance, more memory, and storage headroom.
What I get from RouterOS:
- True static DHCP leasing with granular options
- WireGuard support built-in and ready to use
- PXE boot support via “Next Server” DHCP field
- Simple firewall/NAT rules that make sense
- Stable performance on modest hardware
- No cloud dependency, no phone app required
What It Handles in My Lab
- DHCP: All clients on
10.40.0.0/16get their leases from the turbo router. All core devices (VM hosts, desktops, infrastructure VMs) are mapped via static reservations. - PXE Boot Support: It points clients to the install server with a simple DHCP “next-server” directive. That’s it – dnsmasq on the install server handles the rest.
- Routing/NAT: It’s my gateway to the internet. WAN traffic passes through a gigabit fiber ONT, and RouterOS handles NAT, firewalling, and DNS forwarding.
- Firewall Rules: Minimal but effective – just enough to prevent unwanted inbound traffic while keeping everything lean.
- WireGuard VPN: Secure connections to Linodes I run, and to a colleague in Florida.
Why the Name “Turbo Router”?
Because it’s overkill in the best way. Most consumer routers struggle to juggle DHCP, DNS, routing, and a few dozen devices. This thing? It’s got x86 power, SSD speed, and 8GB of RAM – just for routing.
It boots fast. It routes fast. It just works, and it does it with a CLI and scripting support that most “smart routers” can’t even touch.
Final Thoughts
Could I replace this with a dedicated MikroTik RouterBoard, like an hEX or RB5009? Sure. But this box cost me almost nothing, and it runs like a tank. More importantly – it’s mine. I know how every part of it works, and if I want to add features, automate scripts, or expand the network, I don’t need to beg a vendor for firmware updates.
It’s not flashy, and it’s not cloud-connected. But it’s fast, flexible, and fully under my control.
And that’s what makes it turbo.
Leave a Reply