Project

General

Profile

Actions

Bug #8616

closed

When reconfiguring a captiveportal, connected users get disconnected and can't login back

Added by A FL almost 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
Captive Portal
Target version:
Start date:
07/03/2018
Due date:
% Done:

100%

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

Description

Hello,

I noticed a weird behaviour with captiveportal when reconfiguring a CP while active users are connected : When administrator saves settings, ipfw rules are automatically flushed.

This is a big problem when editing captive portal settings while some users are connected : user are technically disconnected and are redirected to the login page (because ipfw rules are flushed), but they are still considered as connected and are unable to log-in again (because they are still present in the sqlite database).

This happen because when settings are saved, captiveportal rules are re-appplied unconditionally to the network interface.

One easy/dirty workaround would be to flush sqlite3 database when re-applying ipfw rules (meaning users get will get disconnected, but will be able to login again).

One (maybe better) fix would be to apply ipfw rules only if necessary (eg, when changing the captive portal’s network interface or some key settings) and to connect-back users after applying rules.

Actions

Also available in: Atom PDF