Wondershaper in Post-Firewall

[britnet]

Hello,

I want to run the wondershaper.

Is this Code correct in post-firewall?

#!/bin/sh
/sbin/wshaper start "$1" 1024 128

My connection is: 1024 Downstream und 128 kbit/s upstream.

highest priority should have voip.

Can somebody help me?

[Styno]

Hello,

I want to run the wondershaper.

Is this Code correct in post-firewall?

#!/bin/sh
/sbin/wshaper start "$1" 1024 128

My connection is: 1024 Downstream und 128 kbit/s upstream.

highest priority should have voip.

Can somebody help me?

The place is right, but I recommend lower bandwidth settings. I suggest 960 and 80. This because the up and downstream values are theoretical numbers and the wondershaper script needs realistic values. You can find your own personal best numbers by testing diffent speeds while up- and downloading heavilly and doing a ping stream (to a fast server) at the same time. When the ping numbers stay low the settings are fine. If you want VoIP to have priority you should put that protocol into the high priority queue. You need to edit the script for that.

Note: Wondershaper is a script which can be customized completely and should be considered: an example. Furthermore: traffic shaping is a complex thing in Linux, you should read up into it.

There's allready a topic on wondershaper here with lots of info: http://wl500g.info/showthread.php?t=...t=wondershaper

[britnet]

Hello,

i did the wondershaper in post-firewall.
But i dont know if it runs.

I teste the Status with

wshaper status eth1

but there is no message.

Does it run?

[Styno]

If you've executed the command in a telnet session you should get output like this (If it doesn't it's not running (at least not on the eth1 interface)):

#wshaper status eth1
qdisc ingress ffff:
statistics truncated
 qdisc sfq 30: quantum 1514b perturb 10sec
statistics truncated
 qdisc sfq 20: quantum 1514b perturb 10sec
statistics truncated
 qdisc sfq 10: quantum 1514b perturb 10sec
statistics truncated
 qdisc htb 1: r2q 10 default 30 direct_packets_stat 24
statistics truncated
 class htb 1:1 root rate 320Kbit ceil 320Kbit burst 6Kb cburst 2008b
 Sent 26373712 bytes 62944 pkts (dropped 0, overlimits 0)
 rate 40540bps 111pps
 lended: 24958 borrowed: 0 giants: 0
 tokens: 69731 ctokens: -12970

class htb 1:10 parent 1:1 leaf 10: prio 1 rate 320Kbit ceil 320Kbit burst 6Kb cburst 2008b
 Sent 1694535 bytes 30560 pkts (dropped 0, overlimits 0)
 rate 2907bps 52pps
 lended: 30560 borrowed: 0 giants: 0
 tokens: 119044 ctokens: 36343

class htb 1:20 parent 1:1 leaf 20: prio 2 rate 288Kbit ceil 288Kbit burst 6Kb cburst 1967b
 Sent 494414 bytes 4506 pkts (dropped 0, overlimits 0)
 rate 1122bps 17pps
 lended: 4506 borrowed: 0 giants: 0
 tokens: 135466 ctokens: 42666

class htb 1:30 parent 1:1 leaf 30: prio 2 rate 32Kbit ceil 288Kbit burst 6Kb cburst 1967b
 Sent 25051594 bytes 27987 pkts (dropped 2872, overlimits 0)
 rate 36605bps 42pps backlog 109p
 lended: 2920 borrowed: 24958 giants: 0
 tokens: -168176 ctokens: -26227

Did you save the flashfs filesystem after you've made changes to the post-firewall script (Check if the line which starts wshaper is in the script)?

Perhaps you should echo the $1 parameter of the post-firewall script to a logfile in /temp to check which interface wshaper is started on.