From: Andy Furniss <adf.lists@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow isolation for ISPs
Date: Thu, 6 Apr 2017 16:41:37 +0100 [thread overview]
Message-ID: <2f543169-e5ad-1b9c-6c50-64747b717272@gmail.com> (raw)
In-Reply-To: <82EC6101-3328-451B-8445-C101C9E4A08F@gmail.com>
Pete Heist wrote:
>
>> Date: Thu, 6 Apr 2017 13:48:00 +0100 From: Andy Furniss
>> <adf.lists@gmail.com> To: cake@lists.bufferbloat.net Subject: Re:
>> [Cake] flow isolation for ISPs
>>
>> Pete Heist wrote:
>>
>>> Cake is not a requirement yet. I like it for several of its
>>> attributes (good performance with high numbers of flows, and also
>>> when “over-limiting”, which I’ll explain more in my next round of
>>> point-to-point WiFi results).
>>
>> Would be nicer for your users though?
>>
>> I mean in the sense that if the "outer" hash could be done on some
>> mark then the inner hash on connection as normal then they would
>> get more than a fifo, which seems to be how current solutions are
>> heading.
>>
>> TBH, though I don't even get your set up - I mean is WISP like some
>> giant lan, or does anyone that asks get a real IP, do subscribers
>> normally have more than one access point? Just curious.
>
> Cake has some nice qualities, yes, so we’ll see.
>
> The network has been assembled over a number of years, by a number
> of people (not by me personally), so it has a life of its own, but
> works quite well, from a member’s perspective. :) I’m still figuring
> out more about it myself, but it consists of a series of nodes, each
> of which has at least a router, a WiFi AP for clients and an uplink
> to the Internet connection either with point-to-point WiFi or some
> other means (fiber, licensed radios, etc). If you want an idea:
>
> http://mapa.czfree.net/#lat=50.76816800116274&lng=15.066890716552734&zoom=13&autofilter=1&type=satellite&geolocate=98%7C114%7C111%7C117%7C109%7C111%7C118%7C115%7C107%7C97&node=6101&aponly=1&bbonly=1&actlink=1&actnode=1&tilt=0&heading=0&
>
>
<http://mapa.czfree.net/#lat=50.76816800116274&lng=15.066890716552734&zoom=13&autofilter=1&type=satellite&geolocate=98|114|111|117|109|111|118|115|107|97&node=6101&aponly=1&bbonly=1&actlink=1&actnode=1&tilt=0&heading=0&>
>
> In some cases, like mine, my CPE has a single IP address from the
> node’s router. In others, where there are nodes on top of apartment
> buildings for example, members connect with Ethernet straight to the
> router on the roof of the building, and IP addresses come from the
> DHCP server on that router, and they get multiple IPs.
>
> So it’s a mixture in this case, and that’s what makes hashing only
> by IP address, or by IP address and flow, not ideal.
Ahh, OK, complicated then.
FWIW you may already know, but as I haven't read u32 docs for years I
don't know if it says but -
To match macs you use (IIRC from a decade ago) negative offsets, so -2
will get ethertype, -8 for 6 bytes is src -14 for dst.
next prev parent reply other threads:[~2017-04-06 15:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.340.1491486631.3609.cake@lists.bufferbloat.net>
2017-04-06 14:18 ` Pete Heist
2017-04-06 15:41 ` Andy Furniss [this message]
2017-04-06 13:19 Konstantin Shalygin
-- strict thread matches above, loose matches on Subject: below --
2017-04-06 8:27 Pete Heist
2017-04-06 8:39 ` David Lang
2017-04-06 8:48 ` Pete Heist
2017-04-06 8:57 ` Jonathan Morton
2017-04-06 9:04 ` Pete Heist
2017-04-06 10:26 ` Andy Furniss
2017-04-06 9:11 ` Jonathan Morton
2017-04-06 9:26 ` Pete Heist
2017-04-07 8:13 ` Pete Heist
2017-04-07 8:28 ` Jonathan Morton
2017-04-07 9:37 ` Pete Heist
2017-04-07 11:13 ` Sebastian Moeller
2017-04-07 11:42 ` Pete Heist
2017-04-08 6:16 ` Pete Heist
2017-04-07 10:56 ` John Sager
2017-04-06 9:33 ` Toke Høiland-Jørgensen
2017-04-06 10:26 ` Pete Heist
2017-04-06 10:50 ` Toke Høiland-Jørgensen
2017-04-06 11:34 ` Pete Heist
2017-04-06 12:14 ` Toke Høiland-Jørgensen
2017-04-06 13:30 ` Pete Heist
2017-04-06 13:42 ` Toke Høiland-Jørgensen
2017-04-06 13:50 ` Pete Heist
2017-04-06 14:41 ` Dave Taht
2017-04-06 12:48 ` Andy Furniss
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=2f543169-e5ad-1b9c-6c50-64747b717272@gmail.com \
--to=adf.lists@gmail.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