The other concern - and
@thiggins brought this up on the review - is the 256MB RAM...
I probably need to explain myself a bit more on this one... with NAT and SPI, we track states not by clients, but by connections - as some clients open and maintain many connections, and some don't.
A general rule of thumb is to reserve/allocation 10 percent of total memory for the state tables - classic demand/capacity theory, which is based on queuing theory, which most communications and network engineers have a decent handle on when designing platforms - need to make sure we're "right-sized" so we don't spend too much overbuilding, or underbuild and have a bad user/customer experience.
Each entry in the state table takes roughly 1Kbit of ram, and in a 1GB system, we can support approximately 100 clients - this is also why many vendors limit the total number of clients on consumer routers, because you have to... they're memory bound.
Once the memory limit is hit, one of two things happen - either connections get blocked, or older entries must be flushed from the table, which can impact clients that maintain connections for a long period of time (think watching netflix for example) - so it's actually better to block than to shed in most cases.
The recent move by many of the vendors to 512MB takes some of this pressure off, but the limit is a hard one.
This is also why after an extended bit torrent session that sometimes one has to power cycle the router, as the state tables are absolutely full (and one of the reasons that folks get into trouble with running a torrent client on the router itself).
Now all that being said - most of the current top-tier machines are running 512MB, and they seem to be pretty good with this in most cases - even the WRT1900acV2/ACS and the EA8500 have 512MB, so I was pretty amazed with the EA9500 being limited to 256MB, which suggests roughly a 25 client max (give or take a few depending on traffic use cases).
It seems like a step backwards, esp. when we add 4 more gigabit ethernet ports, and the second 5GHz radio - SmartConnect needs to track state there as well to make sure it knows where the clients are... if we throw samba and/or cups into the mix, along with DLNA and OpenVPN, this device seems very memory bound.
Tim - can you confirm with Linksys that it is 256MB, and maybe pass along this post - it would be interesting to see their response.