Trafic shaping for Streaming to twitch as well as streaming Netflix/YouTube
-
Try to run the wizard HFSC and enable codel on all queues
-
I will try this. I start my stream in a few hours. Thank you in advance!
I will update this as soon as i know -
If it still doesn't work, use FairQ as your shaper, set your interface to 90% of your actual speed, have one queue on your interface, make sure it's the default and enable Codel on it.
-
I'll bet that if you just use dummynet and enable fq_codel via CLI and use that for all your traffic then your problem will be solved.
Fq_codel is like magic for latency sensitive traffic when the pipe is full.
EDIT: This requires 2.4.x to be installed.
-
I attempted to run the wizard in HFSC with CODEL enabled on all queues and it fixed the problem for me on my end but slowed the WiFi down to the speed of dial-up. Which kind of defeats the purpose of what i want to do. I am now going to try to run the wizard in CBQ and enable CODEL on all as well.
If it still doesn't work, use FairQ as your shaper, set your interface to 90% of your actual speed, have one queue on your interface, make sure it's the default and enable Codel on it.
Can you help me more with this or explain to me what you mean by having one queue on my interface?
thanks for all your help.
-
" but slowed the WiFi down to the speed of dialup"
That is strange it has nothing to do with specifically slowing down the wifi speed, try restarting pfsense after the traffic shaping setup. if that still does not work for you take Harvy66 advice, he is one of the best in traffic shaping here you cant get better advice then he can give you
-
fq_codel is not the same as codel. You can only implement it on dummynet and only via CLI. You just turn it on for everything and it will almost certainly solve your problem.
-
fq_codel is not the same as codel. You can only implement it on dummynet and only via CLI. You just turn it on for everything and it will almost certainly solve your problem.
Dude we for sure know what FQ_CODEL is and that it is not codel, but the OP has to install 2.4 RC first and install it from the command line, so it is not the supported way to advice yet till it is officially in pfsense
-
fq_codel I agree has a good chance of solving this, but if you not comfortable in doing all this in the cli, then try this.
HSFC for downstream and make sure to give the queue handling netflix realtime bandwidth allocation enough for it to stream optimally.
FairQ for upstream.
Enable codel on all queues.
By default the queue size is 50, in certain scenarios this may need to be increased for proper performance, if you increase do it in small chunks. so dont e.g. jump from 50 to 500. A larger queue makes it less likely for packet drops in that queue, and less likely to have packet ordering issues. However it also increases the possibility of buffer bloat.
There is also RED (random early detection), what this does is drop packets in a queue before the queue fills up, in anticipation of the queue filling up, the aim of this is to slow down throughput in that queue before it gets full.
The issue I think is very likely in the upstream, since streaming is uploading, its likely affecting the ack's from the netflix downstream traffic, so downstream shaping may not have much of an impact. Fairq+codel combo seems best for me on upstream on altq. Make sure acks for downstream traffic are properly been allocated to the 'ack' queue on the upstream.
-
fq_codel is not the same as codel. You can only implement it on dummynet and only via CLI. You just turn it on for everything and it will almost certainly solve your problem.
Dude we for sure know what FQ_CODEL is and that it is not codel, but the OP has to install 2.4 RC first and install it from the command line, so it is not the supported way to advice yet till it is officially in pfsense
It is officially in pfSense…. You don't install it from the CLI, you just select it.
-
fq_codel is not the same as codel. You can only implement it on dummynet and only via CLI. You just turn it on for everything and it will almost certainly solve your problem.
Dude we for sure know what FQ_CODEL is and that it is not codel, but the OP has to install 2.4 RC first and install it from the command line, so it is not the supported way to advice yet till it is officially in pfsense
It is officially in pfSense…. You don't install it from the CLI, you just select it.
Just to clarify, did you mean fq_codel is officially in pfSense or just Codel - the latter yes I would agree, but if the former, where do you select it?
-
You select it with ipfw
ipfw sched 1 config pipe 1 type fq_codelSo if you have dummynet setup with two pipes (up & down) and want to make fq_codel persistent, then in shellcmd ->
ipfw sched 1 config pipe 1 type fq_codel && ipfw sched 2 config pipe 2 type fq_codelIf you plug in a monitor on boot you'll see it load up fq_codel, no need to install anything at all, just select it on CLI, and if you want it to persist across reboots, use shellcmd.
-
You select it with ipfw
ipfw sched 1 config pipe 1 type fq_codelSo if you have dummynet setup with two pipes (up & down) and want to make fq_codel persistent, then in shellcmd ->
ipfw sched 1 config pipe 1 type fq_codel && ipfw sched 2 config pipe 2 type fq_codelIf you plug in a monitor on boot you'll see it load up fq_codel, no need to install anything at all, just select it on CLI, and if you want it to persist across reboots, use shellcmd.
That makes sense - my apologies, I misunderstood your original post and thought you meant selecting fq_codel in the UI vs the CLI.
-
Oh gotya, no worries. Stilla CLI selection, I was just saying it's all preinstalled and ready to go, no additional repositories or sideloading stuff into pfSense.
-
"It is officially in pfSense…. You don't install it from the CLI, you just select it."
You are spreading miss information. FQ_codel is officially in BSD not officially implanted in pfsense, it wil be officially implanted in pfsense when the pf team enable it and you can select it from the gui not playing around in cli.
-
Right, well it officially works. But sure, if nothing's official to you unless there's a box to check in a gui then by all means it isn't official. ::)
-
"if nothing's official to you unless there's a box to check in a gui then by all means it isn't official. ::)"
Exactly. if it was fully official pfsense devs would have put in the checkbox. hekk 2.4 is not even official release yet. Oh and keep hitting the smite as much as you like two can play that game lol if you cant have a simple conversation you should get a real smite lol
-
You keep on ignoring features unless someone builds a GUI box for you.
fq_codel is still the solution to this problem, and it is part of pfSense 2.4 - and it works, and it's easier to setup than ALTQ for this problem, and it's more effective.
-
You keep on ignoring features unless someone builds a GUI box for you.
fq_codel is still the solution to this problem, and it is part of pfSense 2.4 - and it works, and it's easier to setup than ALTQ for this problem, and it's more effective.
Thats not what I was saying, infect I used the cli also, all i said is that we know what fq_codel is and we know what it can do and it solves most of the problems and yes if the OP uses fq_codel his problems might be over, all I said is thet till 2.4 is fully released and fq_ is implemented I do not think it is a good Idea to suggest playing around in the cli to maybe newer people to pfsense or traffic shaping. Oh and looks like we are going to start having some fun with the smite game if you want it will do it :)
-
it's just copy paste into shellcmd - that has a GUI! not "playing around with cli".
I would argue that it's a much better idea to simply pass along very simple instructions on how to solve a maybe newer users problem with the appropriate tool, rather than suggesting they do a complicated workaround with ALTQ / HFSC which few people really understand to begin with - just because it has a GUI.
Anyways, if OP would like any help either method just ask.