From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] arp flow dissector
Date: Mon, 3 Sep 2018 15:26:11 +0300 [thread overview]
Message-ID: <44155B82-EEFA-4769-AD95-5D17EC677905@gmail.com> (raw)
In-Reply-To: <87ftyq25q0.fsf@toke.dk>
> On 3 Sep, 2018, at 2:14 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> However, in normal operation ARPs should be fairly rare, so adding this
> support to CAKE would mostly be to protect against flooding, wouldn't
> it?
Mostly it's just for consistency's sake. Currently all ARPs end up in a single queue together, because they have no IP header and no transport header to extract any of the components of the usual 5-tuple from. With IP addresses extracted, they would be correctly associated with their originating and/or destination hosts for fairness purposes, while still being in distinct queues from normal traffic.
I suspect anyone generating an ARP flood would also be doing a lot of spoofing, so it's not actually very helpful from that perspective. In fact, arguably the current behaviour of putting all ARP traffic in a single queue would be better.
Conversely, it's straightforward to imagine a scenario where ARP is a tiny fraction of the traffic generated by one host, but ARP traffic from many idle hosts contributes more significantly to the total. Most of these ARP requests might just be part of a DHCP transaction.
- Jonathan Morton
next prev parent reply other threads:[~2018-09-03 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 19:37 Dave Taht
2018-09-03 1:36 ` Jonathan Morton
2018-09-03 11:14 ` Toke Høiland-Jørgensen
2018-09-03 12:26 ` Jonathan Morton [this message]
[not found] ` <nycvar.QRO.7.76.6.1809030529130.4352@qynat-yncgbc>
2018-09-03 13:00 ` Jonathan Morton
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=44155B82-EEFA-4769-AD95-5D17EC677905@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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