Shorewall users - Apr 2004 - Traffic Shaping using Shorewall and WonderShaper

Hi Guys,

	I''m asking this question again because I have exhausted resources
for understanding how to get it to work.

I''ve read the howto on getting traffic shaping to work
(shorewall''s
web site) as well as trying out wondershaper''s htb and cbq scripts.
Somehow both does not seem to happen as I want it to.

I''ve also read through the lartc documentation/ADSL bandwidth
management.
I also went to the IRC Channel (no traffic) and tried subscribing to 
the lartc mailing list (no response). Emailing the wondershaper Script
writer. (no response)

Ping Times are Not very good. (ping www.yahoo.com)
Loaded Average ~1500ms (Using Bittorrent, DL 1 file @~25KB/s)
Unloaded Average ~310ms

The Link when Unloaded, trying one of those Bandwidth Test (on the internet)
unloaded yielded ~230kbit/s.
Loaded yielded ~30kbit/s

Due to this, Web surfing slows to a crawl, and ftp transfers also slows
to a crawl. 

I''ve also tried inputting this lines into iptables

iptables -t mangle -A outtos -p tcp -m tcp --dport 80 -j TOS --set-tos 0x10
iptables -t mangle -A outtos -p tcp -m tcp --sport 80 -j TOS --set-tos 0x10

(mimicking what I saw for the ssh ports)

No Cigar there as well. I really Need some pointer here. I know this is 
not the place. But I have no idea where else to turn/google for more info.

This works well for me. I didn''t need much, I just wanted to make sure
uploads didn''t kill interactive performance, and that even under heavy
download use by multiple users I could still get in to the firewall.

 - I used the CBQ version of Wondershaper 1.1a

 - TC_ENABLED=Yes  and  CLEAR_TC=Yes  in shorewall.conf

 - create a tcstart script under /etc/shorewall that runs the wondershaper:
       #!/bin/bash
       /etc/shorewall/wshaper

 - I only set three variables at the top of the wondershaper script:
      DOWNLINK=360   # this is for a 384kbit up and down connection
      UPLINK=360
      DEV=eth0       # this is my public-side interface

 - There''s one other small change you must make in the top portion of
wshaper script, read the script to see what it is ;)

 - all else at shorewall default (version 1.4.something)


This was on a Redhat 9 box, and Redhat''s kernel already had everything
needed for traffic shaping. Tom has more info about what''s needed in
the
kernel at http://www.shorewall.net/traffic_shaping.htm