From: Jonathan Morton <chromatix99@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
cake@lists.bufferbloat.net
Subject: Re: [Cake] triple flow isolation
Date: Thu, 14 Jan 2016 18:05:12 +0200 [thread overview]
Message-ID: <D1056413-5D83-44A6-8ED0-9AD456017200@gmail.com> (raw)
In-Reply-To: <A0226FC7-8277-443A-8C8F-97E008440CEF@gmx.de>
> On 14 Jan, 2016, at 17:48, moeller0 <moeller0@gmx.de> wrote:
>
> I am still curious about the non-NAT fairness by internal IP addresses only performance, as far as I understand that is the main request/use case people seem to have.
Non-NAT should work fine, once I’ve fixed the algorithm. That’s a major part of what I intended triple-isolation to do. It still won’t isolate a given host from it’s *own* swarm traffic, unless you also apply Diffserv, but it should prevent one host from monopolising the link with a swarm.
NAT is a problem for Cake instances operating on the “outside” of the boundary, in both directions; they see only the public IP address of the local network, and the addresses of the remote hosts. The only real solution is probably to integrate connection tracking with the flow dissector (or to hurry along the migration to IPv6). That’s beyond my area of expertise in the kernel.
- Jonathan Morton
next prev parent reply other threads:[~2016-01-14 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 17:40 Kevin Darbyshire-Bryant
2016-01-11 18:16 ` moeller0
2016-01-11 20:33 ` Kevin Darbyshire-Bryant
2016-01-14 14:20 ` moeller0
2016-01-14 14:45 ` Jonathan Morton
2016-01-14 15:48 ` moeller0
2016-01-14 16:05 ` Jonathan Morton [this message]
[not found] ` <02A10F37-145C-4BF9-B428-BC1BDF700135@gmx.de>
2016-01-15 0:05 ` Jonathan Morton
2016-01-15 8:05 ` moeller0
2016-01-16 9:05 ` Jonathan Morton
2016-01-16 9:35 ` Jonathan Morton
2016-01-17 22:22 ` moeller0
2016-01-18 9:21 ` moeller0
2016-01-18 9:37 ` Jonathan Morton
2016-01-18 11:08 ` Alan Jenkins
2016-01-18 11:39 ` Jonathan Morton
2016-01-18 16:20 ` Sebastian Moeller
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=D1056413-5D83-44A6-8ED0-9AD456017200@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
--cc=moeller0@gmx.de \
/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