lartc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux Traffic-Shaper and other Products
Date: Thu, 27 Dec 2001 08:59:11 +0000	[thread overview]
Message-ID: <marc-lartc-100944374802506@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100938771626368@msgid-missing>

On Thursday 27 December 2001 07:40, Sumit Pandya wrote:
> -- Stef Write :
> >> Take a look at www.allot.com.  They have boxes that can shape traffic
>
> (these boxes run linux with a web-interface and use CBQ to do the traffic
> shaping). They cost about 15.000 USD and they do a poor job. On the other
> hand, I can write you some scripts, you take an old PC with 2 NIC's and you
> pay ma as much as you would paid Allot :-)
> 	Its wonderful, It means we can also shape traffic "from and to" in our
> favorite Linux Box. But sadly on our list I didn't found any clue to
> implement this. Infact what I found is impossibility of this solution. My
> quoriocity to know if there is existing solution, was against  possibility
> of solution, not to buy solution ;-).
>
> >> What you want to do is so easy that you can do it by yourself.  Just
> >> take
>
> a look at the howto, try some things out and post it to this mailing list.
> We will be happy to help you if you encounter a problem.
> 	Hey just a min. HOWTO is documented for limiting one-way traffic. Once
> again I want to clear here that total traffic mean "from and to" a computer
> must be limited to certain limit. Okay then help me, and many list members
> too ;-), and write the way or script to limiting total-traffic of a
> computer. Or otherwise lets go ahead to beat system like allot and
> coordinate for solution for this.
> 	Thanks for taking time to write in.
It's very easy.  If yoy want to shape traffic from and to a computer, you 
need a dedicated linux box that you can put in front of that computer and 
that will act as a gateway.  1 NIC connected to that box and 1 NIC connected 
to the rest of the network.  You really needs this because you can only shape 
traffic that leaves the NIC.  When you have a dedicated box, you can shape on 
both NIC's and so can shape in both directions.  

So we only speak from shaping in one direction, but with 2 NIC's, you can 
shape in both directions.  Allot is doing the same thing.

Stef


-- 

stef.coene@docum.org
 More QOS info : http://www.docum.org/
 Title : "Using Linux as bandwidth manager"
     

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-27  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26 14:47 [LARTC] Linux Traffic-Shaper and other Products Sumit Pandya
2001-12-26 20:20 ` Stef Coene
2001-12-27  6:52 ` Sumit Pandya
2001-12-27  8:59 ` Stef Coene [this message]
2002-01-04 15:28 ` Jerome Petazzoni
2002-01-04 15:48 ` Alessandro Rubini
2002-01-04 20:24 ` Alessandro Rubini
2002-01-05 13:19 ` bert hubert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-100944374802506@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).