----- Original Message -----
From: "Andrew Lewis" <andrew at coastal dot com>
To: "Brandon Holland" <brandon at cookssaw dot com>
Cc: <m0n0wall at lists dot m0n0 dot ch>
Sent: Friday, February 20, 2004 6:52 AM
Subject: Re: [m0n0wall] Shaper - Pipe Momentarily Burstable?
> Brandon Holland wrote:
> > I have a problem similar in nature. We currently use a wirelessly
> > shared T1 connection.
> > Brandon
> >>-----Original Message-----
> >>From: BaitFish [mailto:holycarp00 at hotmail dot com]
> >>Sent: Thursday, February 19, 2004 7:43 PM
> >>To: m0n0wall list
> >>Subject: [m0n0wall] Shaper - Pipe Momentarily Burstable?
> >>I've read up looking for info but haven't found an answer. Thanks for
> > the
> >>write up on shaping by the way, Adam. My situation is this. My cable
> >>connection (Comcast) allows a higher than the normal throughput burst
> Are you talking about burstable inbound speed (from the ISP to you),
> outbound, or both?
> In my experience inbound traffic can only be throttled so much.
> Delaying TCP acks or whatever. Most of the time though your shaping
> policy in really only effective on the outbound traffic.
Yes, that's what I was speaking of. Now that you put it that way, I
understand what you're getting at. Using a shaper to delay inbound ISP=>me
traffic is kinda useless, just creating a bottleneck, damning up packets,
more delay, right? Would it be better to abandon inbound shaping? My
objective with shaping is to prevent delays to "normal" web use while say
P2P or NNTP uses as much of the bandwidth as it can otherwise.