It's downright impossible to implement traffic shaping when the traffic is
asymmetrically loaded and you do not control the other end of the link. You
can reserve uplink bandwidth but look at how the problem plays out with
HTTP requests.
You make a tiny, 30 byte request that results in a flood of return traffic.
If you attempt to shape traffic in the customer-side router, you can't
shape it because you've already saturated the inbound pipe.
We experience this problem all the time at DNA lounge. Some joker saturates
the inbound pipe and our best defense becomes 'ban his mac address from
dhcp'. I've seen many recipes for PF that claim to do this but it's
generally hopeless.
-j
On Mon, Sep 23, 2013 at 11:43 AM, Nicholas LoCicero <nick.locicero at gmail.com
> wrote:
> I was there as well, but didn't notice any slow internet. Do you think it
> could be the ISP?
> On Sep 23, 2013 6:45 AM, "Romy Snowyla" <romy at snowyla.com> wrote:
>>> I was at Noisebridge Saturday evening and verify yes it was very slow
>>>> Sent from my iPhone
>>>> > On Sep 22, 2013, at 6:18 PM, Jake <jake at spaz.org> wrote:
>> >
>> > how do you find out what is using up all the bandwidth, and block it?
>> >
>> > the internet is unusably slow. If noisebridge doesn't have tools,
>> materials or even internet connectivity, what are we doing?
>> >
>> > assuming nobody wants to tell me how to poke into the innards of our
>> traffic routing, maybe someone can implement traffic shaping so that no one
>> can use so much bandwidth that everyone else is shut out?
>> >
>> > -jake
>> >
>> _______________________________________________
>> Noisebridge-discuss mailing list
>>Noisebridge-discuss at lists.noisebridge.net>>https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss>>>> _______________________________________________
> Noisebridge-discuss mailing list
>Noisebridge-discuss at lists.noisebridge.net>https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.noisebridge.net/pipermail/noisebridge-discuss/attachments/20130923/c2b9e101/attachment.html>