From: Daryll Swer <contact@daryllswer.com>
To: Jeff Hansen <x@jeffhansen.com>
Cc: Frantisek Borsik <frantisek.borsik@gmail.com>,
Jonathan Morton <chromatix99@gmail.com>,
jordan@inacomptc.com, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] CAKE is going to be deployed on Alta Labs any day now!
Date: Mon, 24 Mar 2025 15:39:13 -0000 [thread overview]
Message-ID: <CACyFTPE7FfR0gjyNaJwtc2SfszVoSjWAqCnUyqS+K6KiTABqpA@mail.gmail.com> (raw)
In-Reply-To: <8756E062-0FC3-4301-8884-B1BCA7A124B5@jeffhansen.com>
[-- Attachment #1: Type: text/plain, Size: 4443 bytes --]
I was looking at your Route10 product, but it looks to be consumer-heavy,
at this point time. I run stuff like BGP in my home network (as I have
MPLS-to-the-home delivery) and PIM-SM, would be cool if you folks supported
some DC-fabric features on Route10 in the future with FRR as the daemon or
something.
One thing I'd like to mention, Route10 should have a good NAT
implementation to support EIM-NAT for TCP/UDP to allow P2P networking to
work over a NAT box.
Additionally, support NAT Hairpinning for user's LAN subnets to allow
intra-NAT traffic to work over STUN discovery, this eliminates TURN traffic.
Small to large-scale CGNAT deployments around the globe is something I've
been consulting for a few years now. I'm happy to potentially beta test
your products, if you'd like, for best practices conformance with very
specific RFCs.
BQL would be good to have for long-term viewpoint, perhaps your Ethernet
driver provider, could patch it up for BQL support and that would be a good
foundation for FQ_Codel on your Route10. MikroTik has FQ_Codel, but lacks
BQL, and they refused to listen to Fran and Dave Taht, so perhaps you folks
are our only hope :)
*--*
Best Regards
Daryll Swer
Website: daryllswer.com
<https://mailtrack.io/l/6bdc1188688bc319302e68dd0abb6ef092a85bc8?url=https%3A%2F%2Fwww.daryllswer.com&u=2153471&signature=673d0c5350bbb0e6>
On Mon, 24 Mar 2025 at 20:53, Jeff Hansen <x@jeffhansen.com> wrote:
> Frank,
>
> The hardware that Route10 is based off of doesn’t support FQ Codel nor
> CAKE at all, so everything is done in software on our 5.4 Linux kernel. It
> works great, though. In some instances it’s the only way to max out a PPPoE
> connection and have optimal latency.
>
> It doesn’t look like our ethernet driver supports BQL at all, so we
> haven’t tried that yet, but as is, it absolutely eliminates high latency if
> tuned properly.
>
> -Jeff
>
> On Mar 21, 2025, at 2:27 AM, Frantisek Borsik <frantisek.borsik@gmail.com>
> wrote:
>
> Happy to see that! Thanks, guys.
>
> Adding Jeff
> <https://mailtrack.io/l/874104aa2fae8c2c3e8c0b7c66386cd9ef1a83ab?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjeff-hansen-6794021%2F&u=2153471&signature=efe63bcd8a19e5e7>,
> Alta Labs CTO - Darryl
> <https://mailtrack.io/l/56dc9d27cea2a0afbd536db4021116428c91b0e6?url=https%3A%2F%2Fx.com%2FDaryllSwer%2Fstatus%2F1902486684476047544&u=2153471&signature=b49f25a96708f53a>
> has a suggestion how to push this further: "Maybe they can add both
> FQ_CoDel and CAKE with BQL support? How's hardware-offloading of FQ_CoDel
> looking on these “prosumer” equipment these days? I haven't kept up over a
> year on this topic."
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
>
> https://www.linkedin.com/in/frantisekborsik
> <https://mailtrack.io/l/62c56dba3ad2b34d25f6a2db81adf0b5e9e7c6aa?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Ffrantisekborsik&u=2153471&signature=80914c9fb3689eb2>
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
>
>
> On Fri, Mar 21, 2025 at 3:44 AM Jonathan Morton <chromatix99@gmail.com>
> wrote:
>
>> > On 19 Mar, 2025, at 12:01 am, Frantisek Borsik via Cake <
>> cake@lists.bufferbloat.net> wrote:
>> >
>> > Should be pushed through production in day or two and they will be
>> talking about it on https://streamyard.com/watch/ubYm2AffWkYi
>> <https://mailtrack.io/l/f6be4a2c3da3f8d78695f24266cda26e686e9453?url=https%3A%2F%2Fstreamyard.com%2Fwatch%2FubYm2AffWkYi&u=2153471&signature=a5dbc7add3e2dbe3>
>> this Wednesday, March 19, at 1PM EST / 12PM CST / 11AM MST / 10AM PST
>>
>> I joined the stream, and was able to ask about the throughput they were
>> getting with CAKE on their hardware. This is just for the "Route 10"
>> rather than their APs, and they reported getting about 2.5Gbps throughput
>> with CAKE enabled. They do correctly note that the hardware-accelerated
>> forwarding path is disabled for the interface where CAKE is turned on.
>>
>> Supporting 2.5Gbps is pretty good I think, and should be sufficient to
>> handle all practical Internet subscriptions that are likely to require
>> bufferbloat mitigation. For comparison, on the same call they claimed
>> about 800Mbps throughput for acting as a WireGuard tunnel endpoint.
>>
>> - Jonathan Morton
>
>
>
[-- Attachment #2: Type: text/html, Size: 7080 bytes --]
next prev parent reply other threads:[~2025-03-24 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 22:01 Frantisek Borsik
2025-03-21 0:31 ` jordan
2025-03-21 2:44 ` Jonathan Morton
2025-03-21 8:27 ` Frantisek Borsik
2025-03-24 15:23 ` Jeff Hansen
2025-03-24 15:39 ` Daryll Swer [this message]
2025-03-27 18:45 ` Frantisek Borsik
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=CACyFTPE7FfR0gjyNaJwtc2SfszVoSjWAqCnUyqS+K6KiTABqpA@mail.gmail.com \
--to=contact@daryllswer.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=jordan@inacomptc.com \
--cc=x@jeffhansen.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