Has anyone made a similar switch? How was the experience? Was there any functionality that you weren't able to replicate? Or perhaps was especially difficult to implement?
(for others reading, re: pfsense - as the OP has gone a different way)...
I'm in the process of making the cut-over to pfsense w/learning curve - for the very same reason(s) yourself and @
eibgrad have made, with several of my own concerns as well... inevitably, it's the way forward...
I hate gui interfaces (as they are unscriptable and awkward to document) but in this case pfsense's gui has been a quite helpful and their gui serves as a sanity check as well...
I work on it late nights when I have time, and can interrupt the network - but continue using the asus stuff during the day to get things done... an rj45 a/b switchbox and extra cisco vlan-capable switch allows switching between two network hardware paths,a simple task, minus a few stale arp-cache incidents (cold boot is your friend)...
however... there is a given amount of prior knowledge necessary for anything more than a very basic pfsense implementation...
if you don't have these skill sets under your fingers - or the time to learn them - it will prolong the learning curve and you may be better off hiring someone to config the network initially...
I came from cisco CLI almost thirty years ago when a 1.544 Mbs T-1 line was 'fast' - and today my business runs on cisco but I don't/wouldn't try to admin it myself...
leveraging inexpensive hardware like asus routers has its place - I've been getting away with an asus cheap-seats implementation for years on a home network - but eventually the diminishing returns will catch up to us all...