Project

General

Profile

Actions
Copy link

Regression #13147

closed

Captive Portal: Idle timeout does not see activity

Added by Steve Wheeler over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Reid Linnemann
Category:
Captive Portal
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Force Exclusion
Affected Version:
2.7.x
Affected Architecture:
All

Description

The idle timeout value is applied regardless of activity from the connected user. Functions as a hard timeout.

Here set for 5mins:

May 10 22:11:00     logportalauth     387     Zone: test_zone - ACCEPT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10
May 10 22:16:08     logportalauth     45924     Zone: test_zone - IDLE TIMEOUT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10
May 10 22:17:19     logportalauth     387     Zone: test_zone - ACCEPT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10
May 10 22:23:09     logportalauth     5291     Zone: test_zone - IDLE TIMEOUT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10
May 10 22:23:28     logportalauth     387     Zone: test_zone - ACCEPT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10
May 10 22:29:10     logportalauth     14389     Zone: test_zone - IDLE TIMEOUT: unauthenticated, 3a:d2:8d:84:6e:56, 192.168.20.10

Tested: 22.05.a.20220510.1205

Related issues

Related to Todo #13100: Transition Captive Portal from IPFW to PFResolvedViktor Gurov

Actions
Actions
Copy link

Also available in: Atom PDF