From: Nathan Owens <nathan@nathan.io>
To: Dave Taht <davet@teklibre.net>
Cc: Hauke Mehrtens <hauke@hauke-m.de>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] (udm pro) Was: Re: Does the dish run OpenWrt?
Date: Tue, 8 Jun 2021 14:52:24 -0700 [thread overview]
Message-ID: <CALjsLJtcxLmhkELfDM7pmeXyuLYJL4UyYOVSyd=o1Hyq5bYN4w@mail.gmail.com> (raw)
In-Reply-To: <6A2BF4D0-EF5E-4256-AE95-B61F12200BD8@teklibre.net>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
I found out you can build custom kernels for the UDM Pro. The current one
doesn't have CAKE, but it does have FQ_CODEL so I switched to that for now.
I'll get around to building a custom kernel in the coming weeks.
I'm running pihole and ntopng now:
https://github.com/boostchicken/udm-utilities
On Sun, May 16, 2021 at 4:04 PM Dave Taht <davet@teklibre.net> wrote:
> hmm, the ubnt udm pro is also built around buildroot.
>
> Is there some 3rd party software shop out there doing wierd things with
> json, etc, leveraging buildroot? I mean… angular? come on...
>
> The udm pro is really great hw, saddled with really crappy software. As
> appears to be the dishy…. I hope one day we could make openwrt run on both.
>
>
>
> > On May 16, 2021, at 3:21 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >
> > On 5/16/21 10:30 PM, Dave Taht wrote:
> >>
> https://www.starlink.com/assets/pdfs/Starlink-Open-Source-Components-License-Notices.pdf
> >> I don’t see any obvious notes to openwrt related modules, nor dnsmasq.
> linux 4.9 seems to be in use.
> >
> > Thank you for this link.
> > It says: "buildroot2017.1" many software components are from the end of
> 2016 or the beginning of 2017 which matches the buildroot version. This
> does not look like an OpenWrt (fork) or something using the QSDK.
> >
> > They are using musl libc from 2020 and Linux 4.9.
> >
> > Did anyone request access to the code for the Open Source Components
> used by Starlink?
> > They says:
> > > You may request access to the code for our Open Source Components
> > > through your Starlink account.
> > https://www.starlink.com/legal/software-license-and-usage-terms
> >
> > If so, it would be nice if you could upload the code somewhere.
> >
> > Hauke
> > <OpenPGP_0x93DD20630910B515.asc>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2977 bytes --]
next parent reply other threads:[~2021-06-08 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98e5e35f-dcca-0b1c-65c1-3da193779b5f@phrozen.org>
[not found] ` <d7409eb6-e972-ac74-36d0-ea5297c39ad0@hauke-m.de>
[not found] ` <95CC2CF3-6EBB-4F8F-AD2C-58E791459E8D@teklibre.net>
[not found] ` <701613ff-7a53-267f-77d0-a4e015b8410c@hauke-m.de>
[not found] ` <6A2BF4D0-EF5E-4256-AE95-B61F12200BD8@teklibre.net>
2021-06-08 21:52 ` Nathan Owens [this message]
2021-06-08 22:29 ` Nils Andreas Svee
2021-06-08 22:31 ` Nathan Owens
2021-06-08 23:37 ` Dave Taht
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALjsLJtcxLmhkELfDM7pmeXyuLYJL4UyYOVSyd=o1Hyq5bYN4w@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=davet@teklibre.net \
--cc=hauke@hauke-m.de \
--cc=starlink@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