Yes, with the new queue disciplines (codel and fq_codel) the "default priority for Unidentified Traffic" is not being changed! The script needs to be updated to meet the new discipline rules.still checking wont hurt, he might need to modify it to support codel and fq-codel, since the original was sfq.
hi fresh will you be updating the script due to the 380.67 beta 3 qos changes?
If you want to ensure that your tc commands aren't reprocessed (when the fq_codel patch is in place), look for the presence of /usr/sbin/realtc. If it exists, use it instead of /usr/sbin/tc. It will always be the real tc command, not the pre-processing faketc script.
This will work starting with beta 4 only - in beta 3 the patch was trying to make its own copy, which could lead to potential endless loop if the patch failed to be properly removed during a QoS configuration change.
i have fatih in your skillsIf it's within my skill I will. I hope asus didn't block off my pathway.
@ everyone else. I promised updates and didn't deliver yet. Had some major issues 4th of July weekend and had no time
cru d QOS_CHECK
echo "" > /jffs/scripts/firewall-start
Thanks for the update @FreshJR
So with the new custom rule template can we attribute a port to a specific category for proper identification like IPTV?
I have looked into the original post, however can't seem to find the updated script, I'm assuming you're still updating the post...
awesome, may i ask how would wan packet over head factor into the script, like how does it affect the scripts abilty to allocate bandwidth.Correct on both questions. Still updating posts and that type of filtering has been achieved.
Unfortunately I will not be fully explaining the port mask (used to define range) defining syntax used in the script today. I do not have enough time.
First post will be a little crude. Just wait out a little longer for full explanations.
awesome, may i ask how would wan packet over head factor into the script, like how does it affect the scripts abilty to allocate bandwidth.
So wan packet overhead is factored into the new script that what i was trying to ask, and wanted to know about.Bandwidth allocation was explained multiple times in this thread. WAN packet overhead should be included.
The gist of it is is that bandwidth allocation will give each category a guaranteed bandwidth but bandwidth from categories not using will NOT be lost.
That unused bandwidth will given to the category that needs it in order of priority. The allocations are really just minimums, and will be exceeded 99% of the time.
So wan packet overhead is factored into the new script that what i was trying to ask, and wanted to know about.
Thank you very much. Kudos. Keep up the good work.
if [ ! -f "/jffs/scripts/firewall-start" ]; then
echo "#!/bin/sh" > /jffs/scripts/firewall-start
elif [ -f "/jffs/scripts/firewall-start" ] && ! head -1 /jffs/scripts/firewall-start | grep -qE "^#!/bin/sh"; then
sed -i '1s~^~#!/bin/sh\n~' /jffs/scripts/firewall-start
fi
/jffs/scripts/FreshJR_QOS # Added By FreshQOS
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!