From: Georgios Amanakis <g_amanakis@yahoo.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Per-host fairness
Date: Mon, 17 Oct 2016 21:33:46 -0400 [thread overview]
Message-ID: <1476754426.21726.1.camel@yahoo.com> (raw)
In-Reply-To: <EA1B0031-CA00-4E54-81DD-670B6A42839A@yahoo.com>
I tried with "besteffort dual-dsthost nat" on ifb ingress and
"besteffort dual-srchost nat" on WAN egress, and when doing simple
things (i.e. downloading from a couple of websites) the bandwidth is
divided fair per-host, i.e 1:1 between A and B. However, when one of
the hosts is using bittorrent, he also gets most of the bandwidth, i.e.
if total ingress bandwidth is 3300kbit, A is using bittorrent and gets
2900kbit, B is downloading from a single website and gets 400kbit.
next prev parent reply other threads:[~2016-10-18 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 15:57 G. Amanakis
2016-10-16 17:30 ` G. Amanakis
2016-10-16 17:59 ` Sebastian Moeller
2016-10-18 1:33 ` Georgios Amanakis [this message]
2016-10-18 8:44 ` moeller0
[not found] <mailman.3.1476806401.24997.cake@lists.bufferbloat.net>
2016-10-21 3:08 ` Georgios Amanakis
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476754426.21726.1.camel@yahoo.com \
--to=g_amanakis@yahoo.com \
--cc=cake@lists.bufferbloat.net \
/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