Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Mark Thurston <mark@mdvthu.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	"OpenWrt Development List" <openwrt-devel@lists.openwrt.org>,
	"BBR Development" <bbr-dev@googlegroups.com>,
	discuss <discuss@measurementlab.net>
Subject: Re: [Cerowrt-devel] packet captures of sony's new 80Mbit service?
Date: Thu, 12 Oct 2023 00:20:37 +0200	[thread overview]
Message-ID: <AA091DB2-03C9-4999-BC47-0531C70D2254@gmx.de> (raw)
In-Reply-To: <18b20214171.ce230271334007.9002624123008361629@mdvthu.com>

Hi Mark,


> On Oct 11, 2023, at 21:05, Mark Thurston <mark@mdvthu.com> wrote:
> 
> ---- On Wed, 11 Oct 2023 18:04:41 +0100  Dave Taht  wrote --- 
>> Anyone got a ps4 or ps5 and can take a packet capture at their router?
>> Dying to know if it is cubic or bbr in particular
>> 
> 
> Sorry if this is a silly comment but will all traffic not be encrypted?

	[SM] Yes, likely it will be.

> Unless you've changed the certs on the PS, surely it won't be easy to do MITM packet analysis of the content, only analysis of the approximate size?

	[SM] I guess the first question really is, is the data rate going to be constant or variable and what rate will be measurable on average... and will the quality be noticeably better. After all few users will pick an 80 Mbps service unless that is noticeably better than a 25 mbps service... I can hardly notice the difference between 1K and 4K resolution (on a 43inch display at 2-3 meter distance) so I would likely not notice or care, but I am not the core audience anyway ;)


Regards
	Sebatian


> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel


      parent reply	other threads:[~2023-10-11 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 17:04 Dave Taht
     [not found] ` <18b20214171.ce230271334007.9002624123008361629@mdvthu.com>
2023-10-11 22:20   ` Sebastian Moeller [this message]

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=AA091DB2-03C9-4999-BC47-0531C70D2254@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bbr-dev@googlegroups.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=discuss@measurementlab.net \
    --cc=mark@mdvthu.com \
    --cc=openwrt-devel@lists.openwrt.org \
    /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