All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Traffic shaping for upload & download
Date: Fri, 01 Nov 2002 08:56:40 +0000	[thread overview]
Message-ID: <marc-lartc-103614140018268@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103612899211878@msgid-missing>

On Friday 01 November 2002 06:35, Joseph Watson wrote:
> Hello,
>
> I have a question about two way traffic, and how to shape it?
>
> Lets say we want to limit a customer usage to 256kbit total.  So on my
> firewall I add shaping rules to the client side nice with a ceiling of
> 256kbit.  Now I also want to limit there upload, so I add the same to the
> other nice in the firewall.  But if the customer uploads and downloads at
> the same time, they could use up 512kbit of my connection.  How can one
> handle this problem.  Is there a way to specify a max for all traphic and
> then alow barrowing between upload and download??  Or it this a limitation
> that I will have to live with?
You can use the imq device.  This is a virtual device.  You can redirect 
packets with iptables to it and you can do it on incoming/outgoing and from 
different NIC's.  So you can limit download + upload together like you want.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2002-11-01  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  5:35 [LARTC] Traffic shaping for upload & download Joseph Watson
2002-11-01  8:56 ` Stef Coene [this message]
2002-11-01 16:15 ` Don Cohen

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-103614140018268@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.