Maximum concurrent connections without user logins

  • We are using the captive portal without user logins.  The users just see an acceptable usage page and then click "accept" to continue.
    How does setting the Maximum concurrent connections  value affect this?  My concern is a malicious user opening several connections to the portal page

  • "This setting limits the number of concurrent connections to the captive portal HTTP(S) server. This does not set how many users can be logged in to the captive portal, but rather how many users can load the portal page or authenticate at the same time! Default is 4 connections per client IP address, with a total maximum of 16 connections."