Bug #13475
closed
Captive Portal per-user limiters malfunction
Added by Georgiy Tyutyunnik about 2 years ago.
Updated almost 2 years ago.
Affected Architecture:
All
Description
22.05 6100 with captive portal and enabled per-user bandwidth is experiencing traffic being shaped for the whole interface instead of per-user at times. Changing or deapplying/reapplying per-user bandwidth limitations seems to fix the issue for a period of time. The reoccurrence is more frequent with heavier load.
Correction: the problem is present with and without per-user bandwidth enabled.
User can reliably reproduce this on his system:
1) disconnect a user from captiveportal by status->captiveportal
2) traffic for all users stops completely
3) reconnect a different user to captiveportal
4) traffic starts flowing again for all devices
Georgiy Tyutyunnik wrote in #note-2:
Correction: the problem is present with and without per-user bandwidth enabled.
User can reliably reproduce this on his system:
1) disconnect a user from captiveportal by status->captiveportal
2) traffic for all users stops completely
3) reconnect a different user to captiveportal
4) traffic starts flowing again for all devices
I created a different redmine for that issue. It seems related, but I'm not sure it's the same cause. The original complaint about the per-user limits explained that it would just stop working after a certain amount of time until the "per-user" settings were changed and saved.
https://redmine.pfsense.org/issues/13477
- Related to Regression #13488: All Captive Portal users are given the same limiter pipe pair added
- Status changed from New to Duplicate
- Assignee set to Kristof Provost
- Target version set to 2.7.0
- Plus Target Version set to 23.01
- Target version deleted (
2.7.0)
- Plus Target Version deleted (
23.01)
Also available in: Atom
PDF