Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Nils Andreas Svee <me@lochnair.net>
Cc: Dave Taht <dave.taht@gmail.com>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] udm pro review
Date: Thu, 11 Mar 2021 11:09:14 +1300	[thread overview]
Message-ID: <CAKiAkGTK1nSdXt3S49F1AdL_jsjnDxu9s+3ejPWDzuoD+on9XA@mail.gmail.com> (raw)
In-Reply-To: <797d57333ef504c724262aae5856d5dda54459d0.camel@lochnair.net>

[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]

I was hoping the Lawsuit with Cambria would result in something.

tl;dr Ubiquity took cambria to court because the claimed they copied stuff,
cambria responded with their own litigation by saying Ubiquity wasn't
complying with GPL.

But they settled under NDA and we all lost out.

On Thu, Mar 11, 2021 at 10:44 AM Nils Andreas Svee <me@lochnair.net> wrote:

> Was kinda tempted to get one of those at one point, but seeing the
> software problems with them I'm staying away. Although it could be a
> nice OpenWrt box of course.
>
> Ah yes the GPL violations. I've been asked about bringing both CAKE and
> WireGuard to the UDMs, but with no sources there's not really anything
> I can do (someone did get userspace based WireGuard working though).
>
> When someone contacted UBNT support about it they responded with "We
> don't have any plan to release the GPL source code for the UDM and UDM
> pro yet".
>
> I mean in EdgeMax land they might need a poke to release the archives
> for a new firmware release, but they'll do it. For these however it's
> been 8 months since that request and we've seen nothing.
>
> Next time I'm in the market for new networking equipment I'm probably
> not going to touch Ubiquiti again. I digged it back in the days
> fq_codel was added into the firmware that we reminisced about, but
> those times seems to be long behind us.
>
> </rant>
>
> --
> Best Regards,
> Nils
>
> On Wed, 2021-03-10 at 12:09 -0800, Dave Taht wrote:
> > I have been fiddling with a ubnt udm pro
> >
> > the great - 4GB of ram, really fast cpus, can push a lot of bits
> > through sqm. the sqm-scripts
> > just worked but to make it truly functional at all you need the gui...
> > the good - galene videoconferencing server cross compiled and ran on
> > it first time
> > the bad - innumerable gpl violations
> > the awful - having to register the product online in order to use it
> > at all... and the registration process for a new account... doesn't
> > work.
> >
> > I have never been so tempted to just arbitrarily reflash a box to
> > openwrt without fiddlin further.
> >
> >
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 3357 bytes --]

  reply	other threads:[~2021-03-10 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 20:09 Dave Taht
2021-03-10 21:44 ` Nils Andreas Svee
2021-03-10 22:09   ` Joel Wirāmu Pauling [this message]
2021-03-14 16:31 ` Stephen Hemminger
2021-03-14 17:00   ` 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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKiAkGTK1nSdXt3S49F1AdL_jsjnDxu9s+3ejPWDzuoD+on9XA@mail.gmail.com \
    --to=joel@aenertia.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=me@lochnair.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