[alias_neo]

I've replied to a couple of others, normally I would have recommended Ubiquiti, but I no longer do. Not just because of their recent breach debackle, but because their software quality has declined since some of their best developers left.

The short but not so useful answer is, run something with pfSense or similar, I hear PCEngines hardware works well and is open source from the bootloader up.

Ubiquiti has hardware offloading using Cavium hardware so you need to get some throughout tests if you need high bandwidth in hardware without the offloading hardware.

[aborsy]

Although netgate’s recent debacle calls into question the code quality of pfsense as well:

https://lists.zx2c4.com/pipermail/wireguard/2021-March/00649...

[hedora]

I can recommend PC Engines (though a bit pricey, and kind of a hobby project to set up), and also Ubiquiti (ignoring the recent debacle).

Both are generally maintenance free once they’re set up.

[stilisstuk]

Considering linksys WRT3200ACM. Heard pfsense is not good with wireless.

[Daho0n]

I switched to pfsense* from a WRT. Awful router! It uses a cloud service to log in and nine times out of ten the awfulness that is their app cannot "locate a Linksys router on the network" even from a phone using the routers WiFi. I even tried flashing OpenWRT which was much better but the hardware still sucked and had to be restarted often. Cannot recommend (sadly I did recommend it to a friend before I knew how awful it is and he has the exact same problems even though he owns a different WRT model (1900 I think)).

* I'd recommend OPNsense over pfsense. If nothing else then because they break licenses (pfsense is NOT open source as they claim. You cannot built from the sources they provide).

[katbyte]

Pfsense isn’t a replacement for ubiquity if you want a single plane for firewall switch’s and aps - I don’t know if any reasonable one sadly