Thank you. We will try this and see if it works. ... View more

The 350 clients is during the whole day, not concurrent. The normal bandwith utilization is normally approx. 25 Mbit/s with som peaks racing 100-120. That is far from tha capacity of the MX and I can't see why it should be needed to use limitations/quota for the clients.   I guess that the MX sees one VPN-connection as one client, but I am not sure about that. There is not much traffic going there anyways ... View more

There are local static routes for the vlans defined on the MX. The Client tracking mode is set to MAC address. We have some layer 3 Cisco switches that handles some routing for clients. I see from the description that the IP address mothod should be used for client tracking. However, that will require us to have a split network. I can not see why the browsing should be slower with this tracking method. That must be a bug or bad design. Will the change of tracking method interrupt traffic in any way? Will it cause downtime and a need og reconfiguration?   ... View more

The MX100 has a recommended limit of 500 users. During the time period we tested the filtering there was approx 350 unique clients, but the usage peaked at 70 Mbit/s. That is far from the stated 650 Mbit/s with  Advanced security Throughput. Anyway, the number of users should not be a problem. What matters is the number og concurrent sessions and the throughput at the given tim.   The WAN uplink is set to the speed offered by our ISP provider. Each client does not have any limit. We only experience the lag when the content filtering is enabled. I don't find any place to view the usage in real time, but in the summary report it is not over 60% during these tests. We have 6-7 VPN site-to site connections.   With these numbers the MX should not be over-utilized, but could it be anyway? ... View more

I have tried both enabling several and only one (Pornography). There is no difference. The same applies when eanbling one or more threat categories. ... View more