From: Michael Richardson <mcr@sandelman.ca>
To: Adam Thompson <athompson@merlin.mb.ca>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] VPN woes, recommendations?
Date: Fri, 17 Feb 2023 13:29:23 -0500 [thread overview]
Message-ID: <12481.1676658563@localhost> (raw)
In-Reply-To: <YQBPR0101MB89254CCAC6EB4DB67D5BD6C59BA19@YQBPR0101MB8925.CANPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
Do we know for sure that the starlink terminals don't do any kind of TCP
performance enhancing proxy? (TCP ACK spoofing)
VPNs hide that info.
I believe that the Flent tests would also ignore such things.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-02-17 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:30 Adam Thompson
2023-02-17 16:34 ` Dave Taht
2023-02-17 16:36 ` Daniel C. Eckert
2023-02-17 16:38 ` Adam Thompson
2023-02-17 16:39 ` Adam Thompson
2023-02-17 16:45 ` Dave Taht
2023-02-17 17:38 ` Adam Thompson
2023-02-17 17:40 ` Dave Taht
2023-02-17 16:47 ` Nathan Owens
2023-02-17 18:29 ` Michael Richardson [this message]
2023-02-17 21:01 ` David Lang
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=12481.1676658563@localhost \
--to=mcr@sandelman.ca \
--cc=athompson@merlin.mb.ca \
--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