From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id CAC203B2A4 for ; Thu, 21 Sep 2023 22:37:19 -0400 (EDT) Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-59c215f2f4aso20735557b3.1 for ; Thu, 21 Sep 2023 19:37:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695350238; x=1695955038; darn=lists.bufferbloat.net; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=XUb1PLAYfuaXTTF9m06uUHpEzDjI+cmz7HpFUJW+DKc=; b=Hxp6bTYn+1rxKMT5TXo1uOAocI/ux5iw04EnpW4K19O/k9ZR9UUUylrq4Lg9wZEI+z 3oEiKk/HiWtr8L8xX+sVt3QynJYStwn6KDKzFlYrJH1bL1ZsQjeW/mWBXeiA+e/b4xf1 4mTQ34Pb4AJqRStJoB0KLD/mkDi1XzZXJYsSdWMJu3ozvJ689AGA7dZAe5vA8a65j7pb 7h2QdebnxVwfleVJ4f6RnceglUOoK25+GI+SuyKLksEJLQ8LHkMiTjVf0sKTTdh7yNqh agQeSRUAePucp7wq/fSFEh2Wx7/ns5obcDaSUZsImIkWnuN3ingM09bbv/zfHpRKjQyO +KBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695350238; x=1695955038; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=XUb1PLAYfuaXTTF9m06uUHpEzDjI+cmz7HpFUJW+DKc=; b=OL2LJK5d6V5tT4Gh+E2wXIzZD4OuxFKrSU/Yq8X8CnOXpvjfsny7+cGwCgevwbHNdk HfXwy4nlggou+4w0NWiUlNjhMJDXjQDRvSXLvCvAGMA/E/K7GgTyQ3mCZcqNqkoN60W1 eteOky7WKKYWqwWH8tzJ2iqnw2FStxEpp7uCWoGXvHyPRUw3i7/DcRzAmkf5xPGBOUtI zvK4ti/poNvYgw7ItqWmrh/2t4Eh2GgawGQT+0BxQC/htUoP9tI9AfhiKfjDZyTV3kfU +d3yC4Q+Sh8Zj4mPk0QgHGQ7ptWAcdgqym6YEA+BWbXE7WJrXohfSL07y9jL79gUdhv/ 5yyg== X-Gm-Message-State: AOJu0Yxd98Ft4G0QKGSPDAp1EAtrisuREYHPqyBeMvR2EHs2wlmWjSUr hls+iSViRGvEuWWIQy3+9n7unMwMIkhRjF2QRKzfJddHS8Y= X-Google-Smtp-Source: AGHT+IE6gbZpbb/wCbD/rrNOPTwh5W3LoS29RGGyRbNp2JHsgnrUfI/1qoogT8YrWSfkeXZrELqtRFl+8s+aPDoAbzU= X-Received: by 2002:a81:4f8d:0:b0:59b:da0e:9f7d with SMTP id d135-20020a814f8d000000b0059bda0e9f7dmr6970192ywb.12.1695350238403; Thu, 21 Sep 2023 19:37:18 -0700 (PDT) MIME-Version: 1.0 From: Dave Taht Date: Thu, 21 Sep 2023 19:37:05 -0700 Message-ID: To: Dave Taht via Starlink Content-Type: multipart/alternative; boundary="000000000000bae29d0605e97c2a" Subject: [Starlink] revisiting the old "starwrt" plan X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2023 02:37:19 -0000 --000000000000bae29d0605e97c2a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable A genesis point for the creation of this email list was this failed, too ambitious, and too multi-faceted, project proposal from over 2 years back. See and comment on it here: https://docs.google.com/document/d/1rVGC-iNq2NZ0jk4f3IAiVUHz2S9O6P-F3vVZU2y= BYtw/edit In reviewing it today, I am so pleased that everyone here has leaned in on the measurement side described therein, and also there seems to be a ton of information about how starlink=C2=B4s spot beams, etc seemed to work that m= ay or may not be obsolete within it that I would like to update. In retrospect, I gave up on the idea of making all of openwrt, and cool subsystems like samba or matter, interoperate with the mesh code on the starlink routers, or of producing a build that "just worked" on their routers. It was too hard, and too locked down, to even try. I think broader mesh interoperability would be great however - living in an age where an eero cannot interoperate with a tp-link, and so on, evades the true beauty of wifi, and I still hold dear the ideas of starlink powering village connectivity and local services like email, etc, as well as being a better backup to other links, gaining BGP support, in particular. On the embedded front, their first router was IPQ8014 based, for which I had labored for a couple years to finally produce a very good wifi subsystem for, the second (and presently most popular I think? 1+ million in the field) is mt76 based which is getting better all the time, and their latest wifi6 product I know nothing about, and being deeply cynical about all the wifi6 devices I had tested before exiting the embedded the market, would like someone else to test. I personally exited the embedded market in favor of working on libreqos over a year ago. ... and it was mostly the dishy that in the end I felt just needed a few tweaks, and their headends. Anyway: given that openwrt is nearing a final release in this development cycle and I have also been scoping out improvements to CAKE based on what we have learned from the mikrotik and LibreQos deployments, thinking about what is still wrong with wifi was on my mind today. In particular, I enjoyed reminiscing about the fire I had had in my veins back then about getting in there and making it the best ISP router on the planet. --=20 Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.htm= l Dave T=C3=A4ht CSO, LibreQos --000000000000bae29d0605e97c2a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

A genesis point for the creation of th= is email list was this failed, too ambitious, and too multi-faceted, projec= t proposal from over 2 years back. See and comment on it here:


In reviewing=C2=A0it today,=C2=A0 I am so pleased that everyo= ne here has leaned in on the measurement side described therein, and also t= here seems to be a ton of information about how starlink=C2=B4s spot beams,= etc seemed to work that may or may not be obsolete within it that I would = like to update.=C2=A0

In retrospect, I gave up on = the idea of making all of openwrt, and cool subsystems like samba or matter= ,=C2=A0=C2=A0interoperate with the mesh code on the starlink routers, or of= producing a build that "just worked" on their routers. It was to= o hard, and too locked down, to even try.=C2=A0

I = think broader mesh interoperability would be great however - living in an a= ge where an eero cannot interoperate with a tp-link, and so on, evades the = true beauty of wifi, and I still hold dear the ideas of starlink powering v= illage=C2=A0connectivity and local services like email, etc, as well as bei= ng a better backup to other links, gaining BGP support, in particular.=C2= =A0=C2=A0

On the embedded front, their first route= r was IPQ8014 based, for which I had labored for a couple years to finally = produce a very good wifi subsystem for, the second (and presently most popu= lar I think? 1+ million in the field) is mt76 based which is getting better= all the time, and their latest wifi6 product I know nothing about, and bei= ng deeply cynical about all the wifi6 devices I had tested before exiting t= he embedded the market, would like someone else to test.

I personally exited the embedded market in favor of working on libre= qos over a year ago.

... and it was mostly the dis= hy that in the end I felt just needed a few tweaks, and their headends.

Anyway: given that openwrt is nearing a final release= in this development cycle and I have also been scoping out improvements to= CAKE based on what we have learned from the mikrotik and LibreQos deployme= nts, thinking about what is still wrong with wifi was on my mind today. In = particular, I enjoyed reminiscing=C2=A0about the fire I had had in my veins= back then about getting in there and making it the best ISP router on the = planet.=C2=A0=C2=A0




--
--000000000000bae29d0605e97c2a--