Up limiter in captive protal cannot be deleted

[D3messiah]

using 2.4.4-p1 and 2.4.4.-p3 this bug seems to insist. When trying to delete or disable the Per-user bandwidth restriction it has no effect. even after disabling captive portal upload limit still effect. I did not use traffic shaping. Limiter info still has data even after removing all limiters or and disabling captive portal. The only way to remove the captive protal limiter is disable the portal then reload filter. Yet after the limiters are gone the upload limiter still stock. Without pfsense I get 5-7 mbps up but with pfsense i can only get 1mbps up. no limiters info. Somewhere outhere the limiter i created for upload 1 mbps still exist. fresh install of pfsense i get normal speed.

[free4]

@D3messiah said in Up limiter in captive protal cannot be deleted:

using 2.4.4-p1 and 2.4.4.-p3 this bug seems to insist. When trying to delete or disable the Per-user bandwidth restriction it has no effect.

that is expected : the new settings will only apply to new users, not already connected users.

@D3messiah said in Up limiter in captive protal cannot be deleted:

even after disabling captive portal upload limit still effect.

this however, isn't normal at all.
would you have a list of steps to make in order to reproduce the issue? how could I reproduce the issue myself ?

@D3messiah said in Up limiter in captive protal cannot be deleted:

Limiter info still has data even after removing all limiters or and disabling captive portal.

how did you check for limiter info? using ipfw pipe command ?

[Gertjan]

@D3messiah said in Up limiter in captive protal cannot be deleted:

When trying to delete or disable the Per-user bandwidth restriction it has no effect.
....
I did not use traffic shaping

When you use the "Per-user bandwidth restriction", you actually instructed to 'ipfw' to build pipes for the connections, these pipes produces the band with restriction. I guess this is pretty close to traffic shaping ^^

When you de-activate the captive portal on an Interface, ipfw won't run any more. That ends any "bandwidth restriction" related to the captive portal.

As @free4 said : show us the

ipfw pipe show

command when the portal is down.
If you don't use any traffic shaping else where, then something bad's going on.

Don't use less then 2.4.4-p3. You'll get bitten by other bugs.