From: patric <pakar@imperialnet.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: different bandwidth for each connection
Date: Wed, 11 Jul 2007 14:16:31 +0200 [thread overview]
Message-ID: <4694CA1F.1070705@imperialnet.org> (raw)
In-Reply-To: <4.4-22817-973625708-1184150309@seznam.cz>
Hi Thomas,
Sounds like this is a question for the user-list and not the devel.
But here you have a packet-shaping guide. It's for gentoo, but should be
quite similar on all distributions.
http://gentoo-wiki.com/HOWTO_Packet_Shaping
And if you don't want to manually write the shaper-scripts then have a
look at either shorewall, that has shaping built in, or have a look at
wondershaper.
/Patric
tomasnull@seznam.cz wrote:
> Hi *,
>
> I have an application which opens more TCP sockets,
> what I need to do is
> limit the bandwidth that each socket may consume
> (possibly to
> different values). I'm wondering what is the best way
> to do this?
>
> Thanks for your responses
> Tomas
>
>
>
next prev parent reply other threads:[~2007-07-11 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 10:38 different bandwidth for each connection
2007-07-11 12:16 ` patric [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-11 9:56 tomas
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=4694CA1F.1070705@imperialnet.org \
--to=pakar@imperialnet.org \
--cc=netfilter-devel@lists.netfilter.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.