Hi,
So, I've isolated the problem to this piece of code from the script:
########## downlink #############
# slow downloads down to somewhat less than the real speed to prevent
# queuing at our ISP. Tune to see how high you can set it.
# ISPs tend to have *huge* queues to make sure big downloads are fast
#
# attach ingress policer:
tc qdisc add dev $DEV handle ffff: ingress
# filter *everything* to it (0.0.0.0/0), drop everything that's
# coming in too fast:
== HERE ==
tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \
0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1
==========
and I really have no idea why this would cause the interface to drop all
packets (that's what it seems to be doing).
Anyone have any ideas??
BTW, wondershaper script is at:
http://lartc.org/wondershaper/
Thanks,
Rob
On Mon, 28 Oct 2002 13:43:35 -0500
Rob <rob00si@fastmail.fm> wrote:
> Hi,
>
> When i do 'wshaper start' the interface i have defined stops routing
> traffic for some reason. It resumes routing when i do 'wshaper stop'.
>
> I'm using debian stable (3.0 woody) with debian's default 2.4.18-686
> kernel.
>
> When I run the script I get no errors, and when I do a 'status',
> everything looks correct.
>
> Can ANYONE please give me a little insight as to what to do?
>
> I have the variables set as follows:
>
> DOWNLINK=1450
> UPLINK=180
> DEV=eth0
>
> The machine is a NAT machine. I'm using shorewall to handle the NAT
> stuff for me. But even with shorewall disabled, wshaper still fails.
>
> Thank you for your help.
>
> -Rob
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
