Thanks, wasn't exactly sure how to make the script reading, guessing, and trial lol.You don’t need the sleep commands nor the stop/starts in qos-start.
And with 75ms target, I suggest interval be 170ms (however much your target exceeds 5ms, increase interval by the same absolute amount). 100 + ( 75 - 5 ) = 170.
Just confirm all the settings and script took effect by running:Thanks, wasn't exactly sure how to make the script reading, guessing, and trial lol.
Edit:
Thanks for all your help seems to be working now grade is A ; seriously doubt I would have been able to figure this out myself.
service restart_qos
tc -d qdisc ls
Just confirm all the settings and script took effect by running:
Code:service restart_qos tc -d qdisc ls
#!/bin/sh
sed -Ei '/TQAU parent 2:[3-9][0-9] .*SCH/ s/$/ target 95ms interval 190ms/g' /tmp/qos
Yep it was on.Make sure JFFS Custom Configs & Scripts is enabled in the GUI ( Administration/System page).
chmod 755 /jffs/scripts/qos-startYep it was on.
chmod 755 /jffs/scripts/qos-start
#!/bin/sh
/tmp/qos stop
sed -Ei '/TQAU parent 2:[3-9][0-9] .*SCH/ s/$/ target 95ms interval 190ms/g' /tmp/qos
/tmp/qos start
Turns out the firmware doesn’t call qos-start for bandwidth limiter mode. Sorry, my bad. I hardly ever looked into this mode before.Still nope. Even tried gutting a different script I know works "nat-start" rewriting it by putting my script into the file changing the name and overwriting qos-start. Must be the script itself?
-rwxr-xr-x 1 Dave root 97 Oct 2 13:03 qos-start
From what I can see in my system logs qos-start isn't even mentioned.
./qos-start doesn't execute the script.
Changed the script to add the start stop command I noticed if I did "sed -Ei '/TQAU parent 2:[3-9][0-9] .*SCH/ s/$/ target 95ms interval 190ms/g' /tmp/qos" without it then it wouldn't change if I did it manually. So now when I use ./qos-start I can change the config faster then writing it in manually and it works.
So if added it to services-start "@reboot sleep 2m ./jffs/scripts/qos-start" would that work or would it work if it was a cron job?
Edit: Tried it in services-start didn't work. but I think I'm on the right track idk.
Code:#!/bin/sh /tmp/qos stop sed -Ei '/TQAU parent 2:[3-9][0-9] .*SCH/ s/$/ target 95ms interval 190ms/g' /tmp/qos /tmp/qos start
Neat.An example of what you can do in /jffs/scripts/service-event-end.Bash:#!/bin/sh if [ echo "$1" | grep -q "start" ] && [ "$2" = "qos" ]; then /tmp/qos stop sh /jffs/scripts/qos-start /tmp/qos start fi
qos-start script (discription not actually in script):
#!/bin/sh
sed -Ei '/TQAU parent 2:[3-9][0-9] .*SCH/ s/$/ target 95ms interval 190ms/g' /tmp/qos
Service-Event-End Script(discription not actually in script):
#!/bin/sh
if echo "$1" | grep -q "start" && [ "$2" = "qos" ]; then
/tmp/qos stop
sh /jffs/scripts/qos-start
/tmp/qos start
fi
EUREKA!!You can runservice restart_qos
without much impact.
If you want, you can move the sed to the service-event-end in place of the call to qos-start. Or just leave well enough alone.
If you switch to CAKE or Traditional QoS on the router, you will want to remove these scripts.
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!