Project

General

Profile

Actions

Bug #13477

closed
CC KP

Captive Portal disconnecting a single user stops all traffic.

Bug #13477: Captive Portal disconnecting a single user stops all traffic.

Added by Christopher Cope about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
Captive Portal
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:

Description

Steps to reproduce:

  1. Disconnect a user from Captive Portal in Status > Captive Portal
  2. Traffic for all users stops completely
  3. Reconnect a different user to Captive Portal
  4. Traffic starts flowing again for all devices

Related issues 1 (0 open1 closed)

Related to Regression #13488: All Captive Portal users are given the same limiter pipe pairResolvedKristof Provost

Actions

AP Updated by aleksei prokofiev almost 4 years ago Actions #1

Tested on 22.05 and I can confirm this behavior.

MM Updated by Marcos M almost 4 years ago Actions #2

  • Related to Regression #13488: All Captive Portal users are given the same limiter pipe pair added

MM Updated by Marcos M almost 4 years ago Actions #3

  • Related to deleted (Regression #13488: All Captive Portal users are given the same limiter pipe pair)

MM Updated by Marcos M almost 4 years ago Actions #4

  • Is duplicate of Regression #13488: All Captive Portal users are given the same limiter pipe pair added

MM Updated by Marcos M almost 4 years ago Actions #5

  • Is duplicate of deleted (Regression #13488: All Captive Portal users are given the same limiter pipe pair)

MM Updated by Marcos M almost 4 years ago Actions #6

  • Related to Regression #13488: All Captive Portal users are given the same limiter pipe pair added

MM Updated by Marcos M almost 4 years ago Actions #7

  • Status changed from New to Resolved
  • Assignee set to Kristof Provost
  • Target version set to 2.7.0
  • Plus Target Version set to 23.01
  • Release Notes changed from Default to Force Exclusion

Tested latest snap. This is no longer a problem after the fix in the related issue #13488.

Actions

Also available in: Atom