Wrong limiter speed
-
interface using em0:em1
set limiter to 905 Mbit/s
speedtest can't go over 640 Mbit/sif i set my limiter to 965 Mbit/s
il'l get around 853 Mbit/smore the limiter is high more de accuracy is wrong
is there a broblem with limiter ??
-
I have the same issues. I wind up just increasing the limiter until I can get the actual speeds I'm looking for. At the moment, I have a rule for 350Mbps but I can't scratch above 270Mbps with it. I tell users it's set at 300Mbps and they are within 10% so it's OK, but I don't understand it. It'd be great to get an answer on this, though.
-
I believe that netgate does not worry about 2 idiots who are in the same boat, about a problem which does not exist! do'H
-
@Jimbohello said in Wrong limiter speed:
I believe that netgate does not worry about 2 idiots who are in the same boat, about a problem which does not exist! do'H
Well, it must exist since we are both experiencing it. I just kinda gave up on trying to fix it long ago. I remember posting about it but I can't remember if I ever got a response, much less a resolution. I know what settings will give people the numbers they want to see so I just go with it.
In actuality, I logged into the forums today looking for an answer to this exact same problem. I've tried different algorithms with no success.
-
@Stewart Have you tried setting Powerd to maximum in
System / Advanced / Miscellaneous?
I remember encountering something similar once which the above fixed. -
@bobbenheim Thank's
did not change noting !
your help was please ! thanks -
Hello!
Never used a limiter in pfsense, but the docs say :
"Limiters cannot effectively guarantee a minimum bandwidth amount for a pipe or queue, only a maximum."
I understand this to mean that you wont get more than the limit, but you could get less. Blowing past the limit would be one thing, but never hitting it? I dont know...
https://docs.netgate.com/pfsense/en/latest/trafficshaper/limiters.html
John
-
Hey
Tested it right now
And hit the limit (not able to get more than the limit)Limit 5 on a 100
The first time
Then 4,5 then 4,8....Not gettin more than the limit an hit it once ;) out of 3
-
@Jimbohello what system are you running pfsense on and are you seeing higher speeds without limiter?
-
@serbus
first off, i read the documentation already.
cant’t garranty minimum exacly !
but suppose to garranty a maximum, that’s the issue.if you look a the firts post ! you will understand better ! the situation does appears on a breach of certain point !
let say max limiter is 300 you will get 270
let say limiter is set to 425 you will get 390
let say limiter is set to 905 you will get 670
and so on ! nothing to do with limiting 5 or 10 or 20! we are talking about more the limiter size increace more de accuracy is wrongthank’s
-
lenovo m93p
core i5 4th gen
no hardware offloading
aes-ni
2 nic intel prouseless stuf disable in bios / onboard nic / onboard sound card / etc !
-
and ! yes the maximun reach point is reach without limiter !
940 -945 approx -
We've seen in APU1 and APU2 boxes. The disparity gets larger and larger the higher we set it.
-
@Stewart said in Wrong limiter speed:
We've seen in APU1 and APU2 boxes
yes same here.. but with some testing
the limiter is set to a solid work.we use it to prevent clients / networks / hosts
to consume all the bandwidth available -
What does Diagnostics > Limiter Info show during the testing?
See post https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/38 ... "On downloads you will commonly see below the configured bitrate because each time you hit the limit pfSense will tell the sender to slow down below the limit."
"minimum bandwidth" I think is referring to that limiters can't guarantee a device will get any bandwidth at all, they can only cap the device.
-
@Jimbohello what are your limiter settings?
-
@bobbenheim
<dnshaper>
<queue>
<name>in</name>
<number>1</number>
<qlimit></qlimit>
<plr></plr>
<description></description>
<bandwidth>
<item>
<bw>799</bw>
<burst></burst>
<bwscale>Mb</bwscale>
<bwsched>none</bwsched>
</item>
</bandwidth>
<enabled>on</enabled>
<buckets></buckets>
<mask>none</mask>
<maskbits></maskbits>
<maskbitsv6></maskbitsv6>
<delay>0</delay>
<sched>wf2q+</sched>
<aqm>droptail</aqm>
<ecn></ecn>
<queue>
<name>in-queue</name>
<number>1</number>
<qlimit></qlimit>
<description></description>
<weight></weight>
<enabled>on</enabled>
<buckets></buckets>
<mask>dstaddress</mask>
<maskbits>32</maskbits>
<maskbitsv6>128</maskbitsv6>
<aqm>droptail</aqm>
<ecn></ecn>
</queue>
</queue>
<queue>
<name>out</name>
<number>2</number>
<qlimit></qlimit>
<plr></plr>
<description></description>
<bandwidth>
<item>
<bw>799</bw>
<burst></burst>
<bwscale>Mb</bwscale>
<bwsched>none</bwsched>
</item>
</bandwidth>
<enabled>on</enabled>
<buckets></buckets>
<mask>none</mask>
<maskbits></maskbits>
<maskbitsv6></maskbitsv6>
<delay>0</delay>
<sched>wf2q+</sched>
<aqm>droptail</aqm>
<ecn></ecn>
<queue>
<name>out-queue</name>
<number>2</number>
<qlimit></qlimit>
<description></description>
<weight></weight>
<enabled>on</enabled>
<buckets></buckets>
<mask>srcaddress</mask>
<maskbits>32</maskbits>
<maskbitsv6>128</maskbitsv6>
<aqm>droptail</aqm>
<ecn></ecn>
</queue>
</queue>
</dnshaper> -
@noplan Certainly we can make it work. It's just that the numbers don't really line up. Oh, and fast.com goes crazy when put through one of the limiters. Through the ones we set up last week fast.com couldn't get more than 120Mbps no matter what the limiter was set to. Without the limiter it would get the full 600+Mbps. I thought that was odd. Speedtest.net is the one that would increase, just at a different rate to what the limiter was being set at.
-
@Jimbohello Can you try enabling ECN in the limiter (not the queues) and see if that makes a difference, else you might also need to increase queue length from the default 50 to something larger.
Have you made any tweaks in loader.conf.local? -