Project

General

Profile

Actions
Copy link

Bug #2270

closed

CP - default value of "Maximum concurrent connections per client IP address"

Added by Dim Hatz about 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
03/08/2012
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:

Description

I noticed the "Maximum concurrent connections per client IP address" ($maxprocperip) setting is used to set a value to lighttpd's evasive.max-conns-per-ip directive. However, if the $maxprocperip "Maximum concurrent connections" field is left empty in webGUI config, it doesn't create a lighty evasive.* directive at all in /var/etc/lighty-Captive*.

Since I can't seem to find how the webGUI comment "Default 4 connections per client IP, with a max of 16" is enforced, it seems like a small bug to me.

Either fix the comment in the webGUI ("default is no limit"), or use the $maxprocperip value from captiveportal.inc or set 

$captive_portal_mod_evasive = "evasive.max-conns-per-ip = 4"
in system.inc

Actions
Copy link
 #1

Updated by Ermal Luçi almost 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Jim Pingle almost 12 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF