[ previous ] [ next ] [ threads ]
 From:  "Dennis Wallberg" <dennis dot wallberg at bredband dot net>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  SV: [m0n0wall] Re: m0n0 - traffic_shaper
 Date:  Sun, 25 Apr 2004 05:52:12 +0200
I was not saying that inbound traffic shaping did not work just that it
is not sane to use inbound shaping when you have a xDSL/cable I-net

your inbound traffic unless you are ISP... limiting inbound traffic will
not achieve anything unless you have control of the edge routers which


-----Ursprungligt meddelande-----

Skickat: den 24 april 2004 20:36
Till: Adam Nellemann
Kopia: Dennis Wallberg; m0n0wall at lists dot m0n0 dot ch

Hi all you guys!

configured the traffic
shaper for inbound traffic and outbound traffic and it works so fine! I
limited the downstream to
64 Kbits and the upstream to 32 Kbits and it works okey too.
I dont understand you guys. Can you explain me what are you talking
My internet connection is 512 kbits upstream and 128 kbits downstream
(ADSL) and I have 12
computers of different people using Kazaa, Emule, etc etc in each
computer, without any control of
each computer, but its working okey since 4 months ago when I configured
the traffic shaper.

Greetings to all you friends!!!!


> >> Hi
> >> I read the traffic_shaper.txt and I have one question. "For
> >> WAN connections, it is important to ensure that all pipes and
> >> exists in pairs, one for each direction, and that these have the
> >> apropriate bandwidth specifications". Do I really have to have
> >> pipes/queues for inbound traffic? Would it not be sufficient with
> >> rules/pipes/queues on by outbound traffic since this it the only
> >> I really can control?!
> >>  
> >> /Dennis
> Hi Dennis,
> You are of course right, there is (usually) no need to have any 
> pipes/queues/rules for inbound traffic. Indeed, this will often make 
> things worse!
> I was rather new to traffic sharing when I wrote the text, and did so 
> in a hurry due to "popular demand". At the time I thought I'd soon get

> around to writing another, more thorough, version, as well as possibly

> doing the traffic shaper chapter for the m0n0wall documentation 
> project. Unfortunatly I've been very busy ever since, and have thus 
> had no time to do these things :(
> Since then I've myself removed all the inbound rules from my own 
> m0n0wall configuration. I guess I should have posted a notice about
> Sorry for the inconvinience this may have caused!
> Hopefully I will soon be able to, at least, post an updated version of

> traffic_shaper.txt, with corrections such as the above, but right now 
> I'm still too busy.
> Adam.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch

El objetivo escencial del correr es probar los limites de la voluntad