From: "Daniel C. Eckert" <eckertd@gmail.com>
To: Adam Thompson <athompson@merlin.mb.ca>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] VPN woes, recommendations?
Date: Fri, 17 Feb 2023 11:36:24 -0500 [thread overview]
Message-ID: <CAGNc-gDX0u=pFwy3kXkQu3sPo8XJCCG9OZd7nagfvbKVVsMp9g@mail.gmail.com> (raw)
In-Reply-To: <YQBPR0101MB89254CCAC6EB4DB67D5BD6C59BA19@YQBPR0101MB8925.CANPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2487 bytes --]
Interesting scenario. This reply only addresses a small part of your
message: While I see you've done the math and checked the specs for the
Aruba devices -- have you already conducted a few non-VPN tests between
direct-wire-connected laptops/devices at those two locations to know what
"baseline" bandwidth you're starting from when considering the max
potential bandwidth for the encrypted traffic? For example, since you're
on a business plan, you should have a direct public IP to target with iperf
traffic from either end, even if not encrypted.
Dan
On Fri, Feb 17, 2023 at 11:30 AM Adam Thompson via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Hi, all.
> We've been trying to develop a plug-and-play L2 VPN over Starlink, using
> Aruba Hospitality-series Remote APs like their RAP-505H.
> It's not going great, and I'm wondering about several Starlink-specific
> issues.
>
> First, having multiple devices in serial is generally not a great idea for
> reliability. Can we realistically plug our remote AP directly into the
> dish, still? (This is using Starlink Business, FWIW.). I know we lose
> access to the Starlink app, but we also lose a NATing router and an
> unwanted wifi AP, so that's probably a net zero. I just don't know what
> other dangers/problems that topology might cause.
>
> Secondly, we're only able to push about 30Mbps through the (magical
> Aruba-proprietary GRE+IPsec) tunnel. The bandwidth-delay equations suggest
> we should be seeing around 100Mbps, not 30. (The Aruba devices are rated
> for ~2Gbps encrypted at the site end, and ~7Gbps at the head end, so
> presumably that's not the bottleneck.)
>
> So:
> * does anyone have corroborating *or* contradicting evidence of VPN
> performance over Starlink's particular flavor of Long Fat Pipe, and
> * does anyone have any positive (or negative, I guess!) recommendations
> for cloud-managed VPN devices that can do at least 100M and magically work
> from behind double-NAT/CGNAT like we see with Starlink? Bonus points if it
> does L2 tunnels or can run a dynamic routing protocol.
> * Other comments or suggestions welcome, too.
>
> Thanks,
> -Adam
>
> Get Outlook for Android
> <https://streaklinks.com/BZdCYXLz80mmcz4jWATVEg7r/https%3A%2F%2Faka.ms%2FAAb9ysg>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
ᐧ
ᐧ
[-- Attachment #2: Type: text/html, Size: 4483 bytes --]
next prev parent reply other threads:[~2023-02-17 16:37 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 [this message]
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
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='CAGNc-gDX0u=pFwy3kXkQu3sPo8XJCCG9OZd7nagfvbKVVsMp9g@mail.gmail.com' \
--to=eckertd@gmail.com \
--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