Playing with fq_codel in 2.4
-
That's an idea, I'll give that a shot!
-
Yea, that didn't work.
-
Just for testing purpose, try to change bw limiting to delay limiting :
pipe 1 config delay 0ms
for both pipes
-
Sorry gone for a few days, vacation.
I gave that a shot by changing the /tmp file, it doesn't seem to have an affect. I am only changing the /tmp file, maybe it needs to be rebooted and hardcoded into the file? The only reason I haven't done this is because I haven't seen the results everybody is reporting…
-
Yes it's need to be rebooted or reloaded with```
/etc/rc.reload_allAfter you did that run the following command``` ipfw sched show ```and you should see something like``` 00001: unlimited 0 ms burst 0 ```for the both pipes you have.
-
@w0w:
Yes it's need to be rebooted or reloaded with```
/etc/rc.reload_allAfter you did that run the following command``` ipfw sched show ```and you should see something like``` 00001: unlimited 0 ms burst 0 ```for the both pipes you have.
Yes, all relatively simple and you've been great at walking through the steps you put in place.
I'm getting this for both pipes.
00003: unlimited 0 ms burst 0
00004: unlimited 0 ms burst 0
Yet I can't get better than a B rating for bufferbloat, which is the same if I literally do nothing at all….
-
But what about VPN bandwidth? Are you still getting 120Mbps?
-
That part HAS improved, looks like it does get about 145-ish or so which is about right. It just does nothing for bufferbloat.
-
Can you post the full output of```
ipfw sched show -
I'd like to look at implementing this, but I was wondering
Anyone know the status of pfsync + limiters?
-
I'd like to look at implementing this, but I was wondering
Anyone know the status of pfsync + limiters?
What was the last status you know? :D
-
The last status I know is that the pfsense book says not to use pfsync and limiters together, but doesn't explain why
-
The last status I know is that the pfsense book says not to use pfsync and limiters together, but doesn't explain why
This is actual. https://redmine.pfsense.org/issues/4310 have 0% progress.
-
@w0w:
The last status I know is that the pfsense book says not to use pfsync and limiters together, but doesn't explain why
This is actual. https://redmine.pfsense.org/issues/4310 have 0% progress.
D=
-
Is there any chance fq_codel will make it into the 2.4 GUI in limiters?
-
Definitely not!
They are keeping eyes on it, but currently no plans, no moves, AFAIK. -
Darn. I'm thinking about switching back to pfSense but I really want fq_codel.
-
fq_codel, the ZFS of AQMs, or nearly. Cake aims to be the "ZFS", but close enough.
-
Is the command of "ipfw sched 1 config pipe 1 type fq_codel && ipfw sched 2 config pipe 2 type fq_codel" the same if I only have 2 root limiters? Both of them are root limiters one has a mask of source and the other has a mask of destination.
I would like to try this out but wondering if the command is different for just root limiters without "child" queues. Obviously I am highly dependent on the gui I am a bit confused with the ipfw command since it references both sched and pipe.
Thanks for any reply!
-
TS sample is for the root limiters also, if you have some troubles understanding, post the content of your /tmp/rules.limiter