From: Sebastian Moeller <moeller0@gmx.de>
To: "G. Amanakis" <g_amanakis@yahoo.com>,cake@lists.bufferbloat.net
Subject: Re: [Cake] Per-host fairness
Date: Sun, 16 Oct 2016 19:59:08 +0200 [thread overview]
Message-ID: <D392FF3C-D3DB-4F1B-9198-0F08CB3AF73D@gmx.de> (raw)
In-Reply-To: <EA1B0031-CA00-4E54-81DD-670B6A42839A@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
Hi,
Could you also try dual-srchost on egress and dual-srchost on ingress, please. These promise per-IP fairness at the first level and per-flow fairness "inside" each IP. So if you think through it you can setup the ingress and egress shapers to aim for per-internal-IP address which I believe is what you are after. Triple-isolate is much harder to argue with, partly because it is lacking a clear description what it does short of the source code, so it is somewhat opaque what to expect in a given set of bidirectional flows. In short you might have found a flaw in triple-isolate or it is working as intended, which only JM will be able to answer. Cursory experiments in the past indicated that a properly configured dual-srchost/dsthost pair on ingress and egress work closer to a layman's expectations... Oh, with the new and shiny deNAT features the dual-isolation options should now also work on a wan interface for IPv4, thanks to Kevin's persistence.
Best Regards
Sebastian
On October 16, 2016 7:30:04 PM GMT+02:00, "G. Amanakis" <g_amanakis@yahoo.com> wrote:
>I meant B gets always 1/3 of the bandwidth. It also gets worse if A is
>using bittorrent. The setup with cake doesn't involve tc-flow or
>marking packets with iptables.
>
>On October 16, 2016 11:57:03 AM EDT, "G. Amanakis"
><g_amanakis@yahoo.com> wrote:
>>I am trying the cobalt branch along with the 950-add-cake-to-tc.patch
>>from lede-git on Archlinux. However, I cannot get per-host fairness as
>>expected, neither with IPv4 behind NAT, nor with IPv6. Having host A
>>downloading from 2 sites and host B from 1, A gets always 1/3 of
>>available bandwidth. I am using "bestefforts triple-isolate nat" on
>>egress and ingress ifb of the WAN interface. Kernel 4.4.24 and 4.7.6.
>>
>>The same setup with the same bandwidth limiting (3300kbit/900kbit)
>>works as expected with fq_codel, tc-flow using mark for hashing, and
>>iptables with HMARK using source egress ip for hashing and CONNMARK on
>>WAN.
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Cake mailing list
>Cake@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cake
[-- Attachment #2: Type: text/html, Size: 2758 bytes --]
next prev parent reply other threads:[~2016-10-16 17:59 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 [this message]
2016-10-18 1:33 ` Georgios Amanakis
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=D392FF3C-D3DB-4F1B-9198-0F08CB3AF73D@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=g_amanakis@yahoo.com \
/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