Does the MX actually cap the size of a scope you can create? Never tried anything larger than /21.
@PhilipDAth Are you referencing the recommended client count?
Not entirely certain how much I trust that because the MX84 says '200', which seems really low. I use the MX mostly as a firewall for the guest SSID to terminate to (so that we can do a non-routed VLAN vs NAT because roaming etc.) at our sites, with its own dedicated ISP.
What I look at more often is the throughput capabilities and go from there.
I usually default to a /21 for the MX to hand out DHCP for guest users (its only job really other than sending them out the internet). While this 'seems' high since /21 = 2k client count. I use it more as a deterrent for DHCP leases not being exhausted, not because we actually have 2k active clients connecting.
I set lease time to 4 hours. On average we might have around 300 to 500 active clients, but wireless works fine, WAN utilization rarely goes over 400Mbps (this specific circuit is 500Mbps), but every now and then it does (which is fine, just means its being used).
However right now it says there is around 750 clients on the DHCP table, (right now only 370 active). I 'could' use a /22 but it is getting a little close for comfort for the table to run out and its just a simple fix to me to avoid that by making it a /21.
CPU utilization has not gone over 25% from what I've seen (daytime usage).
**EDIT - I have top site content filtering enabled, but no AMP/IPS or any other fancy features (FYI).