From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sa.plexicomm.net (sa.plexicomm.net [204.80.232.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F0DFD3B29E for ; Fri, 22 Nov 2019 06:07:55 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by sa.plexicomm.net (Postfix) with ESMTP id 5B1DA412EFC for ; Fri, 22 Nov 2019 06:06:28 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at plexicomm.net X-Spam-Flag: NO X-Spam-Score: -0.202 X-Spam-Level: X-Spam-Status: No, score=-0.202 tagged_above=-9999 required=4.5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: sa.plexicomm.net (amavisd-new); dkim=pass (1024-bit key) header.d=plexicomm.net Received: from sa.plexicomm.net ([127.0.0.1]) by localhost (sa.plexicomm.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-x2fJeuDNJe for ; Fri, 22 Nov 2019 06:06:27 -0500 (EST) Received: from mail.plexicomm.net (mail.plexicomm.net [204.80.232.17]) by sa.plexicomm.net (Postfix) with ESMTP id DC9B9412EFA for ; Fri, 22 Nov 2019 06:06:27 -0500 (EST) DKIM-Signature: a=rsa-sha256; t=1574420867; x=1575025667; s=key1; d=plexicomm.net; c=relaxed/relaxed; v=1; bh=ndfDlHkrr6V2eFWHYZmDKsRCl2RPMvkcAMLlaLW6S2A=; h=From:Reply-To:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; b=VQzdjo1HdvCd0Fd59YhOpZT1dpHT7yyBWx/D5WcgDr5CeEodkvdXLUKnPcYjWG7XO91ZCMxU81c8bGb9mYz7zOvEy7gVIkvXUAFTyFM+G/9LtZ34J5kIB/Ezi7DEmfhE4Ixe9Be947niJdz1CTZyqoGGVobTq0BAKa5CnNLYO4E= Received: from [192.168.11.33] ([23.226.94.156]) by mail.plexicomm.net (12.2.0 x64) with ASMTP id 201911220607473144 for ; Fri, 22 Nov 2019 06:07:47 -0500 From: "Adam Moffett" To: cake@lists.bufferbloat.net Date: Fri, 22 Nov 2019 11:07:54 +0000 Message-Id: In-Reply-To: References: Reply-To: "Adam Moffett" User-Agent: eM_Client/7.2.36908.0 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] Cake implementations X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Nov 2019 11:07:56 -0000 >> >> Are there any commercial products already using Cake? > >Evenroute, eero, ubnt top that list. Evenroute's implementation is >superb, the first one that used active line measurements to handle >"sag". Anything derived from openwrt (somewhere between 10-30% of the >home router market). I'm not sure if preseem is using it or not. >dd-wrt. Most other things doing "SQM" are doing it via htb + fq_codel. > > An idea which was floated was to experiment with routing ISP customer=20 traffic through a Linux server using cake to improve customer=20 experience. Basically like Preseem. My colleague has toyed with it a=20 bit in small test cases and was impressed with the outcomes. He's looked closer than I have, but I'm trying to picture how his idea=20 would scale. I believe I'm seeing a CLI tool for configuring policies. =20 It seems like we'd have to create a middle layer to create/update=20 policies for customer's IP address based on information obtained from=20 our AAA and CRM systems. I can picture some shapes that might take, but=20 I think it would ultimately have to revolve around scripting the tc=20 command. There would be thousands of policies and a policy would be=20 created/updated whenever a subscriber reconnects (e.g. when a DHCP lease=20 renews or a RADIUS auth event happens or similar). Should we even pursue this idea? Although most staff who would touch this will have studied programming=20 in college, I would not qualify any of us as "programmers" per se. My=20 biggest concern would be hitting a service affecting problem that we=20 can't solve. Second concern is that many of our equipment vendors already use Linux. =20 Even Cisco now in some products. Maybe we'll waste our time trying to=20 roll our own solution and then find that a software update from a vendor=20 next year gives us everything we needed anyway. -Adam