From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Patrick Leslie Polzer <leslie.polzer@gmx.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Shaping ingress traffic
Date: Fri, 18 Jun 2004 01:47:58 +0100 [thread overview]
Message-ID: <40D23BBE.7060404@dsl.pipex.com> (raw)
In-Reply-To: <20040614180844.392a2608.leslie.polzer@gmx.net>
Patrick Leslie Polzer wrote:
> Hello,
>
> I know that policing ingress traffic can not be as effective as shaping
> egress traffic, but I would still like to know your opinions on the
> best thing I could do with my setup:
>
> I have a total asymmetric bandwidth of 768kBit/128kBit.
>
> Three hosts are masqueraded via this interface (ppp0),
> with two on the interface 'vortex' and one on 'dec'.
> Each one should get at least about one third of the
> available downstream, and more if there's more available.
>
> How is this most effectively achieved?
You could use IMQ(+NAT patch) on ppp0 then shape using HTB etc.
www.linuximq.net
www.lartc.org
The lartc list may help with details.
Andy.
prev parent reply other threads:[~2004-06-18 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 16:08 Shaping ingress traffic Patrick Leslie Polzer
2004-06-18 0:47 ` Andy Furniss [this message]
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=40D23BBE.7060404@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=leslie.polzer@gmx.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox