Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cerowrt (linux 3.10) vs openwrt 21.02.2
Date: Wed, 9 Mar 2022 09:37:09 -0500	[thread overview]
Message-ID: <CAA93jw4ryCEo9-OtZTnHKgEy28TQQFCu-UdBgimmqA4ED_qt6g@mail.gmail.com> (raw)

I am testing what I think might be the last cerowrt box in the world
at esr's place.

# cerowrt, on FIOS, with sqm configured for 24/24 mbit up/down, over
unencrypted wifi

https://www.waveform.com/tools/bufferbloat?test-id=a6e6d9a7-051f-4168-8149-8ebe44026ce8
https://www.waveform.com/tools/bufferbloat?test-id=415a03d5-2788-4589-a3cf-282d63a2fc2f

Bufferbloat scores of A or A+ on those above.

# openwrt, same FIOS connection, admittedly this time going through
the cerowrt box ALSO,
with cake configured for 20/20 on a wndr3700 with wpa2

https://www.waveform.com/tools/bufferbloat?test-id=7f3c7a5a-467b-4c01-91cd-fd88e14d460e
https://www.waveform.com/tools/bufferbloat?test-id=cc77ad98-afca-4240-8597-5c7301980cb3

Much worse bufferbloat scores.

# Disabling cake entirely on the openwrt router

https://www.waveform.com/tools/bufferbloat?test-id=f144e0c0-ba7d-4905-8c1e-8349e4491cf6

Was not much help. Really puzzled as to why the down was so much
slower. Cerowrt of course doesn't bridge wifi interfaces as openwrt
does,

Same distance from the AP in both cases. Anyway, I plan to "upgrade"
this last cerowrt box on the planet today, hopefully it's the double
nat,
or some other variable leading to such a difference between code from
2014 and today

-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2022-03-09 14:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4ryCEo9-OtZTnHKgEy28TQQFCu-UdBgimmqA4ED_qt6g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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