The traffic download limit only applies half of what I give it. why?
-
@HLPPC Thank you for your reply, I'm not even using FQ_codel, I used Tail Drop with the default scheduler worse case weighted fair queueing on the LAN interface. As some users had previously noted, version 2.6 didn't have this problem.
Maybe the new FreeBSD 14 caused some conflicts I'm not sure, but it should be an easy problem to reproduce and detect.
-
After trying it...
I end up using the limiter on Floating Rules.
I use Taildrop - Codel - Taildrop
Then put the queue on Floating rules with Out direction..
I finally get the expected upload / download results.I think that has to be like that from 2.7.2
-
S SteveITS referenced this topic on
-
Is it a bug or configuration change?
I have the same problem.
-
-
Has to be a bug. After updating (which was a task in and of itself) from 2.7.0 my limiters aren't working as before. With a good amount of testing, I ended up basically doubling the limiters bandwidth to reach what it should be limiting to. Hopefully they find the reason for it, what a pain in the butt last few days.
-
I can confirm the same issue on six different pfSense firewalls. This is for sure a bug somewhere in the conversion.
Here what I experienced:
10240 Mbit/s limit --> Traffic does not pass anymore, like a blocking rule
50 Mbit/s limit --> about 46 Mbit/s
51200 Kbit/s limit --> about 49 Mbit/s
52428800 Bit/s limit --> about 50 Mbit/sCan others confirm the same?
Edit: Found another thread with the same issue, that the set limit does not match the applied limit.
-
I have since situated my limiters and have got them working properly now. Before upgrading to 2.7.2 (which was a task due to a bug) I installed an additional fail-over wan, which didn't have rules for the limiters. My rules were set per lan/vlan to use my gateway group and it's respective limiter. I had only made limiters for upload/download. My problem seemed to situate once I put my rules into the floating ruleset, made my limiters simple tail-drop with worst-case waieghted fair queueing, then made a queue for each limiter utilizing PIE with ecn checked. The rules used default gateway rather than gateway group (pfSense gateway is set to use the gateway group rather now) and the limiters were the actual queues I set up under the limiters. Hope it helps someone out there.
-
Ran into this issue just now. This is a bug. This bug is now old. This bug needs to be fixed. As a temp solution, I doubled the bandwidth in the queues as that's the trend I noticed.
-
@PhantomsWay It's been fixed since 24.03:
https://redmine.pfsense.org/issues/14854 -
@bipton said in The traffic download limit only applies half of what I give it. why?:
rules used default gateway
There is this, scheduled for 2.8...?
https://redmine.pfsense.org/issues/14854
"...if the gateway is left to default the limiter works as expected but if a specific gateway or a gateway group is specified the limiter [drops by half]."