From: "Nils Andreas Svee" <me@lochnair.net>
To: "Dave Taht" <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] UniFi Dream Machine Pro
Date: Sun, 24 Jan 2021 01:31:30 +0100 [thread overview]
Message-ID: <031e7e2e-0191-4f38-b446-1cc2acba0d61@www.fastmail.com> (raw)
In-Reply-To: <CAA93jw6WvsKNQXHB8BuVi=ZzfJ88y36YHnki3c6Z-0k292pD0w@mail.gmail.com>
Was asked to chip in here, so I'll provide what little I know.
I never looked too hard at the new ARM-based units, because Ubiquiti's been refusing to release the GPL archives for them [1].
But AFAIK they're based on Buildroot (there's some info about that in the same thread [2]), and people have been cross-compiling userspace stuff for them, tusc from the WireGuard thread did just that with Boringtun to at least have WireGuard running in userspace [3].
It's running kernel 4.1.37 (heavily modified I assume, as they always are). And in [2] there's linked a text file with a information dump from on of those boxes, kernel config included. I assume though, that they've backported so much it's not possible to use the upstream kernel tree to compile against.
[1]: https://github.com/WireGuard/wireguard-vyatta-ubnt/issues/32#issuecomment-652755919
[2]: https://github.com/WireGuard/wireguard-vyatta-ubnt/issues/32#issuecomment-643757919
[3]: https://github.com/tusc/wireguard/blob/master/compiling.md
Best Regards
Nils
next prev parent reply other threads:[~2021-01-24 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:55 Dave Taht
2021-01-22 19:42 ` Stuart Cheshire
2021-01-22 20:42 ` Sebastian Moeller
2021-01-22 21:09 ` Toke Høiland-Jørgensen
2021-01-22 21:43 ` Jonathan Morton
2021-01-23 23:19 ` Dave Taht
2021-01-24 6:50 ` Mikael Abrahamsson
2021-01-23 23:30 ` Dave Taht
2021-01-24 0:31 ` Nils Andreas Svee [this message]
2021-01-24 1:08 ` Nils Andreas Svee
2021-01-26 16:02 ` Dave Taht
2021-01-27 22:58 ` Nils Andreas Svee
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=031e7e2e-0191-4f38-b446-1cc2acba0d61@www.fastmail.com \
--to=me@lochnair.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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